On 27 December 2017 at 19:58, Sebastian Rothbucher < [email protected]> wrote:
> Hi Damjan, > > thanks for reaching out - and yes, there is an explanation for this thing - > e.g. here https://blog.couchdb.org/2016/08/01/couchdb-2-0-architecture/ > and > here https://blog.couchdb.org/2016/08/17/migrating-to-couchdb-2-0/ (search > for 'changes'). Long story short: as CouchDB is clustered by default, it > does its best to consolidate from several shards which might cause the > shuffle you experience. Esp. for documents with close timestamps. > > Ad-hoc, I'm not sure about the docs right now. But as you stumbled: can you > open an issue or PR for the doc page in question, that would really help a > lot... > What is not clear from those blog posts (and the official documentation seems to further the confusion) is if that applies to single-node 2.x instances too. (ps. those were not documents with close timestamps - they were hours appart) I guess the docs are just plain wrong now at this time? -- damjan
