Project

General

Profile

Bug #7666

mnTestMPC repeating attempts to set replica status to FAILED

Added by Robert Waltz almost 6 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
Environment.Stage1
Target version:
Start date:
2016-02-25
Due date:
% Done:

0%

Milestone:
None
Product Version:
*
Story Points:
Sprint:

Description

On staging many objects were replicated by mnTestMPC. They appeared to have been successfully replicated, yet mnTestMPC appears to be attempting to set them all to FAILED on the CN, after having set them on the CN to COMPLETED. The objects on mnTestMPC appear valid.

For instance, the pid aekos.org.au/collection/nsw.gov.au/nsw_atlas/vis_flora_module/WWBPCOBAR.20150515 began replicating to mnTestMPC on (or very close to) 2016-02-24 23:47:41 .

mnTestMPC called to the CN with /cn/v1/replicaNotifications (CNReplication.setReplicationStatus) on 2016-02-24 23:49:19 and set the status to 'COMPLETED'

after this call, mnTestMPC has been repeatedly calling to the CN with /cn/v1/replicaNotifications attempting to set the status to 'FAILED'.

the first call with FAILED occurred at 2016-02-24 23:49:20, one second after the first successful call.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)