Environment:
1. MongoDB Enterprise 3.2.10 using Wired Tiger storage engine
2. Write concern set to W1 with Journal = true
3. Reads are done on the primary, not the replica set

The issue we are seeing is in a very short period (< 10 ms) a document is created in a collection and then queried back. On the query back (using _id field) the document is not found. If queried later by _id it is found.

Is this the expected behavior for Mongo 3.2.10? One observation was this issue starting occurring when we upgraded from 3.0 Mongo to 3.2 Mongo enterprise version.