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

Unicast Discovery: Concurrently connect to nodes to improve cases where some listed nodes are not up #855

Closed
kimchy opened this issue Apr 13, 2011 · 0 comments
Closed

Unicast Discovery: Concurrently connect to nodes to improve cases where some listed nodes are not up #855

kimchy opened this issue Apr 13, 2011 · 0 comments
Labels
>enhancement v0.16.0

Comments

@kimchy
Copy link
Member

kimchy commented Apr 13, 2011

Its better to concurrently connect to nodes, so when some nodes are not up, so the connection timeout will not be aggregated based on the number of nodes that are not up.
@kimchy kimchy closed this as completed in 25eba4b Apr 13, 2011
emilykmarx pushed a commit to emilykmarx/elasticsearch that referenced this issue Dec 26, 2023
@ppf2
Docs: back-port 9.4.0 changelog (elastic#855)
1bdcc80 
ilm_enabled's 'auto' setting was actually added in 9.4.0 (but the default remained 'false').  
10.0.0 is when we switched the default to 'auto'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>enhancement v0.16.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kimchy