- Java REST Client (deprecated): other versions:
- Overview
- Java Low Level REST Client
- Java High Level REST Client
- Getting started
- Document APIs
- Search APIs
- Miscellaneous APIs
- Indices APIs
- Analyze API
- Create Index API
- Delete Index API
- Indices Exists API
- Open Index API
- Close Index API
- Shrink Index API
- Split Index API
- Refresh API
- Flush API
- Flush Synced API
- Clear Cache API
- Force Merge API
- Rollover Index API
- Put Mapping API
- Get Mappings API
- Get Field Mappings API
- Index Aliases API
- Exists Alias API
- Get Alias API
- Update Indices Settings API
- Get Settings API
- Put Template API
- Validate Query API
- Get Templates API
- Get Index API
- Cluster APIs
- Ingest APIs
- Snapshot APIs
- Tasks APIs
- Script APIs
- Licensing APIs
- Machine Learning APIs
- Put Job API
- Get Job API
- Delete Job API
- Open Job API
- Close Job API
- Update Job API
- Flush Job API
- Put Datafeed API
- Get Datafeed API
- Delete Datafeed API
- Preview Datafeed API
- Start Datafeed API
- Stop Datafeed API
- Get Datafeed Stats API
- Get Job Stats API
- Forecast Job API
- Delete Forecast API
- Get Buckets API
- Get Overall Buckets API
- Get Records API
- Post Data API
- Get Influencers API
- Get Categories API
- Get Calendars API
- Put Calendar API
- Delete Calendar API
- Migration APIs
- Rollup APIs
- Security APIs
- Watcher APIs
- Graph APIs
- Using Java Builders
- Migration Guide
- License
Cluster Update Settings API
editCluster Update Settings API
editThe Cluster Update Settings API allows to update cluster wide settings.
Cluster Update Settings Request
editA ClusterUpdateSettingsRequest
:
ClusterUpdateSettingsRequest request = new ClusterUpdateSettingsRequest();
Cluster Settings
editAt least one setting to be updated must be provided:
Providing the Settings
editThe settings to be applied can be provided in different ways:
String transientSettingKey = RecoverySettings.INDICES_RECOVERY_MAX_BYTES_PER_SEC_SETTING.getKey(); int transientSettingValue = 10; Settings transientSettings = Settings.builder() .put(transientSettingKey, transientSettingValue, ByteSizeUnit.BYTES) .build(); String persistentSettingKey = EnableAllocationDecider.CLUSTER_ROUTING_ALLOCATION_ENABLE_SETTING.getKey(); String persistentSettingValue = EnableAllocationDecider.Allocation.NONE.name(); Settings persistentSettings = Settings.builder() .put(persistentSettingKey, persistentSettingValue) .build();
Settings.Builder transientSettingsBuilder = Settings.builder() .put(transientSettingKey, transientSettingValue, ByteSizeUnit.BYTES); request.transientSettings(transientSettingsBuilder);
request.transientSettings( "{\"indices.recovery.max_bytes_per_sec\": \"10b\"}" , XContentType.JSON);
Optional Arguments
editThe following arguments can optionally be provided:
Timeout to wait for the all the nodes to acknowledge the settings were applied
as a |
|
Timeout to wait for the all the nodes to acknowledge the settings were applied
as a |
Synchronous Execution
editWhen executing a ClusterUpdateSettingsRequest
in the following manner, the client waits
for the ClusterUpdateSettingsResponse
to be returned before continuing with code execution:
ClusterUpdateSettingsResponse response = client.cluster().putSettings(request, RequestOptions.DEFAULT);
Asynchronous Execution
editExecuting a ClusterUpdateSettingsRequest
can also be done in an asynchronous fashion so that
the client can return directly. Users need to specify how the response or
potential failures will be handled by passing the request and a listener to the
asynchronous put-settings method:
The |
The asynchronous method does not block and returns immediately. Once it is
completed the ActionListener
is called back using the onResponse
method
if the execution successfully completed or using the onFailure
method if
it failed.
A typical listener for put-settings
looks like:
Cluster Update Settings Response
editThe returned ClusterUpdateSettingsResponse
allows to retrieve information about the
executed operation as follows:
On this page