# Elasticsearch CCR, former follower (leader) index is not writable

**URL:** <https://discuss.elastic.co/t/elasticsearch-ccr-former-follower-leader-index-is-not-writable/292962>\
**Category:** Elasticsearch\
**Tags:** ccr-cross-cluster-replication, ccs-cross-cluster-search\
**Created:** [December 27, 2021, 9:05am UTC](https://discuss.elastic.co/t/elasticsearch-ccr-former-follower-leader-index-is-not-writable/292962 "2021-12-27T09:05:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Armen\_Petrosyan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/armen_petrosyan/32/80330_2.png) [@Armen\_Petrosyan](https://discuss.elastic.co/u/Armen_Petrosyan)\
**Post date:** [December 27, 2021, 9:05am UTC](https://discuss.elastic.co/t/elasticsearch-ccr-former-follower-leader-index-is-not-writable/292962/1 "2021-12-27T09:05:05Z")

</div>

I use **ES 7.7.1**

Below UC that I am trying to test:

1. I have two clusters leader and follower. On leader I have created index, and alias.
2. Starting follow process, I see that index replicated to the follower as well as alias. Everything is good.
3. I am starting unfollowing process (pause, close, unfollow, open)

**Expected**  
Two different 'leader' clusters. I have an ability to write to former follower (leader) as well as to original leader.

**Actual**  
I try to index some document to former follower (leader), I am getting error saying that index is not writable.

**Investigation**  
I starting to check indices and see that in original cluster

```auto
{
"aliases": {}
}

```

However in follower cluster I see

```auto
  }
  "aliases": {
    "MyIndex": {
      "is_write_index": false
    }
  }

```

**Question**

1. How come that after replication value of "is\_write\_index" changed to false. Is it expected behavior?
2. If it is expected behavior, should I update "is\_write\_index" to be true on former follower (leader) in order to continue index documents to it?

P/S - I am reading what is **is\_write\_index** in documentation, and see that [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-put-template.html) description of this flag contradicts with description [on this page](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-aliases.html)

---

<div class="post-metadata">

**Author:** ![Armen\_Petrosyan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/armen_petrosyan/32/80330_2.png) [@Armen\_Petrosyan](https://discuss.elastic.co/u/Armen_Petrosyan)\
**Post date:** [January 19, 2022, 12:29pm UTC](https://discuss.elastic.co/t/elasticsearch-ccr-former-follower-leader-index-is-not-writable/292962/2 "2022-01-19T12:29:58Z")

</div>

Anyone?

---

<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:** [February 16, 2022, 12:30pm UTC](https://discuss.elastic.co/t/elasticsearch-ccr-former-follower-leader-index-is-not-writable/292962/3 "2022-02-16T12:30:57Z")

</div>

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