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] Expire messages based on their timestamp #916

Merged
merged 1 commit into from
Aug 17, 2019
Merged

Conversation

kozlovic
Copy link
Member

This comes into play with clustering when messages are replayed
and their timestamp may now be well in the past.

Resolves #915

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

This comes into play with clustering when messages are replayed
and their timestamp may now be well in the past.

Resolves #915

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

Coverage Status

Coverage increased (+0.04%) to 91.999% when pulling 54ed2b5 on fix_915 into 27593aa 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 dc277f3 into master Aug 17, 2019
@kozlovic kozlovic deleted the fix_915 branch August 17, 2019 01:05
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.

Force memstore/expireMsgs after [INF] STREAM: done restoring from snapshot
3 participants