# Replication on data nodes

**URL:** <https://discuss.elastic.co/t/replication-on-data-nodes/118301>\
**Category:** Elasticsearch\
**Created:** [February 3, 2018, 9:15am UTC](https://discuss.elastic.co/t/replication-on-data-nodes/118301 "2018-02-03T09:15:05Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![iam.Carrot](https://avatars.discourse-cdn.com/v4/letter/i/a9adbd/32.png) [@iam.Carrot](https://discuss.elastic.co/u/iam.Carrot)\
**Post date:** [February 3, 2018, 9:15am UTC](https://discuss.elastic.co/t/replication-on-data-nodes/118301/1 "2018-02-03T09:15:06Z")

</div>

I was upgrading elasticsearch onmy cluster. Successfully been done, I face an issue,

the issue is on my data nodes when I see on the dashboard, one data node has all the original data while other has all the replicated data.  
Below is the image:

 ![Untitled](https://us1.discourse-cdn.com/elastic/original/3X/8/7/876bca2f34dcb2f7135f29db8d85969cadb06054.png)

the information of a single shard is below:

```
{
    "state": "STARTED",
    "primary": true,
    "node": "31mUy4upTjqVgE6mPZo9Zg",
    "relocating_node": null,
    "shard": 2,
    "index": "search_feedback",
    "allocation_id": 
    {
         "id": "VFyr5yfRTO692Lsytpi_nQ"
     }
}

```

If you see the screenshot the shards with the gray border are the original shards while the one's without are the replicas.

How can I make them reallocate such that a each data node has some original shards and some replicas, like the way they used to before I did the upgrade.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [February 3, 2018, 9:48am UTC](https://discuss.elastic.co/t/replication-on-data-nodes/118301/2 "2018-02-03T09:48:35Z")

</div>

It does not really matter. Why do you think it does?

---

<div class="post-metadata">

**Author:** ![iam.Carrot](https://avatars.discourse-cdn.com/v4/letter/i/a9adbd/32.png) [@iam.Carrot](https://discuss.elastic.co/u/iam.Carrot)\
**Post date:** [February 3, 2018, 11:31am UTC](https://discuss.elastic.co/t/replication-on-data-nodes/118301/3 "2018-02-03T11:31:33Z")

</div>

@dadoonet It just seems off since it's never happened that ways. Also I get an error while querying a particular index. with the error illegal\_state\_exception. below is a link

> [@Illegal\_state\_exception with reason unexpected byte \[0xff\]](https://discuss.elastic.co/t/illegal-state-exception-with-reason-unexpected-byte-0xff/118310):
>
> Hi I am using elasticsearch to search through data. I get the below response: { "error": { "root\_cause": [{ "type": "illegal\_state\_exception", "reason": "unexpected byte [0xff]" } ], "type": "search\_phase\_execution\_exception", "reason": "all shards failed", "phase": "query", "grouped": true, "failed\_shards": [ { "shard": 0, "index": "locationdb\_160", "n…

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [February 3, 2018, 11:45am UTC](https://discuss.elastic.co/t/replication-on-data-nodes/118301/4 "2018-02-03T11:45:51Z")

</div>

> Also I get an error while querying a particular index. with the error illegal\_state\_exception. below is a link

This is not related.

> It just seems off since it's never happened that ways.

You can bring up a new node, wait for a new distribution of the shards, then switch off this node and wait for the new distribution and you will probably end up with replicas and primaries mixed together. But I'd not care about this unless you really have performance problems or something like that.

---

<div class="post-metadata">

**Author:** ![iam.Carrot](https://avatars.discourse-cdn.com/v4/letter/i/a9adbd/32.png) [@iam.Carrot](https://discuss.elastic.co/u/iam.Carrot)\
**Post date:** [February 3, 2018, 11:56am UTC](https://discuss.elastic.co/t/replication-on-data-nodes/118301/5 "2018-02-03T11:56:05Z")

</div>

Great! glad to know that, I was wondering if I have to reindex my data

Would you please be able to check out the issue that I've linked in my previous reply? It'll be of great help

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [February 3, 2018, 1:38pm UTC](https://discuss.elastic.co/t/replication-on-data-nodes/118301/6 "2018-02-03T13:38:08Z")

</div>

I looked at it but I don't have the answer so I did not answer as I prefer to leave it non answered so you get a better chance to have someone else to look at it.

---

<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 3, 2018, 1:38pm UTC](https://discuss.elastic.co/t/replication-on-data-nodes/118301/7 "2018-03-03T13:38:12Z")

</div>

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