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

ReliableTopic can not continue after owner&backup shutdowns together #12919

Closed
mmedenjak opened this issue Apr 19, 2018 · 1 comment
Closed

ReliableTopic can not continue after owner&backup shutdowns together #12919

mmedenjak opened this issue Apr 19, 2018 · 1 comment

Comments

@mmedenjak
Copy link
Contributor

@mmedenjak mmedenjak commented Apr 19, 2018

Reliable topic does not guarantee data safety if owner and backup of backed ring buffer goes down at the same time. This is expected and documented.
But also it can not continue to operate. Currently it stops working with a similar log as below

WARNING: hz.client_0 [dev] [3.9.1-SNAPSHOT] Terminating MessageListener WClient$1@6d83d80d on topic: topic. Reason: Unhandled exception, message: sequence:46 is too large. The current tailSequence is:0
java.lang.IllegalArgumentException: sequence:46 is too large. The current tailSequence is:0

This is tested via client but node would behave the same, because in both proxies we are not handling IllegalArgumentException

Basically client side remembers a too high sequence number. Since all data lost in server side, servers start from zero. And when client asks with its sequence number(46 in this case), it gets IllegalArgumentException.

@mmedenjak
Copy link
Contributor Author

@mmedenjak mmedenjak commented Apr 19, 2018

Fixed by: #12689

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.