Moving Elasticsearch 6.2.4 data to Elasticsearch 7.6.1

Elastic Stack Elasticsearch
1

Hi,

I am trying to copy the data from our old Elasticsearch 6.2.4 to the new elasticsearch 7.6.1

I tried the following methods.
Snapshot and restore
Re-index from a remote cluster.

Both methods seem working but I got Yellow color health status in the new server.
Also, what does yellow mean? and I got that status in old elastic server 6.2.4.

What happened in the Elasticsearch 7.6.1 once the data is moved from Elasticsearch 6.2.4

  • I see all the indices in the yellow color status.

  • In the new Elasticsearch authentication failed immediately. I attached the log in the bottom. When I searched about that solution are clean up the data and point to the new data directory in the elasticsearch.

My questions

  1. Basically, How to change the Yellow color health status to Green?

  2. If I do the mappings manually in the new server and moved the data is that enough to get Green status?

I am trying to figure this out If possible can someone help with this?

Thanks
Saravana

2

Welcome!

What is the output of:

GET /
GET /_cat/nodes?v
GET /_cat/health?v
GET /_cat/indices?v

If some outputs are too big, please share them on gist.github.com and link them here.

3

Hi,

Thank you for your reply.

I sent the output of our elasticsearch 6.2.4

Elasticsearch 7.6.1 always show authentication error once I restore the data from the old server

http://localhost:9200/

Elasticserver 6.2.4

{
"name" : "RmnVUCT",
"cluster_name" : "elasticsearch",
"cluster_uuid" : "RIMK9-rQQyibaQ38gUIapg",
"version" : {
"number" : "6.2.4",
"build_hash" : "ccec39f",
"build_date" : "2018-04-12T20:37:28.497551Z",
"build_snapshot" : false,
"lucene_version" : "7.2.1",
"minimum_wire_compatibility_version" : "5.6.0",
"minimum_index_compatibility_version" : "5.0.0"
},
"tagline" : "You Know, for Search"
}

http://localhost:9200/_cat/nodes?v
ip heap.percent ram.percent cpu load_1m load_5m load_15m node.role master name
127.0.0.1 36 92 15 0.69 0.78 0.96 mdi * RmnVUCT

http://localhost:9200/_cat/health?v
epoch timestamp cluster status node.total node.data shards pri relo init unassign pending_tasks max_task_wait_time active_shards_percent
1585910719 10:45:19 elasticsearch yellow 1 1 400 400 0 0 388 0 - 50.8%

4

Please format your code, logs or configuration files using </> icon as explained in this guide and not the citation button. It will make your post more readable.

Or use markdown style like:

```
CODE
```

This is the icon to use if you are not using markdown format:

image
image764×92 16.4 KB

There's a live preview panel for exactly this reasons.

Lots of people read these forums, and many of them will simply skip over a post that is difficult to read, because it's just too large an investment of their time to try and follow a wall of badly formatted text.
If your goal is to get an answer to your questions, it's in your interest to make it as easy to read and understand as possible.
Please update your post.

5

You probably need to fix this problem.
Not sure how you saw them that the cluster is yellow.

But anyway, in the old cluster it's yellow as well.
So everything looks fine.

It can't be green if you have at least one index with the number of replicas greater or equal to 1 and only one node in your cluster.

6

Ok, thanks.
Elasticsearch 7.6.1 I enabled authentication and set up the password for elastic user.
but after the restore process its throwing that error. I will try to fix that

==========================================================
] [node-1] Authentication of [elastic] was terminated by realm [reserved] - failed to authenticate user [elastic]

===========================================================

7

You need to provide the credentials when your cluster is secured.

8

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