Project

General

Profile

Actions
Copy link

Feature #2620

closed

Keep supports I/O locking

Added by Tim Pierce about 10 years ago. Updated almost 10 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Tim Pierce
Category:
-
Target version:
2014-05-07 Storing and Organizing Data
Story points:
2.0

Description

Notes:
  • Lock is per-volume. It's the sysadmin's problem to ensure volumes don't share a spindle.
  • Lock is in-process (not flock). It's the sysadmin's problem to ensure keep servers don't share a volume.
  • Enable per-volume lock with -serialize flag.
  • Exempt from lock behavior: HEAD, index, and the process of discovering whether a block is present during a GET or PUT. In other words, we aren't strictly limiting IO to one client per spindle: we're assuming the OS has good enough cache behavior to support hordes of readdir operations alongside a big read/write without (statistically) causing thrash.

Subtasks 3 (0 open — 3 closed)

Task #2695: Review 2620-keep-serialize-ioResolvedTim Pierce04/01/2014Actions
Task #2629: I/O locking unit testsResolvedTim Pierce04/01/2014Actions
Task #2560: Serialize Keep I/OResolvedTim Pierce04/01/2014Actions
Actions
Copy link

Also available in: Atom PDF