# \[SERVICE\_UNAVAILABLE/1/state not recovered / initialized\];\]

**URL:** <https://discuss.elastic.co/t/service-unavailable-1-state-not-recovered-initialized/374825>\
**Category:** Elastic Search\
**Created:** [February 20, 2025, 3:12pm UTC](https://discuss.elastic.co/t/service-unavailable-1-state-not-recovered-initialized/374825 "2025-02-20T15:12:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mohit2709](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mohit2709/32/141214_2.png) [@mohit2709](https://discuss.elastic.co/u/mohit2709)\
**Post date:** [February 20, 2025, 3:12pm UTC](https://discuss.elastic.co/t/service-unavailable-1-state-not-recovered-initialized/374825/1 "2025-02-20T15:12:58Z")

</div>

Hi. I am trying to move our ES cluster from 1.x to 2.x (2.0.0 to be specific) and facing the below error in elasticsearch logs  
[SERVICE\_UNAVAILABLE/1/state not recovered / initialized];]

Below is the elasticsearch.yml file

```auto
bootstrap:
  mlockall: true
cloud:
  aws:
    region: us-east-1
cluster:
  name: elasticsearch-${CLUSTER}-cluster-${ENVIRONMENT}
  routing:
    allocation:
      awareness:
        attributes: aws_zone
discovery:
  ec2:
   region: us-east-1
   tag:
     cluster: ${CLUSTER}
     node_discovery: true
     environment: ${ENVIRONMENT}
     master_node: true
  type: ec2
  zen:
    fd:
      ping_interval: 1s
      ping_timeout: 30s
      ping_retries: 3
    minimum_master_nodes: 2
gateway:
  expected_nodes: 3
  recover_after_master_nodes: 2
  recover_after_time: 5m
multicast:
  enabled: false
node:
  name: ${CLUSTER}-${NODE_TYPE}-${NODE_ID}
  aws_zone: ${ZONE_ID}
  master: ${MASTER_NODE}
  data: ${DATA_NODE}
path:
  data: /usr/share/elasticsearch/data
  log: /var/log/elasticsearch
threadpool:
  search:
    reject_policy: caller
    size: 300
    type: fixed
  index:
    queue_size: 400
indices:
  memory:
    index_buffer_size: 10%
  fielddata:
    cache:
      size: 20%
script:
  inline: on
  indexed: on

# slow queries log settings
index.search.slowlog.threshold.query.warn: 10s
index.search.slowlog.threshold.query.info: 5s
index.search.slowlog.threshold.query.debug: 1s
index.search.slowlog.threshold.query.trace: 200ms

index.search.slowlog.threshold.fetch.warn: 10s
index.search.slowlog.threshold.fetch.info: 5s
index.search.slowlog.threshold.fetch.debug: 1s
index.search.slowlog.threshold.fetch.trace: 200ms

index.search.slowlog.level: trace

index.indexing.slowlog.threshold.index.warn: 10s
index.indexing.slowlog.threshold.index.info: 5s
index.indexing.slowlog.threshold.index.debug: 1s
index.indexing.slowlog.threshold.index.trace: 200ms

index.indexing.slowlog.level: trace
path.repo: /efs_snapshots/repos/

```

Any idea what could be the issue or if something needs to be modified in the above file?  
Note: Cluster comprises of 3 master and 4 data nodes.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [February 24, 2025, 6:40am UTC](https://discuss.elastic.co/t/service-unavailable-1-state-not-recovered-initialized/374825/2 "2025-02-24T06:40:16Z")

</div>

When upgrading Elasticsearch you should always go to the latest minor version of the major you are upgrading to. That said I do not see the point in upgrading to version 2.4.6 as it was released in 2017 and has been EOL a very long time. It is so old that you may struggle to get any help with it as most people here, myself included, has not used it in many years.

I would recommend you instead upgrade directly to the latest version even though that will require more effort.

---

<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 24, 2025, 6:40am UTC](https://discuss.elastic.co/t/service-unavailable-1-state-not-recovered-initialized/374825/3 "2025-03-24T06:40:34Z")

</div>

Closed on March 24, 2025, 6:40am UTC

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