Project

General

Profile

Actions
Copy link

Feature #4835

closed

Monitor: better handle aborted synchronizations

Added by Greg Farnum almost 11 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Correctness/Safety
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:
Component(RADOS):
Pull request ID:

Description

See #4812. That should not be an assert (graceful shutdowns!), and in that specific case we don't actually want to exclude the MDS which aborted anyway. Either it should have done a nicer abort (telling the sync requester to restart), or maybe the requester should be okay with going back to the aborter? I'm not really sure. Either way, this should be cleaned up, and if we can do so in a way that reduces the size of the interface, so much the better.

Actions
Copy link
 #1

Updated by Joao Eduardo Luis almost 7 years ago

  • Project changed from Ceph to RADOS
  • Category changed from Monitor to Correctness/Safety
  • Status changed from New to Resolved

The synchronization code has been overhauled a few times in the past few years. I believe this to have been resolved at some point.

Actions
Copy link

Also available in: Atom PDF