# Identical node name for all cluster nodes **URL:** \ **Category:** Elasticsearch\ **Created:** [February 28, 2012, 12:47am UTC](https://discuss.elastic.co/t/identical-node-name-for-all-cluster-nodes/6822 "2012-02-28T00:47:00Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Vikram\_Adukia](https://avatars.discourse-cdn.com/v4/letter/v/f4b2a3/32.png) [@Vikram\_Adukia](https://discuss.elastic.co/u/Vikram_Adukia)\ **Post date:** [February 28, 2012, 12:47am UTC](https://discuss.elastic.co/t/identical-node-name-for-all-cluster-nodes/6822/1 "2012-02-28T00:47:00Z")
I just set up a 3 node elasticsearch cluster with version 0.18.7. For some reason, all the nodes are coming up with the node name of "Aardwolf". All nodes are able to find each other. All nodes are using the same cluster.name Currently, there is nothing indexed in the cluster. Currently, I don't have node.name set in the configuration file. Though, if I did set it, it does work. However, without that setting, no matter how many times I restart different nodes, the node name always comes up as "Aardwolf". Each node does have a unique id. So, here are my questions: 1. why is this happening? I don't see this behavior with another elasticsearch cluster that I have set up 2. would this cause any problems? thanks ---
**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\ **Post date:** [February 28, 2012, 1:46am UTC](https://discuss.elastic.co/t/identical-node-name-for-all-cluster-nodes/6822/2 "2012-02-28T01:46:43Z")
My guess would be that you are running Java 7u1 on this new cluster and hitting known bug in ThreadLocalRandom class [http://bugs.sun.com/bugdatabase/view\_bug.do?bug\_id=6955840](http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6955840). This bug is fixed in 7u2, so you can ether upgrade java to 7u2 or 7u3 or downgrade it to 1.6. Since ThreadLocalRandom is used in several other places in elasticsearch, this bug might be causing other issues, but I don't know for sure. On Mon, Feb 27, 2012 at 7:47 PM, Vikram Adukia [adukia@fireitup.net](mailto:adukia@fireitup.net) wrote: > I just set up a 3 node elasticsearch cluster with version 0.18.7. For > some reason, all the nodes are coming up with the node name of > "Aardwolf". > > All nodes are able to find each other. All nodes are using the same > cluster.name > > Currently, there is nothing indexed in the cluster. > > Currently, I don't have node.name set in the configuration file. > Though, if I did set it, it does work. However, without that setting, > no matter how many times I restart different nodes, the node name > always comes up as "Aardwolf". > > Each node does have a unique id. > > So, here are my questions: > > 1. why is this happening? I don't see this behavior with another > elasticsearch cluster that I have set up > 2. would this cause any problems? > > thanks ---
**Author:** ![Vikram\_Adukia\_2](https://avatars.discourse-cdn.com/v4/letter/v/aeb1de/32.png) [@Vikram\_Adukia\_2](https://discuss.elastic.co/u/Vikram_Adukia_2)\ **Post date:** [February 28, 2012, 4:22pm UTC](https://discuss.elastic.co/t/identical-node-name-for-all-cluster-nodes/6822/3 "2012-02-28T16:22:37Z")
Updating to 7u3 does appear to have fixed the issue. thanks On Mon, Feb 27, 2012 at 5:46 PM, Igor Motov [imotov@gmail.com](mailto:imotov@gmail.com) wrote: > My guess would be that you are running Java 7u1 on this new cluster and > hitting known bug in ThreadLocalRandom class > [http://bugs.sun.com/bugdatabase/view\_bug.do?bug\_id=6955840](http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6955840). This bug is > fixed in 7u2, so you can ether upgrade java to 7u2 or 7u3 or downgrade it > to 1.6. Since ThreadLocalRandom is used in several other places in > elasticsearch, this bug might be causing other issues, but I don't know for > sure. > > On Mon, Feb 27, 2012 at 7:47 PM, Vikram Adukia [adukia@fireitup.net](mailto:adukia@fireitup.net)wrote: > > > I just set up a 3 node elasticsearch cluster with version 0.18.7. For > > some reason, all the nodes are coming up with the node name of > > "Aardwolf". > > > > All nodes are able to find each other. All nodes are using the same > > cluster.name > > > > Currently, there is nothing indexed in the cluster. > > > > Currently, I don't have node.name set in the configuration file. > > Though, if I did set it, it does work. However, without that setting, > > no matter how many times I restart different nodes, the node name > > always comes up as "Aardwolf". > > > > Each node does have a unique id. > > > > So, here are my questions: > > > > 1. why is this happening? I don't see this behavior with another > > elasticsearch cluster that I have set up > > 2. would this cause any problems? > > > > thanks ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [February 28, 2012, 8:42pm UTC](https://discuss.elastic.co/t/identical-node-name-for-all-cluster-nodes/6822/4 "2012-02-28T20:42:10Z")
Note also that you should only use Java 7u2 and above, otherwise, you might get index corruptions due to a bug in Java 7 and 7u1 versions. On Tuesday, February 28, 2012 at 6:22 PM, Vikram Adukia wrote: > Updating to 7u3 does appear to have fixed the issue. > > thanks > > On Mon, Feb 27, 2012 at 5:46 PM, Igor Motov \<[imotov@gmail.com](mailto:imotov@gmail.com) ([mailto:imotov@gmail.com](mailto:imotov@gmail.com))\> wrote: > > > My guess would be that you are running Java 7u1 on this new cluster and hitting known bug in ThreadLocalRandom class [http://bugs.sun.com/bugdatabase/view\_bug.do?bug\_id=6955840](http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6955840). This bug is fixed in 7u2, so you can ether upgrade java to 7u2 or 7u3 or downgrade it to 1.6. Since ThreadLocalRandom is used in several other places in elasticsearch, this bug might be causing other issues, but I don't know for sure. > > > > On Mon, Feb 27, 2012 at 7:47 PM, Vikram Adukia \<[adukia@fireitup.net](mailto:adukia@fireitup.net) ([mailto:adukia@fireitup.net](mailto:adukia@fireitup.net))\> wrote: > > > > > I just set up a 3 node elasticsearch cluster with version 0.18.7. For > > > some reason, all the nodes are coming up with the node name of > > > "Aardwolf". > > > > > > All nodes are able to find each other. All nodes are using the same > > > cluster.name ([http://cluster.name](http://cluster.name)) > > > > > > Currently, there is nothing indexed in the cluster. > > > > > > Currently, I don't have node.name ([http://node.name](http://node.name)) set in the configuration file. > > > Though, if I did set it, it does work. However, without that setting, > > > no matter how many times I restart different nodes, the node name > > > always comes up as "Aardwolf". > > > > > > Each node does have a unique id. > > > > > > So, here are my questions: > > > > > > 1. why is this happening? I don't see this behavior with another > > > elasticsearch cluster that I have set up > > > 2. would this cause any problems? > > > > > > thanks ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:37am UTC](https://discuss.elastic.co/t/identical-node-name-for-all-cluster-nodes/6822/5 "2017-07-06T03:37:58Z")