IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Client Settings
edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.
Client Settings
editThe client used to connect to Google Cloud Storage has a number of settings available.
Client setting names are of the form gcs.client.CLIENT_NAME.SETTING_NAME and specified
inside elasticsearch.yml. The default client name looked up by a gcs repository is
called default, but can be customized with the repository setting client.
For example:
PUT _snapshot/my_gcs_repository
{
"type": "gcs",
"settings": {
"bucket": "my_bucket",
"client": "my_alternate_client"
}
}
Some settings are sensitive and must be stored in the elasticsearch keystore. This is the case for the service account file:
bin/elasticsearch-keystore add-file gcs.client.default.credentials_file /path/service-account.json
The following are the available client settings. Those that must be stored in the keystore
are marked as Secure.
-
credentials_file - The service account file that is used to authenticate to the Google Cloud Storage service. (Secure)
-
endpoint - The Google Cloud Storage service endpoint to connect to. This will be automatically determined by the Google Cloud Storage client but can be specified explicitly.
-
connect_timeout -
The timeout to establish a connection to the Google Cloud Storage service. The value should
specify the unit. For example, a value of
5sspecifies a 5 second timeout. The value of-1corresponds to an infinite timeout. The default value is 20 seconds. -
read_timeout -
The timeout to read data from an established connection. The value should
specify the unit. For example, a value of
5sspecifies a 5 second timeout. The value of-1corresponds to an infinite timeout. The default value is 20 seconds. -
application_name -
Name used by the client when it uses the Google Cloud Storage service. Setting
a custom name can be useful to authenticate your cluster when requests
statistics are logged in the Google Cloud Platform. Default to
repository-gcs