Feature #2620: Keep supports I/O locking - Arvados

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)

Actions

Copy link

Updated by Ward Vandewege about 10 years ago

Assigned To set to Tim Pierce

Actions

Copy link

Updated by Tim Pierce about 10 years ago

Tracker changed from Bug to Feature
Subject changed from Keep I/O locking to Keep supports I/O locking

An admin should be able to enable I/O locking: a per-spindle lock that prevents Keep from reading or writing to more than one file at a time. I/O operations on different spindles may still be executed concurrently.

Actions

Copy link