# After upgrade from ES 1.0.2 to ES 2.3.4, cluster state is red
**URL:** https://discuss.elastic.co/t/after-upgrade-from-es-1-0-2-to-es-2-3-4-cluster-state-is-red/56399
**Category:** Elasticsearch
**Created:** [July 26, 2016, 1:29pm UTC](https://discuss.elastic.co/t/after-upgrade-from-es-1-0-2-to-es-2-3-4-cluster-state-is-red/56399 "2016-07-26T13:29:17Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@SwethaS](https://discuss.elastic.co/u/SwethaS)
#### Post date: [July 26, 2016, 1:29pm UTC](https://discuss.elastic.co/t/after-upgrade-from-es-1-0-2-to-es-2-3-4-cluster-state-is-red/56399/1 "2016-07-26T13:29:17Z")
I have 4 indices built using ES 1.0.2, after upgrading to 2.3.4, below is the cluster state
> {
> "cluster\_name": "59f92c3bcfadac7eaf599dad8eace0b3",
> "status": "red",
> "timed\_out": false,
> "number\_of\_nodes": 1,
> "number\_of\_data\_nodes": 1,
> "active\_primary\_shards": 0,
> "active\_shards": 0,
> "relocating\_shards": 0,
> "initializing\_shards": 0,
> "unassigned\_shards": 4,
> "delayed\_unassigned\_shards": 0,
> "number\_of\_pending\_tasks": 0,
> "number\_of\_in\_flight\_fetch": 0,
> "task\_max\_waiting\_in\_queue\_millis": 0,
> "active\_shards\_percent\_as\_number": 0
> }
Is there a way to overcome this?
---
### Author:  [@jpcarey](https://discuss.elastic.co/u/jpcarey)
#### Post date: [July 26, 2016, 1:38pm UTC](https://discuss.elastic.co/t/after-upgrade-from-es-1-0-2-to-es-2-3-4-cluster-state-is-red/56399/2 "2016-07-26T13:38:29Z")
Only one mode is expected? Use `GET /_cat/indices?v` to see which indices are red. `GET /_cat/shards?v` will list all shards. You most likely have primary shards unassigned.
[https://www.elastic.co/guide/en/elasticsearch/reference/current/cat.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/cat.html)
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [July 26, 2016, 1:49pm UTC](https://discuss.elastic.co/t/after-upgrade-from-es-1-0-2-to-es-2-3-4-cluster-state-is-red/56399/3 "2016-07-26T13:49:14Z")
I guess you have errors in logs.
Did you upgrade directly from 1.0.2 to 2.3.4?
You did not run the migration plugin?
You did not follow the upgrade documentation and the breaking changes doc?
[https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking-changes.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking-changes.html)
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 10:32pm UTC](https://discuss.elastic.co/t/after-upgrade-from-es-1-0-2-to-es-2-3-4-cluster-state-is-red/56399/4 "2017-07-05T22:32:52Z")