arifcse019 opened a new issue #1611: Bad Security Object Error After Moving Shards URL: https://github.com/apache/couchdb/issues/1611 Security objects for some databases fail to sync properly in a new node after all shards are moved from an old node. ## Expected Behavior Security objects for all databases should sync when shards are moved to a new node ## Current Behavior Security objects for some databases fail to sync properly in a new node after all shards are moved from an old node. The log says things like: " [error] 2018-09-19T17:24:05.388202Z couchdb@first.couchcluster.internal <0.19944.2> -------- Bad security object in <<"db-name">>: [{{[{<<"_id">>,<<"_security">>},{<<"admins">>,{[{<<"names">>,[]},{<<"roles">>,[]}]}},{<<"members">>,{[{<<"names">>,[<<"user-name">>]},{<<"roles">>,[]}]}}]},13},{{[]},7}] " ## Steps to Reproduce (for bugs) 1. Add a new node to the cluster 2. Move All Shards from an old node to this new one 3. Shut down and delete the old node 4. Verify Security Objects on all databases ## Context We are trying to replace couch cluster instances with new instances as part of preparing for a scenario where one instance can go away abruptly ## Your Environment * Version used: Couch 2.1.2, 3 node cluster
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
