If the fragment needing to be reconstructed already exists, let the handoff node push it to the primary.

Bug #1469815 reported by Minwoo Bae
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Object Storage (swift)
Confirmed
Medium
Unassigned

Bug Description

In a previous patch (#193279), a fix was made to prevent the reconstructor from rebuilding a fragment from a list of fragments that contains itself, by omitting the response from the list. However, we should go further and prevent the reconstruction so that the handoff may push the duplicate frag to its proper location.

Tags: ec
Minwoo Bae (minwoob)
Changed in swift:
assignee: nobody → Minwoo Bae (minwoob)
Minwoo Bae (minwoob)
Changed in swift:
status: New → In Progress
Changed in swift:
importance: Undecided → Low
Revision history for this message
John Dickinson (notmyname) wrote :
Changed in swift:
importance: Low → Medium
Revision history for this message
Tim Burke (1-tim-z) wrote :

That patch has been submitted as https://review.openstack.org/#/c/389676/ but seems stalled... I think it's fair to say this isn't currently "In-Progress"?

Changed in swift:
status: In Progress → Confirmed
assignee: Minwoo Bae (minwoob) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.