Hi,
In the mongo wire protocol I see there is a field requestID which is the identifier for the packet. How is this requestID 32 bit value generated? Will this value be re-used in a later (but unrelated) packet?
Thank you!
Hi,
In the mongo wire protocol I see there is a field requestID which is the identifier for the packet. How is this requestID 32 bit value generated? Will this value be re-used in a later (but unrelated) packet?
Thank you!
Hey @Kartik_Pattaswamy1 ,
Though it’s typically just an auto-incremented integer there aren’t really any requirements as to its generation. Since currently only a single operation can occur per connection the requestID
generated by the client will just be reflected in the responseTo
from the server.
A requestID
wouldn’t be reused for any purpose other than a client being restarted and the value generation being reset.
Topic | Replies | Views | Activity |
---|---|---|---|
Using IMongoQueryable on unit tests for Async methods | 1 | 1.1k | Jun 2024 |
Atomic write to multiple records | 0 | 455 | May 2024 |
Compile error when building Mongocxx driver with gcc-14 | 2 | 442 | Jul 2024 |
Updating Data with Entity Framework Core | 4 | 258 | Sep 2024 |
Darshan Hiranandani : Has anyone tried disabling writeConcern acknowledgment to improve performance? What were the results? | 1 | 49 | Sep 2024 |