Project

General

Profile

Actions
Copy link

Bug #16852

open

[keep-balance] replication level distribution should account for volumes' built-in replication

Added by Tom Clegg over 3 years ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
Future
Story points:
-
Release:
Postponed
Release relationship:
Auto

Description

In olden days, the replication level distribution (logged by keep-balance after each run) reflected the underlying storage device's replication.

This was changed in #15305, perhaps inadvertently, while fixing the byte counters.

We should restore the old behavior, so if 2 blocks are stored on 1 volume that has underlying replication 3, and 2 other blocks are stored on 1 volume that has underlying replication 1, the logged distribution looks like this:

0: 0
1: 2
2: 0
3: 2
Actions
Copy link
 #1

Updated by Peter Amstutz almost 3 years ago

  • Target version deleted (Arvados Future Sprints)
Actions
Copy link
 #2

Updated by Peter Amstutz about 1 year ago

  • Release set to 60
Actions
Copy link
 #3

Updated by Peter Amstutz about 2 months ago

  • Target version set to Future
Actions
Copy link

Also available in: Atom PDF