ndb: fix FDB non-uniquness on different FLAGS #1200
Merged
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.
Closes: #1159
I didn't read logs carefully, unfortunately :)
Every time we got FDB missing we got the following 3 reschedules followed by drop as well:
After logging the error I understood that there were 2 FDBs very similar, only difference was flags and master:
After making
flags
field a part of unique index that entry did showed up in the DB: