nickva edited a comment on issue #3806: URL: https://github.com/apache/couchdb/issues/3806#issuecomment-953931347
Using the correctly configured shards db seems to work. However it also produces some noise in the logs for n=1 and n=2 dbs ``` [notice] 2021-10-28T14:04:51.453035Z [email protected] <0.3689.0> d1af8be8bd 127.0.0.1:15984 127.0.0.1 adm PUT /db2?q=1&n=2 201 ok 288 [notice] 2021-10-28T14:05:57.258774Z [email protected] <0.4773.0> 26625fe22a 127.0.0.1:15984 127.0.0.1 adm PUT /db2?q=1&n=3 412 ok 1 [notice] 2021-10-28T14:06:05.118009Z [email protected] <0.4903.0> 29e9834ffa 127.0.0.1:15984 127.0.0.1 adm PUT /db3?q=1&n=3 201 ok 339 [critical] 2021-10-28T14:06:05.120958Z [email protected] <0.4957.0> -------- 1 shard in cluster with only 1 copy on nodes that are currently up [critical] 2021-10-28T14:06:05.121009Z [email protected] <0.4957.0> -------- 1 shard in cluster with only 1 copy on nodes not in maintenance mode [critical] 2021-10-28T14:06:05.121055Z [email protected] <0.4957.0> -------- 1 shard in cluster with only 2 copies on nodes that are currently up [critical] 2021-10-28T14:06:05.121111Z [email protected] <0.4957.0> -------- 1 shard in cluster with only 2 copies on nodes not in maintenance mode ``` If users specify n=1 or n=2 it should not generate critical errors, so custodian would need to handle those cases before being enabled properly. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
