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

maxResultSetSize expressed in bytes #372

Open
paterczm opened this issue Jun 30, 2017 · 0 comments
Open

maxResultSetSize expressed in bytes #372

paterczm opened this issue Jun 30, 2017 · 0 comments

Comments

@paterczm
Copy link
Contributor

We have maxResultSetSize setting currently which defines maximum number of documents which can be returned in a single call. If the documents are large, it can still lead to OutOfMemory errors in the crud nodeset.

I would rename current maxResultSetSize to maxResultSetCount and introduce maxResultSetSizeB (in bytes) to put a cap on the response size and protect crud resources from exhaustion.

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

No branches or pull requests

1 participant