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

Tcp Transport: Connection pool between nodes and different connection types #564

Closed
kimchy opened this issue Dec 15, 2010 · 1 comment
Closed

Comments

@kimchy
Copy link
Member

kimchy commented Dec 15, 2010

Some messages sent by one node to another requires high priority (such as the ping messages to detect liveness). Others require lower priority since they include large payloads (recovery, bulk), and the rest are, well, the rest.

Introduce connection pooling between one node and another, with high, low, and med. By default, high is set to 1, med is set to 7, and low is set to 2.

This mainly comes from the problem of sending big bulk requests on the same channel causing other messages to get delayed.

@kimchy
Copy link
Member Author

kimchy commented Dec 15, 2010

Tcp Transport: Connection pool between nodes and different connection types, closed by d6bab1a.

medcl pushed a commit to medcl/elasticsearch that referenced this issue Jul 1, 2011
emilykmarx pushed a commit to emilykmarx/elasticsearch that referenced this issue Dec 26, 2023
Fixes elastic#515 by removing the accidentally-unhelpful log message that was
smply logging "Action" with no context.
This issue was closed.
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