Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

non existent setting not removeable but still in cluster #28524

Closed
scratchy opened this issue Feb 5, 2018 · 2 comments
Closed

non existent setting not removeable but still in cluster #28524

scratchy opened this issue Feb 5, 2018 · 2 comments

Comments

@scratchy
Copy link

scratchy commented Feb 5, 2018

After rolling upgrade from 6.0.0 to 6.1.3 im having issues to update cluster settings

for example running this

curl -XPUT 'localhost:9200/_cluster/settings?pretty' -H 'Content-Type: application/json' -d'
{
  "transient": {
    "cluster.routing.allocation.enable": "all"
  }
}
'

results in:

{
  "error" : {
    "root_cause" : [
      {
        "type" : "remote_transport_exception",
        "reason" : "[search-8][xxx:9300][cluster:admin/settings/update]"
      }
    ],
    "type" : "illegal_argument_exception",
    "reason" : "unknown setting [indices.store.throttle.max_bytes_per_sec] did you mean [indices.recovery.max_bytes_per_sec]?"
  },
  "status" : 400
}

tried to remove (set indices.store.throttle.max_bytes_per_sec to null) which complains with 'its not valid since its not there anymore as well as removing the upper level with):

curl -XPUT 'localhost:9200/_cluster/settings?pretty' -H 'Content-Type: application/json' -d'
{
  "persistent": {
    "indices.store.*" : null
  }
}
'

which gets acked:

{
  "acknowledged" : true,
  "persistent" : { },
  "transient" : { }
}

but still the error from above persists. I'm unable to update any cluster settings right now (because all of them complaining with the error above)

Any idears?

@scratchy
Copy link
Author

scratchy commented Feb 5, 2018

curl -XPUT 'localhost:9200/_cluster/settings?pretty' -H 'Content-Type: application/json' -d'
{ "persistent": { "*": null},"transcient:": {"*": null}}'

{
  "error" : {
    "root_cause" : [
      {
        "type" : "remote_transport_exception",
        "reason" : "[search-8][xxx:9300][cluster:admin/settings/update]"
      }
    ],
    "type" : "illegal_argument_exception",
    "reason" : "unknown setting [indices.store.throttle.max_bytes_per_sec] did you mean [indices.recovery.max_bytes_per_sec]?"
  },
  "status" : 400
}

@polyfractal
Copy link
Contributor

I believe this is a duplicate of #28026? E.g. known bug, and some deprecated settings weren't added to the "archived" set (#28026 (comment)) which needs fixing.

Closing in favor of #28026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants