# Improving resiliency or changing settings of system indices

**URL:** https://discuss.elastic.co/t/improving-resiliency-or-changing-settings-of-system-indices/326108
**Category:** Elasticsearch
**Created:** [February 21, 2023, 10:32pm UTC](https://discuss.elastic.co/t/improving-resiliency-or-changing-settings-of-system-indices/326108 "2023-02-21T22:32:00Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![garethhumphriesgkc](https://avatars.discourse-cdn.com/v4/letter/g/eb8c5e/32.png) [@garethhumphriesgkc](https://discuss.elastic.co/u/garethhumphriesgkc)
#### Post date: [February 21, 2023, 10:32pm UTC](https://discuss.elastic.co/t/improving-resiliency-or-changing-settings-of-system-indices/326108/1 "2023-02-21T22:32:00Z")

</div>

Hi,

I'm trying to improve the resiliency of my elastic stack. I want to make it tolerant to any two node failures, but I can't update system indices to have more than one replica.

The setting in question is `index.auto_expand_replicas` - I'd like to make this for example `0-2` instead of `0-1`, but when I try I get:

```auto
PUT /.kibana_7.17.2_001/_settings
{"index.auto_expand_replicas":"0-2"}

{
  "type":"security_exception",
  "reason":"action [indices:admin/settings/update] is unauthorized for user [<user>] with effective roles [kibana_admin,kibana_monitoring,modify_system_indices,monitoring_user,superuser] on restricted indices [.kibana_7.17.2_001], this action is granted by the index privileges [manage,all]"
}

```

As you can see, I've created a role to grant `all` to `.*` in an attempt to explicitly allow it, but still no dice.

Is there any way I can modify these settings?

There are some other settings I'd like to be able to change too, so I can control the addition of new data nodes to my cluster - right now I can't control when system indices get allocated to a new node, so I have to just hope everything goes well rather than cut indices across slowly.

Any tips on how I can change settings on system indices much appreciated.

---

<div class="post-metadata">

### Author: ![garethhumphriesgkc](https://avatars.discourse-cdn.com/v4/letter/g/eb8c5e/32.png) [@garethhumphriesgkc](https://discuss.elastic.co/u/garethhumphriesgkc)
#### Post date: [March 1, 2023, 1:31am UTC](https://discuss.elastic.co/t/improving-resiliency-or-changing-settings-of-system-indices/326108/2 "2023-03-01T01:31:05Z")

</div>

Seems no-one else has any ideas either. Does that mean that, fundamentally, Elasticsearch just doesn't support any better than N+1 resiliency?

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [March 1, 2023, 1:43am UTC](https://discuss.elastic.co/t/improving-resiliency-or-changing-settings-of-system-indices/326108/3 "2023-03-01T01:43:47Z")

</div>

AFAIK we don't support changing things for system indices as they will be overwritten the next time you upgrade.

That's probably not what you want to hear sorry, I would suggest raising a feature request on GitHub to see what can be done.

---

<div class="post-metadata">

### Author: ![garethhumphriesgkc](https://avatars.discourse-cdn.com/v4/letter/g/eb8c5e/32.png) [@garethhumphriesgkc](https://discuss.elastic.co/u/garethhumphriesgkc)
#### Post date: [March 1, 2023, 1:45am UTC](https://discuss.elastic.co/t/improving-resiliency-or-changing-settings-of-system-indices/326108/4 "2023-03-01T01:45:22Z")

</div>

Not ideal, but nice to get confirmation I'm not missing something.

Sure thing, I'll raise an FR. Thanks for responding.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 29, 2023, 1:46am UTC](https://discuss.elastic.co/t/improving-resiliency-or-changing-settings-of-system-indices/326108/5 "2023-03-29T01:46:17Z")

</div>

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