Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tribe node errors on start up #5582

Closed
cleesmith opened this Issue Mar 27, 2014 · 2 comments

Comments

Projects
None yet
2 participants
@cleesmith
Copy link

cleesmith commented Mar 27, 2014

When starting up a tribe node the following is seen in the log file:

[2014-03-27 18:47:23,080][WARN ][tribe                    ] [tribe_x.x.x.x] failed to process [cluster event from t2, updating local node id]
java.lang.NullPointerException
        at org.elasticsearch.cluster.routing.RoutingTable$Builder.add(RoutingTable.java:400)
        at org.elasticsearch.tribe.TribeService$TribeClusterStateListener$1.execute(TribeService.java:285)
        at org.elasticsearch.cluster.service.InternalClusterService$UpdateTask.run(InternalClusterService.java:308)
        at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:134)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:744)

After a few minutes these errors cease and everything seems normal again.
Note: the tribe node is version 1.1.0 and the other nodes are 1.0.1 ... is this the issue?

@kimchy

This comment has been minimized.

Copy link
Member

kimchy commented Mar 27, 2014

I looked into this, and this issue was fixed in 1.x (upcoming 1.2), I will backport just the fix to 1.1.x branch so if we do another 1.1 release

@kimchy kimchy added bug labels Mar 27, 2014

kimchy added a commit that referenced this issue Mar 27, 2014

backport NPE bug fix in tribe
when routing table is not in play yet, don't add the index, this was fix as part of #5501, but fix it also for 1.1 branch
fixes #5582
@cleesmith

This comment has been minimized.

Copy link
Author

cleesmith commented Mar 27, 2014

Amazing, thanks. You guys are on top of things ... now, if I could just keep up with the releases.

@cleesmith cleesmith closed this Mar 27, 2014

mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015

backport NPE bug fix in tribe
when routing table is not in play yet, don't add the index, this was fix as part of elastic#5501, but fix it also for 1.1 branch
fixes elastic#5582
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.