Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FIXED] Clustering: message store not flushed on followers #849

Merged
merged 1 commit into from
May 30, 2019

Conversation

kozlovic
Copy link
Member

With the SQLStore, this would cause messages to be accumulated
in write cache causing memory growth and no message stored in the
DB until the follower shutsdown or become leader.

Resolves #846

Also made server tests skip SQL specific tests if running tests
with -sql=false for users that don't have/want to setup an
SQL server.

Resolves #845

Signed-off-by: Ivan Kozlovic ivan@synadia.com

With the SQLStore, this would cause messages to be accumulated
in write cache causing memory growth and no message stored in the
DB until the follower shutsdown or become leader.

Resolves #846

Also made server tests skip SQL specific tests if running tests
with `-sql=false` for users that don't have/want to setup an
SQL server.

Resolves #845

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
@coveralls
Copy link

Coverage Status

Coverage increased (+0.004%) to 92.041% when pulling dd64168 on cluster_msg_store_flush into 0844ce1 on master.

Copy link
Member

@derekcollison derekcollison left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kozlovic kozlovic merged commit 5dc1190 into master May 30, 2019
@kozlovic kozlovic deleted the cluster_msg_store_flush branch May 30, 2019 02:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Memory Usage increasing not going down go test now has hard database requirement
3 participants