-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
VStream API: Add flag to stop streaming on a reshard #8628
VStream API: Add flag to stop streaming on a reshard #8628
Conversation
…ournal event instead Signed-off-by: Rohit Nayak <[email protected]>
d8149d3
to
88ad81f
Compare
Signed-off-by: Rohit Nayak <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but let's have @sougou review this too.
@@ -56,6 +56,8 @@ var ( | |||
"vreplication_cellalias", | |||
"vstream_failover", | |||
"vreplication_v2", | |||
"vstream_stoponreshard_true", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just for readability, you might consider adding more underscores.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will fix in my next PR, don't feel like babysitting CI for a couple of hours for this ...
Signed-off-by: Vilius Okockis <[email protected]>
Description
A new flag StopOnReshard is added as an option that the VStream client can provide. Usually on a reshard of a shard that is participating in the stream, the VStream API sends all the events on the original shard and then automatically starts streaming from the new shard set. In this case the journal event is not sent on the stream.
This flag, if set, stops the stream after sending all the streams upto the reshard and includes the journal event pertaining to that reshard as the last event.
Signed-off-by: Rohit Nayak [email protected]
Related Issue(s)
#8595
Checklist
Deployment Notes