Project

General

Profile

Actions

Feature #17350

closed

[keep-balance] Expected behaviour with different "replicas_desired" and "storage_classes_desired" values

Added by Nico César over 1 year ago. Updated over 1 year ago.

Status:
Rejected
Priority:
Normal
Assigned To:
-
Category:
Keep
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

Note: for this ticket examples the assumption is that there are 600 blocks equally distributed in the volumes.

Goals of this ticket:
  • to have all the expected behaviour for keep-balance
  • to add to the documentation this behaviour
  • to add necesary tests to make sure we comply with this behaviour

Volumes scenario

Scenario 1
---
Clusters:
  test1:
    Collections:
      DefaultReplication: 1
    Volumes:
      test1-nyw5e-000000000000000:
        AccessViaHosts:
          'http://keep0:25107': {}
      test1-nyw5e-111111111111111:
        AccessViaHosts:
          'http://keep1:25108': {}

Scenario 2
---
Clusters:
  test1:
    Collections:
      DefaultReplication: 1
    Volumes:
      test1-nyw5e-000000000000000:
        AccessViaHosts:
          'http://keep0:25107': {}
      test1-nyw5e-111111111111111:
        AccessViaHosts:
          'http://keep1:25108': {}
        StorageClasses:
          archival: true

Scenario 3
---
Clusters:
  test1:
    Collections:
      DefaultReplication: 1
    Volumes:
      test1-nyw5e-000000000000000:
        AccessViaHosts:
          'http://keep0:25107': {}
      test1-nyw5e-111111111111111:
        AccessViaHosts:
          'http://keep1:25108': {}
        StorageClasses:
          archival: true
        Read-Only

Expected result after tunnign keep balance

Volumes scenario Expected result after keep-balance run
1 300 blocks in each volume
2 600 blocks in test1-nyw5e-000000000000000 and 600 blocks in test1-nyw5e-111111111111111
3 600 blocks in test1-nyw5e-000000000000000 and 300 blocks in test1-nyw5e-111111111111111

To be talked in next grooming session (Feb 16th)

  • What are the common usecase ?
  • What other scenarios we care about?
  • How we address the process of changing configuration and re-running keep-balance?

Related issues

Related to Arvados Epics - Story #16107: Storage classesResolved03/01/202109/30/2021

Actions
Blocked by Arvados - Feature #17349: [Keep API] Revisit "replicas_desired" and "storage_classes_desired".Rejected

Actions
Actions #1

Updated by Nico César over 1 year ago

Actions #2

Updated by Nico César over 1 year ago

  • Description updated (diff)
Actions #3

Updated by Nico César over 1 year ago

  • Description updated (diff)
Actions #4

Updated by Nico César over 1 year ago

  • Blocked by Feature #17349: [Keep API] Revisit "replicas_desired" and "storage_classes_desired". added
Actions #5

Updated by Nico César over 1 year ago

  • Description updated (diff)
Actions #6

Updated by Nico César over 1 year ago

  • Description updated (diff)
Actions #7

Updated by Nico César over 1 year ago

  • Description updated (diff)
Actions #8

Updated by Nico César over 1 year ago

  • Target version set to To Be Groomed
  • Category set to Keep
  • Description updated (diff)
Actions #9

Updated by Nico César over 1 year ago

  • Description updated (diff)
Actions #10

Updated by Nico César over 1 year ago

  • Description updated (diff)
  • Subject changed from [keep-balance] Collection effective value and storage tiers to [keep-balance] Expected behaviour with different "replicas_desired" and "storage_classes_desired" values
Actions #11

Updated by Nico César over 1 year ago

  • Description updated (diff)
Actions #12

Updated by Peter Amstutz over 1 year ago

  • Status changed from New to Rejected
Actions

Also available in: Atom PDF