Update resolve/cluster end user docs with information about the timeout flag and no index expression endpoint #121199
Conversation
…out flag and no index expression endpoint
quux00
added
>docs
|
Documentation preview: |
|
Pinging @elastic/es-docs (Team:Docs) |
|
Pinging @elastic/es-search-foundations (Team:Search Foundations) |
| will show the cluster as not connected and include an error message that the | ||
| request timed out. The default timeout is unset and the query can take | ||
| as long as the networking layer is configured to wait for remote clusters that are | ||
| not responding (typically 30 seconds). |
There was a problem hiding this comment.
Should we mention the setting that influences this timeout?
There was a problem hiding this comment.
What is it and is it something the user can configure?
There was a problem hiding this comment.
transport.connect_timeout. It may or may not exist—if it doesn't, handshake defaults to 30s. On a second thought, maybe let's not mention it. If we unintentionally lead users to this setting and they modify it, it has an effect outside this API's scope—something that could be undesired.
| "cluster_three": { | ||
| "connected": false, | ||
| "skip_unavailable": false, | ||
| "error": "Request timed out before receiving a response from the remote cluster" <4> |
There was a problem hiding this comment.
Not for this patch, but I wonder if it'd help if the error message included the actual timeout value. So the user would know whether the cluster failed to respond in 1s (maybe the timeout too low?) or in 300s (definitely it's dead and also maybe timeout too long).
…out flag and no index expression endpoint (elastic#121199)
💚 Backport successful
|
5 participants
No description provided.