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

GoogleCloudStorageBlobStoreRepositoryTests : NPE in ZenDiscovery.findMaster #24027

Closed
javanna opened this issue Apr 10, 2017 · 5 comments
Closed
Assignees
Labels
>test Issues or PRs that are addressing/adding tests >test-failure Triaged test failures from CI

Comments

@javanna
Copy link
Member

javanna commented Apr 10, 2017

Some of the GoogleCloudStorageBlobStoreRepositoryTests tests failed at the same time in this run:

https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+5.x+multijob-intake/995 .

I found some NPEs when trying to find a master in the logs, here is the stacktrace:

1> [2017-04-10T08:53:08,926][ERROR][o.e.t.d.TestZenDiscovery ] [node_sc1] unexpected error while joining cluster, trying again
  1> java.lang.NullPointerException: null
  1> 	at java.util.stream.FindOps$FindSink$OfRef.<init>(FindOps.java:190) ~[?:1.8.0_121]
  1> 	at java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:152) ~[?:1.8.0_121]
  1> 	at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[?:1.8.0_121]
  1> 	at java.util.stream.ReferencePipeline.findAny(ReferencePipeline.java:469) ~[?:1.8.0_121]
  1> 	at org.elasticsearch.discovery.zen.ZenDiscovery.findMaster(ZenDiscovery.java:896) ~[elasticsearch-5.4.0-SNAPSHOT.jar:5.4.0-SNAPSHOT]
  1> 	at org.elasticsearch.discovery.zen.ZenDiscovery.innerJoinCluster(ZenDiscovery.java:386) ~[elasticsearch-5.4.0-SNAPSHOT.jar:5.4.0-SNAPSHOT]
@javanna javanna added >test-failure Triaged test failures from CI >test Issues or PRs that are addressing/adding tests labels Apr 10, 2017
@javanna
Copy link
Member Author

javanna commented Apr 10, 2017

@bleskes could you have a look at this or further dispatch it?

@abeyad
Copy link

abeyad commented Apr 10, 2017

This also seems to be one of those strange JVM exceptions. FindOps.java line 190 appears to be the start of the OfRef<T> class definition.

@bleskes
Copy link
Contributor

bleskes commented Apr 10, 2017

the ZenDiscovery line is

       assert fullPingResponses.stream().map(ZenPing.PingResponse::node)
            .filter(n -> n.equals(localNode)).findAny().isPresent() == false;

it might be that ZenPing.PingResponse::node returns null

@bleskes
Copy link
Contributor

bleskes commented Apr 10, 2017

@abeyad can you dig a bit in that direction?

@abeyad
Copy link

abeyad commented Apr 10, 2017

@bleskes I am closing this as we are tracking these JVM exceptions elsewhere.

@abeyad abeyad closed this as completed Apr 10, 2017
@bleskes bleskes removed their assignment Apr 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>test Issues or PRs that are addressing/adding tests >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

3 participants