Github user rnewson commented on the pull request:
https://github.com/apache/couchdb-mem3/pull/11#issuecomment-125153544
The problem with changing N is forgetting to change up back up when adding
nodes. Silently making N=1 dbs when you have one node is infinitely preferable
to making N=1 dbs when you have three nodes or more.
The reason we log is so that the observant admin can notice that they
didn't join their multi-node cluster up properly, but I don't think it's a very
good mechanism.
Of all the options, the best one is to leave things as they are. Someone
with a single node 'cluster' will see warnings for this and learn to ignore
them (since they don't apply to them). For everyone else, it helps them avoid a
data loss scenario.
The second best option is to remove the warning, which is what I advocate
for given the number of voices that dislike the warning.
All other options involve more work and just change one compromise into
another one.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
