# How to fix the issue Master node not identified during the Elk upgrade from 6.8 to 7.13.2 **URL:** \ **Category:** Elasticsearch\ **Created:** [March 17, 2024, 4:08pm UTC](https://discuss.elastic.co/t/how-to-fix-the-issue-master-node-not-identified-during-the-elk-upgrade-from-6-8-to-7-13-2/355562 "2024-03-17T16:08:25Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![arun.natha](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@arun.natha](https://discuss.elastic.co/u/arun.natha)\ **Post date:** [March 17, 2024, 4:08pm UTC](https://discuss.elastic.co/t/how-to-fix-the-issue-master-node-not-identified-during-the-elk-upgrade-from-6-8-to-7-13-2/355562/1 "2024-03-17T16:08:25Z")
Hello everyone, I need a help. During the elastic migration from ELK 6.8 to 7.13.2 The problem that we are facing is that when the data is present cluster unique id is not present that's why it cannot connect. ![IMG-20240316-WA0003](https://us1.discourse-cdn.com/elastic/original/3X/4/d/4da60f4362580617fa5e5d36a68967e2657db654.jpeg) ---
**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:** [March 17, 2024, 9:18pm UTC](https://discuss.elastic.co/t/how-to-fix-the-issue-master-node-not-identified-during-the-elk-upgrade-from-6-8-to-7-13-2/355562/2 "2024-03-17T21:18:52Z")
I don't understand what you're meaning. What's the problem? And why migrating to an obsolete version and not 7.17? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 14, 2024, 9:19pm UTC](https://discuss.elastic.co/t/how-to-fix-the-issue-master-node-not-identified-during-the-elk-upgrade-from-6-8-to-7-13-2/355562/3 "2024-04-14T21:19:51Z")
Closed on April 14, 2024, 9:19pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.