You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 10, 2020. It is now read-only.
As reported here moscajs/mosca#102, MongoAscoltatore skips some messages, as the ObjectID (which are used internally) can be unordered in the same second.
The relationship between the order of ObjectId values and generation time is not strict within a single second. If multiple systems, or multiple processes or threads on a single system generate values, within a single second; ObjectId values do not represent a strict insertion order. Clock skew between clients can also result in non-strict ordering even for values, because client drivers generate ObjectId values, not the mongod process.
As reported here moscajs/mosca#102, MongoAscoltatore skips some messages, as the ObjectID (which are used internally) can be unordered in the same second.
from http://docs.mongodb.org/manual/reference/object-id/
The text was updated successfully, but these errors were encountered: