Caliper Fabric Connectors to support reporting of MVCC Read Conflicts to allow workload modules to detect

Open davidkel opened this issue 3 years ago • 1 comments

workload modules may want to benchmark different retry strategies if an MVCC Read Conflict is received. These are reported as errors and so they may want to not report those as failures (which would require a connector specific property to handle) but also the connectors would need to ensure a workload module can determine it from the returned txStatus in a consistent manner regardless of the fabric connector used.

Jun 18 '22 10:06 davidkel

We also want to consider a PHANTOM_READ_CONFLICT commit failure similarly. Also investigate if it's possible to get a situation where proposal responses don't match as an error

Mar 14 '23 08:03 davidkel