Project

General

Profile

Actions
Copy link

Idea #7928

closed

[Keep] keepstore identifies underlying volumes to clients

Added by Brett Smith about 9 years ago. Updated over 7 years ago.

Status:
Duplicate
Priority:
Normal
Assigned To:
-
Category:
Keep
Target version:
-
Start date:
12/02/2015
Due date:
Story points:
-

Description

The problem today: Keep clients figure if they write a block to a Keepstore, that created X-Keep-Replicas-Stored unique copies (default 1). This assumption is broken when multiple Keepstores share underlying storage (e.g., an object store).

Make it possible for clients to know how many copies of the block exist on disk.

  • PUT responses should list which volume(s) the block was stored on, and how many copies live on each.
  • Index responses should list which volume(s) each block lives on, and how many copies live on that volume.

Related issues 5 (2 open — 3 closed)

Is duplicate of Arvados - Feature #11644: [keepstore] mount-oriented APIsResolvedTom Clegg05/09/2017Actions
Blocks Arvados - Idea #7929: [SDKs] PySDK KeepClient considers volume IDs when replicatingClosed12/02/2015Actions
Blocks Arvados - Idea #7930: [SDKs] GoSDK KeepClient considers volume IDs when replicatingNewActions
Blocks Arvados - Idea #7931: [keep-balance] Count block replication by volume IDsResolvedTom Clegg12/02/2015Actions
Blocks Arvados - Idea #7932: [Keep] keepproxy aggregates and reports volume IDs from KeepstoresNewActions
Actions
Copy link
 #1

Updated by Brett Smith about 9 years ago

  • Tracker changed from Bug to Idea
Actions
Copy link
 #2

Updated by Tom Clegg over 7 years ago

  • Status changed from New to Duplicate

covered by #11644

Actions
Copy link

Also available in: Atom PDF