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 |
---|---|---|---|
Can not access a MongoDB datastore with multiple instances. | 1 | 632 | May 2024 |
How to toggle bool field in an array of documents in Golang? | 1 | 685 | Aug 2024 |
Using IMongoQueryable on unit tests for Async methods | 1 | 1.1k | Jun 2024 |
MongoDB Cursor Error Spike After Spring Boot Upgrade | 0 | 77 | Nov 2024 |
CRUD operation fails with Bson Serialization Exception | 3 | 253 | Jan 15 |