# Node names missing after upgrading ES and Marvel to 2.1, KB to 4.3.0
**URL:** https://discuss.elastic.co/t/node-names-missing-after-upgrading-es-and-marvel-to-2-1-kb-to-4-3-0/35510
**Category:** Elasticsearch
**Tags:** elastic-stack-monitoring
**Created:** [November 25, 2015, 6:14am UTC](https://discuss.elastic.co/t/node-names-missing-after-upgrading-es-and-marvel-to-2-1-kb-to-4-3-0/35510 "2015-11-25T06:14:26Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@vtst2412](https://discuss.elastic.co/u/vtst2412)
#### Post date: [November 25, 2015, 6:14am UTC](https://discuss.elastic.co/t/node-names-missing-after-upgrading-es-and-marvel-to-2-1-kb-to-4-3-0/35510/1 "2015-11-25T06:14:26Z")
Node name seems to be falling back to node unique ID now... Any particular log I should be looking at?
---
### Author:  [@Kevin\_Ross](https://discuss.elastic.co/u/Kevin_Ross)
#### Post date: [November 25, 2015, 9:51am UTC](https://discuss.elastic.co/t/node-names-missing-after-upgrading-es-and-marvel-to-2-1-kb-to-4-3-0/35510/2 "2015-11-25T09:51:32Z")
I also have this issue. I can see the node names fine in other plugins such as kopf but in marvel the node name is the UID.
---
### Author:  [@skearns](https://discuss.elastic.co/u/skearns)
#### Post date: [November 25, 2015, 1:00pm UTC](https://discuss.elastic.co/t/node-names-missing-after-upgrading-es-and-marvel-to-2-1-kb-to-4-3-0/35510/3 "2015-11-25T13:00:34Z")
In Marvel 2.1, we began tracking node names in a slightly different way, which allows us to show historic data much more easily/accurately. The data from Marvel 2.0 doesn't have this additional information, so data collected with Marvel 2.0 will display node IDs, rather than names. Please make sure that the cluster being monitored is running ES 2.1 and Marvel 2.1 (the correct version will be installed if you run `bin/plugin install marvel-agent`).
Let me know if that solves the issue here
---
### Author:  [@vtst2412](https://discuss.elastic.co/u/vtst2412)
#### Post date: [November 25, 2015, 2:55pm UTC](https://discuss.elastic.co/t/node-names-missing-after-upgrading-es-and-marvel-to-2-1-kb-to-4-3-0/35510/4 "2015-11-25T14:55:45Z")
Hello all. Thanks for the response.
I have scripted the `bin/plugin remove license; bin/plugin remove marvel-agent; bin/plugin install license; bin/plugin install marvel-agent` to my rolling update script on the individual ES nodes. As a sanity check, I've verified that the jar under `plugins/marvel-agent` is indeed `marvel-agent-2.1.0.jar` for each node. I also notice that the data in .marvel-es-\* do not contain any field for the node name.
Could it be that the new agent is collecting the additional data for node name, but it can't ship to ES due to type conflict?
---
### Author:  [@skearns](https://discuss.elastic.co/u/skearns)
#### Post date: [November 25, 2015, 3:07pm UTC](https://discuss.elastic.co/t/node-names-missing-after-upgrading-es-and-marvel-to-2-1-kb-to-4-3-0/35510/5 "2015-11-25T15:07:28Z")
Indeed, we changed the index template in 2.1. Can you try deleting the .marvel-es-data and .marvel-es-2015-11-25 indexes and see if that solves the problem?
---
### Author:  [@vtst2412](https://discuss.elastic.co/u/vtst2412)
#### Post date: [November 25, 2015, 3:32pm UTC](https://discuss.elastic.co/t/node-names-missing-after-upgrading-es-and-marvel-to-2-1-kb-to-4-3-0/35510/6 "2015-11-25T15:32:29Z")
Deleting .marvel-es-data didn't help (but might have contributed). Deleting the most recent dated index did the trick! I must have upgraded right after the index rolled to the next day. This probably would have gone away after 24 hours when the new dated index is created.
Thanks a lot, Steve. Wasn't a big deal but was bugging me that I couldn't figure out the problem.
---
### Author:  [@skearns](https://discuss.elastic.co/u/skearns)
#### Post date: [November 25, 2015, 3:33pm UTC](https://discuss.elastic.co/t/node-names-missing-after-upgrading-es-and-marvel-to-2-1-kb-to-4-3-0/35510/7 "2015-11-25T15:33:28Z")
Great, I'm glad that did the trick! We'll be updating the docs around this to make it more clear in the future 🙂
---
### Author:  [@renevdm](https://discuss.elastic.co/u/renevdm)
#### Post date: [December 9, 2015, 11:14pm UTC](https://discuss.elastic.co/t/node-names-missing-after-upgrading-es-and-marvel-to-2-1-kb-to-4-3-0/35510/8 "2015-12-09T23:14:11Z")
I had the same issue, so I also deleted the last dated index to solve this. But now I have 2 nodes showing up (one offline, one online)! While I only have one single box running. Both nodes have UID names. How do I solve this?
---
### Author:  [@vtst2412](https://discuss.elastic.co/u/vtst2412)
#### Post date: [December 9, 2015, 11:58pm UTC](https://discuss.elastic.co/t/node-names-missing-after-upgrading-es-and-marvel-to-2-1-kb-to-4-3-0/35510/9 "2015-12-09T23:58:39Z")
You need to delete `.marvel-es-data` as well. I believe that index holds the header fields for Marvel.
---
### Author:  [@renevdm](https://discuss.elastic.co/u/renevdm)
#### Post date: [December 10, 2015, 12:12am UTC](https://discuss.elastic.co/t/node-names-missing-after-upgrading-es-and-marvel-to-2-1-kb-to-4-3-0/35510/10 "2015-12-10T00:12:51Z")
Heeeeyyyyyy, it's back! Many thanks!!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 1:46pm UTC](https://discuss.elastic.co/t/node-names-missing-after-upgrading-es-and-marvel-to-2-1-kb-to-4-3-0/35510/11 "2017-07-06T13:46:10Z")