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.

Sign up for GitHub

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

Jump to bottom

Provided upper bound on batch-size to ensure buffer-overruns and request timeouts don't occur. #113

Open
brianoliver opened this issue Apr 28, 2014 · 2 comments
Open

Provided upper bound on batch-size to ensure buffer-overruns and request timeouts don't occur. #113

brianoliver opened this issue Apr 28, 2014 · 2 comments
Assignees
@brianoliver
Labels
Module: Event Distribution Pattern Priority: Major Type: Improvement
Milestone
11-FUTURE

Comments

@brianoliver
Copy link
Contributor

When an batch-size is configure to an extremely large size, combined with very large cache entries, long inter-batch delays and/or high-latency networks, it's possible to create a RemoteInvocationRequest that may saturate a network, cause BrokenPipes, dropped Connections and/or RequestTimeOuts.

To resolve this we should measure and limit the size of batches (or make it automatic).
@brianoliver
Copy link
Contributor Author

Reported by @brianoliver

@brianoliver brianoliver added this to the 11-FUTURE milestone Jun 30, 2016
@brianoliver brianoliver self-assigned this Jun 30, 2016
@brianoliver
Copy link
Contributor Author

This issue was imported from JIRA COHINC-113

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@brianoliver brianoliver

Labels
Module: Event Distribution Pattern Priority: Major Type: Improvement
Projects
None yet
Milestone
11-FUTURE
Development

No branches or pull requests
1 participant
@brianoliver