I have an issue with GridFS (See https://jira.mongodb.org/browse/CXX-2148 for details) where writes on the secondary seemed to be applied in arbitrary order, more specifically chunks of a given document are not readable while the files entry already is, despite the fact that (AFAIU) chunks are written before the files entry.
The documentation states that “MongoDB provides monotonic write guarantees, by default, for standalone instances and replica set”. Doesn’t that mean that write order on the primary are replicated in the same order on secondaries if there is no sharding ?
Or maybe it does but it’s not reflected from the point of view of a reader of those writes ?
I see that there is causally consistent client session that could be used to provide stronger guarantee but I’d like to be sure I understand correctly the default behavior in my case.
Thanks in advance.
Env: mongo 4.2, cluster with 6 replicas, no sharding.