Setting a Metacat member node's synchronization false doesn't work.
In order to test the metadata editor form and avoid to create test documents on production CN, we set the synchronization false through the Metacat admin page. We didn't see any error. However, the test content was synchronized to the CN. We have to use the curl command to remove it from CNs.
#2 Updated by Jing Tao almost 5 years ago
- Category changed from d1_cn_node_registry to Metacat
- Status changed from New to Closed
- % Done changed from 0 to 100
The problem was in Metacat. In the d1Admin page, those properties were modified by the Metacat way - throught the properties service class. However, reading value is by the Dataone way - the Setting class. Those two properties were not synchronized. I added code the synchronize them after the modification of properties. It worked. The fix will be included in Metacat 2.7.2 and later release.