Getting Non-existing Value with Concurrent Operations

[kxu1985]

This is a finding when doing the consistency validation.

• Deployment configuration: 4 storage instance (1 us-east-1, 1 us-east-2, 1 us-west-1, 1 us-west-2)
• Sync/Async nodes: 3 async nodes (localreplicanum=0, remotereplicanum=3, remotestorelatencythresholdinmillisec=0)
• Consistency validation setting: num_client=5, duration=20

Result: a client can get a value which is not existing in the redis backend. For example, in the following screenshot client 4 got a value 582. From the original log the corresponding revision number is 132. The returned value from the curl command for revision 132 is 311.

[jshaofuturewei]

Can you pull the revision history before running the consistency tests? Since consistent tests do not clear databases before running. The 137 value might be the old data entry as we verified it before.

[kxu1985]

This is an old issue posted one month ago. Yes, the 'non-existing' value is the old entry from previous tests. This issue is just kept for tracking for now.