Skip to content

Commit bd03512

Browse files
committed
delete repetition
1 parent b3d76e0 commit bd03512

File tree

1 file changed

+0
-3
lines changed
  • docs/reference/query-languages/esql/_snippets/commands/layout

1 file changed

+0
-3
lines changed

docs/reference/query-languages/esql/_snippets/commands/layout/completion.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -59,18 +59,15 @@ How you increase the timeout depends on your deployment type:
5959
:::{tab-item} {{ech}}
6060
* You can adjust {{es}} settings in the [Elastic Cloud Console](docs-content://deploy-manage/deploy/elastic-cloud/edit-stack-settings.md)
6161
* You can also adjust the `search.default_search_timeout` cluster setting using [Kibana's Advanced settings](kibana://reference/advanced-settings.md#kibana-search-settings)
62-
* The default timeout is 10 minutes
6362
:::
6463

6564
:::{tab-item} Self-managed
6665
* You can configure at the cluster level by setting `search.default_search_timeout` in `elasticsearch.yml` or updating via [Cluster Settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings)
6766
* You can also adjust the `search:timeout` setting using [Kibana's Advanced settings](kibana://reference/advanced-settings.md#kibana-search-settings)
6867
* Alternatively, you can add timeout parameters to individual queries
69-
* The default timeout is 10 minutes
7068
:::
7169

7270
:::{tab-item} {{serverless-full}}
73-
* The default timeout is 10 minutes
7471
* Requires a manual override from Elastic Support because you cannot modify timeout settings directly
7572
:::
7673
::::

0 commit comments

Comments
 (0)