Project

General

Profile

Bug #7917

Fix the issue that the system data exists but the bytes doesn't exist for an object on CN after synchronization

Added by Jing Tao about 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Metacat
Target version:
Start date:
2016-10-21
Due date:
% Done:

100%

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

Description

We have an odd situation to correct in production where an object system metadata is present but the document is not present in /var/metacat/data on any CN. We should avoid this scenario.


Related issues

Related to CN REST - Bug #7918: SEAD object only partially synchronized - missing autogen.2016092916012224122 document from /var/metacat/documents New 2016-10-21

History

#1 Updated by Dave Vieglais about 6 years ago

  • Target version changed from CCI-2.3.0 to CCI-2.3.1

Moved this to v2.3.1 to avoid blocking deployment of 2.3.0

#2 Updated by Jing Tao about 6 years ago

Dave confirmed that the identifier table had the guid and docid (autogen) for this object.

#3 Updated by Dave Vieglais about 6 years ago

  • Related to Bug #7918: SEAD object only partially synchronized - missing autogen.2016092916012224122 document from /var/metacat/documents added

#4 Updated by Jing Tao almost 6 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

In the end of create method, we will check if the local files which contain the bytes do exist or not. If not, the systemmetadata will be removed.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)