Skip to content

Getting Non-existing Value with Concurrent Operations  #81

Description

@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.

Screen Shot 2022-09-19 at 9 38 49 AM
Screen Shot 2022-09-19 at 9 39 56 AM

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions