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.

Sign up for GitHub

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

Jump to bottom

[FIXED] Clustering: possibly getting empty messages #815

Merged
merged 1 commit into from
Apr 30, 2019
Merged

[FIXED] Clustering: possibly getting empty messages #815

merged 1 commit into from
Apr 30, 2019

Conversation

kozlovic
Copy link
Member

Resolves #814

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

@kozlovic
[FIXED] Clustering: possibly getting empty messages
72b0ebb 
Resolves #814

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

Coverage Status

Coverage increased (+0.02%) to 92.051% when pulling 72b0ebb on cluster_fix_issue_after_snapshot into 25d6ada on master.

@kozlovic kozlovic requested a review from derekcollison April 30, 2019 17:05
derekcollison
derekcollison approved these changes Apr 30, 2019
View reviewed changes
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 57c6c84 into master Apr 30, 2019
@kozlovic kozlovic deleted the cluster_fix_issue_after_snapshot branch April 30, 2019 17:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@derekcollison derekcollison derekcollison approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Clustering: getting empty messages after snapshot if msg store not flushed
3 participants
@kozlovic @coveralls @derekcollison