Call MN.archive() when SM.archive=true in MN.systemMetadataChanged()
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.
Updated by Matt Jones over 9 years ago
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.