You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: deploy-manage/autoscaling/trained-model-autoscaling.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -133,8 +133,8 @@ In case of ingest-optimized deployments, we maximize the number of model allocat
133
133
| Level | Allocations | Threads | VCUs |
134
134
| --- | --- | --- | --- |
135
135
| Low | 0 to 2 dynamically | 1 | 0 to 16 dynamically |
136
-
| Medium |1 to 32 dynamically | 1 | 8 to 256 dynamically |
137
-
| High |1 to 512 for Search<br> 1 to 128 for Security and Observability<br> | 1 | 8 to 4096 for Search<br> 8 to 1024 for Security and Observability<br> |
136
+
| Medium |0 to 32 dynamically | 1 | 8 to 256 dynamically |
137
+
| High |0 to 512 for Search<br> 1 to 128 for Security and Observability<br> | 1 | 8 to 4096 for Search<br> 8 to 1024 for Security and Observability<br> |
Copy file name to clipboardExpand all lines: deploy-manage/deploy/self-managed/install-elasticsearch-docker-configure.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -124,6 +124,7 @@ If you’ve already created the keystore and don’t need to update it, you can
124
124
-e KEYSTORE_PASSWORD=mypassword
125
125
```
126
126
127
+
When you upgrade your cluster to a newer version, {{es}} will attempt to automatically upgrade the `elasticsearch.keystore` file to match. However, bind-mounted files are read-only, so {{es}} cannot automatically upgrade a bind-mounted `elasticsearch.keystore` file. Instead, if you are bind-mounting the `elasticsearch.keystore` file directly, you must use the `bin/elasticsearch-keystore upgrade` command to manually upgrade each node's keystore when you upgrade that node.
127
128
128
129
## Using custom Docker images [_c_customized_image]
Copy file name to clipboardExpand all lines: deploy-manage/tools/snapshot-and-restore/s3-repository.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -125,6 +125,9 @@ The following list contains the available S3 client settings. Those that must be
125
125
`max_retries`
126
126
: The number of retries to use when an S3 request fails. The default value is `3`.
127
127
128
+
`connection_max_idle_time`
129
+
: ([time value](elasticsearch://reference/elasticsearch/rest-apis/api-conventions.md#time-units)) The timeout after which {{es}} will close an idle connection. The default value is 60 seconds.
130
+
128
131
`path_style_access`
129
132
: Whether to force the use of the path style access pattern. If `true`, the path style access pattern will be used. If `false`, the access pattern will be automatically determined by the AWS Java SDK (See [AWS documentation](https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/AmazonS3Builder.html#setPathStyleAccessEnabled-java.lang.Boolean-) for details). Defaults to `false`.
0 commit comments