You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary:
This test was flaky because sometimes a nvm put could be aborted due to an outstanding tombstone for the same key. This can happen because the test is inserting items very quickly and thus evicting quickly. The following scenario can happen:
1. insert "key1" and queue a remove operation for "key1" to NvmCache (via insertOrReplace)
2. insert "key2" ... "key100"
3. triggers eviction of "key1" while a remove tombstone is outstanding for "key1". This NvmCache put is thus aborted.
The fix is to flush nvm-cache periodically to avoid such a race condition.
Reviewed By: jaesoo-fb
Differential Revision: D42443647
fbshipit-source-id: 56508b88b260b5a8fbe41b6d8dd5444e8f2c171f
0 commit comments