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
***Verification failed for column family 0 key 87500643: Value not found: NotFound:***
However this is difficult to debug since the translation from integer used to generate the key into the actual key bytes is complex and configuration-dependent. That makes it difficult to do manual investigation like looking for the key in the SST files. It'd be good to accompany the key integer with the actual key bytes (in hex format) in all error messages printed by the stress tests.
The text was updated successfully, but these errors were encountered:
Summary:
db_stress prints key in both id and hex. #7531
Pull Request resolved: #7533
Test Plan: local test
Reviewed By: akankshamahajan15
Differential Revision: D24252725
Pulled By: jay-zhuang
fbshipit-source-id: f0c1409a0568874df36949d5da139316d978fa98
Summary:
db_stress prints key in both id and hex. facebook#7531
Pull Request resolved: facebook#7533
Test Plan: local test
Reviewed By: akankshamahajan15
Differential Revision: D24252725
Pulled By: jay-zhuang
fbshipit-source-id: f0c1409a0568874df36949d5da139316d978fa98
Currently some failures look like this:
However this is difficult to debug since the translation from integer used to generate the key into the actual key bytes is complex and configuration-dependent. That makes it difficult to do manual investigation like looking for the key in the SST files. It'd be good to accompany the key integer with the actual key bytes (in hex format) in all error messages printed by the stress tests.
The text was updated successfully, but these errors were encountered: