doc: take out w + n params, folks get confused. #4874
Conversation
There was a problem hiding this comment.
there's little utility to setting these, but they -do- work. what's missing from this text is the detail that couchdb will lower the r or w value provided if it knows a required node is down (missing from [node()|nodes()].), which is a distinct failure mode from 'only receive a response once all nodes ... have responded or timed out'.
I've a mild preference for simply correcting this documentation to match the real semantics (as above) rather than striking it.
Alternatively a Pull Request that strikes this text and removes the code that lets you set r and w in chttpd. the documentation then still matches the code.
There was a problem hiding this comment.
These are valid parameters. Wonder if there is a specific confusing point we can clarify perhaps?
Is this mostly about w=3? We could add a section about the common pitfalls about it , say if we use w=3 but you only two or one nodes up, or describe a scenario with how conflicts can still be generated, and difference between 201 and 202 responses for writes.
No description provided.