Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Protection of sources too strict in the reaper #1637

Open
bari12 opened this issue Oct 11, 2018 · 0 comments

Comments

@bari12
Copy link
Member

commented Oct 11, 2018

Motivation

Currently the reaper is over-protective with the protection of sources if a transfer is active. All possible sources of an active transfer are not eligible for deletion, which is too protective, if there are many possible sources.
This should be changed to:

  • If only 1 source is available, protect it --> behaviour stays as it is
  • If 2 or more sources are available, all are eligible for deletion, except the one with the alphabetically first RSE (or the one which is oldest) - some shared knowledge so that multiple reapers would not accidentally delete the 2 remaining sources.

This was discussed in the dev meeting on 2018-10-11

@bari12 bari12 added Deletion and removed Dataset deletion labels Oct 11, 2018

@bari12 bari12 referenced this issue Mar 29, 2019
1 of 11 tasks complete
bari12 added a commit that referenced this issue Jul 9, 2019
Merge pull request #2641 from cserf/patch-2444-Reaper_2_0_outer_loop_…
…_Creation_of_list_of_RSES_to_delete_on_and_list_unlocked_replicas_changes

Reaper 2.0 outer loop: Creation of list of RSES to delete on and list_unlocked_replicas changes : Closes #2444, #1637, #1804, #2266
bari12 added a commit that referenced this issue Jul 9, 2019
Merge pull request #2642 from cserf/patch-2444-Reaper_2_0_outer_loop_…
…_Creation_of_list_of_RSES_to_delete_on_and_list_unlocked_replicas_changes

Reaper 2.0 outer loop: Creation of list of RSES to delete on and list_unlocked_replicas changes : Closes #2444, #1637, #1804, #2266
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
4 participants
You can’t perform that action at this time.