You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2021/10/28 17:16:47 UTC
[GitHub] [couchdb] jaydoane commented on issue #3806: custodian hard-codes `dbs` db instead of the configured shards db
jaydoane commented on issue #3806:
URL: https://github.com/apache/couchdb/issues/3806#issuecomment-954043895
> 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.
Custodian is opinionated about how many copies of data you have in a cluster, which seems like a good thing in general. But I can see how it would get annoying to have `critical` log messages when you know what you're doing with low `n` dbs.
Perhaps we could make a `[custodian] unsafe_log_level = critical` config option which would allow those more comfortable with potential data loss change it to something less scary?
--
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: notifications-unsubscribe@couchdb.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org