tikv / tikv/client-rust

Will pressure testing put on the same key with pessimistic transactions result in a write conflict error?

Open
#482 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
425
Forks
163
Avg merge
10h 51m
Merged PRs (30d)
3

Description

As stated in the title

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names pressure testing, pessimistic transactions, and concurrent writes to the same key, but provides no file, test, or entry point. First locate the transaction and conflict-handling tests, then reproduce the scenario; done means confirming whether a write-conflict error occurs and documenting the result or a clearly scoped fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
databases, distributed-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.