Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle OP_MSG requests exceeding MaxMessageSizeBytes #67

Closed
domodwyer opened this issue Dec 12, 2017 · 0 comments
Closed

Handle OP_MSG requests exceeding MaxMessageSizeBytes #67

domodwyer opened this issue Dec 12, 2017 · 0 comments

Comments

@domodwyer
Copy link

domodwyer commented Dec 12, 2017

NOTE: this issue is for an experimental feature, and does not affect the production driver.


The OP_MSG specification states:

Each OP_MSG MUST NOT exceed the maxMessageSizeBytes as configured by the MongoDB Handshake.

Currently the experimental support for OP_MSG (contributed by @feliixx - thanks!) does not gracefully handle a message exceeding maxMessageSizeBytes - in the future this limit should be handled transparently by the driver.

In socket.go we return an error from sendMessage() when the limit is exceeded - ideally the driver should split the requests into messages that do not exceed this limit internally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant