-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Add test that shows clfs behavior on dups #5181
base: main
Are you sure you want to change the base?
Conversation
I think the test we want stays under any snapshot limits. Had lots of CLFS increments and then switches leaders. |
9f8fcaa
to
66d06f5
Compare
Signed-off-by: Waldemar Quevedo <wally@nats.io>
66d06f5
to
bb404c5
Compare
var wg sync.WaitGroup | ||
|
||
// The test will be successful if it runs for this long without dup issues. | ||
ctx, cancel := context.WithTimeout(context.Background(), 1*time.Minute) |
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.
Can the test be meaningful running for less time?
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.
In my testing yesterday it was difficult to trip the problem straight away, it would normally need the leader to have bounced around a few times.
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.
on v2.10.11 it would have happened around the 3rd or 4th leader election in this test
Signed-off-by: Neil Twigg <neil@nats.io>
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
No description provided.