Project

General

Profile

Story #7807

cn.synchronize should support synchronization failure corrections.

Added by Rob Nahf over 5 years ago. Updated almost 4 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Architecture Design
Target version:
-
Start date:
2016-05-13
Due date:
% Done:

0%

Story Points:

Description

cn.synchronize(session, identifier) works well for its original purpose (supporting MN-driven system metadata updates, and MN-driven push synchronization), but doesn't seem to work for manual synchronization failure workflows. The main problem is that the request can only be made by the MN itself (using the MN client certificate).

As we envision a centralized dashboard for monitoring failed synchronization items, how do we address this situation?

The synchronization processing queue needs both the pid and a nodeId from where to retrieve the object. the NodeId is not specified directly in the method call, but gleaned from the session by a reverse lookup from the certificate. (It uses the first node found in the NodeList where the Node.subject field matches the certificate subject).

Should we allow node.contactSubjects into the algorithm?
Should we add nodeId as a parameter?

History

#1 Updated by Dave Vieglais almost 4 years ago

  • Sprint set to Infrastructure backlog

#2 Updated by Dave Vieglais almost 4 years ago

  • Priority changed from Normal to Low

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)