Index level settings are wiped-out from v5.2.2

Elastic Stack Elasticsearch
1

Hello techies
we are using elasticsearch 2.1.0(centos7) servers on production.
we want to upgrade to v5.2.2 very soon.
Following parameters are using while creating new indexes.
index.translog.flush_threshold_ops: 100000
index.number_of_shards: 5
index.number_of_replicas: 1
index.refresh_interval: 60s
Q: index.translog.flush_threshold_ops option is deprecated from v5.0.0
can you please suggest alternative for above?

2

You can update those settings as below:

PUT /twitter/_settings
{
    "index" : {
        "translog.flush_threshold_ops" : 100000
    }
}

More over you can refer the docs here.
https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-update-settings.html

3

Following error observed while applying threshold settings.

{
"error": {
"root_cause": [
{
"type": "illegal_argument_exception",
"reason": "unknown setting [index.translog.flush_threshold_ops] did you mean [index.translog.flush_threshold_size]?"
}
],
"type": "illegal_argument_exception",
"reason": "unknown setting [index.translog.flush_threshold_ops] did you mean [index.translog.flush_threshold_size]?"
},
"status": 400
}

i want to use index level setting using JAVA API

4

`The index.translog.[quote="kishore419, post:3, topic:81975"]
"reason": "unknown setting [index.translog.flush_threshold_ops] did you mean

See here : https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking_50_settings_changes.html#_translog_settings

The index.translog.flush_threshold_ops setting is not supported anymore. In order to control flushes based on the transaction log growth use index.translog.flush_threshold_size instead.

5

it works for me
thanks prashant.

1 Like
6

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.