Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Improve how M3DB handles data durability during topology changes #1183
Improve how M3DB handles data durability during topology changes #1183
Changes from 53 commits
6ef03a3
ff2de89
bb703b1
cd52034
98259a5
a78c997
c84140c
e211867
24774e8
53d2e27
eb08aea
e77a2f9
0677a2a
fbfdd6f
f9652fb
a8b0a3d
e0110b9
e42468d
0684d5c
a651bcf
68f54c9
ca1c3a7
5d09229
71f4f81
79232da
e124a5a
d473e88
7a6700d
4bf1283
7692578
a9d82cd
bf8c623
211955b
35c645d
1a18570
9313876
da65182
053b706
343d9a3
7ca3da6
176edb9
db44926
e0b8541
8cbc5a7
ed99b59
b359a10
dffcbaa
9f6b13a
e6167ba
b472abc
4431196
fc42969
48bfa8a
bd1eb3b
19918e7
ca02bfe
bc798ea
8cfaefb
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Should we just add this as a separate test? Seems like we're repurposing this one and changing it quite substantially?
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.
There are two separate tests, they just call into this shared codepath. I think its fine, if I separated them out completely they'd be almost complete copy-pasta of each other, and the existing test benefits from this additional check as well (even if you don't verify the commitlog behavior, if you're doing a node add you probably want to make sure the node adding keeps track of the data it receives from its peer as well as all the data its receiving while actually joining)
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.
I see, yeah makes sense.
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.
Hm maybe it's better to make it just RF=3?
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.
I honestly just didn't do it because it would probably take a few hours to re-write all the sharding logic and fix any little issues that crop up and it doesn't really make the test any better. Can change it if you feel strongly
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.
Np, that's fine.