Feature #6417
closed
Call MN.archive() when SM.archive=true in MN.systemMetadataChanged()
Added by ben leinfelder almost 11 years ago.
Updated about 9 years ago.
Description
We decided the CN should not call MN.archive() when it harvests SM from nodes and tries to inform other replicas about the change. It will only alert them that sysMeta has been updated. So we can either update the flag on the MN replica, or we can call MN.archive() ourself in response.
If we don't call MN.archive() the object will continue to show up in Metacat API's pathquery.
- Description updated (diff)
- Assignee set to ben leinfelder
I added a comment in the code for where this could be done, but the actual method call is commented out.
In general this sounds good, but won't calling MN.archive() result in other side effects (like other changes to system metadata like the datsysmetamodified, and logging it as an ARCHIVE event locally)? When we are simply recording a change to an object that some other node initiated, we should try to do so without these side effects, as the change originated elsewhere and we are simply tracking it as a replica.
- Assignee changed from ben leinfelder to Jing Tao
- Status changed from New to In Progress
- Status changed from In Progress to Closed
This issue was fixed and tested.
Also available in: Atom
PDF