vmware / vmware/splinterdb

During memtable incorporation, should acquire claims on both lookup lock and root before locking

Open
#132 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
732
Forks
67
PR merge metrics
No merged PRs in 30d

Description

This should reduce the amount of time that the lookup lock is held and therefore blocking memtable lookups while the root lock is being acquired.

Contributor guide

Open the contributing guide

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

Trace memtable incorporation and the lookup-lock and root-lock acquisition paths first. Determine how claims are currently acquired and verify that acquiring both claims before locking preserves correctness while reducing the time the lookup lock is held; the issue provides no file or test names.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
databases
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.