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

NullPointerException in CompletionStats #3619

Closed
rdeaton opened this Issue Sep 4, 2013 · 3 comments

Comments

Projects
None yet
3 participants
@rdeaton
Copy link

rdeaton commented Sep 4, 2013

[2013-09-04 00:46:46,113][DEBUG][action.admin.cluster.node.stats] [qtau] failed to execute on node [3MfX8Mx6Rmmp0_fukOT4lQ]
org.elasticsearch.transport.RemoteTransportException: [qantiup][inet[/192.168.72.143:9300]][cluster/nodes/stats/n]
Caused by: java.lang.NullPointerException
at org.elasticsearch.index.engine.robin.RobinEngine.searcher(RobinEngine.java:682)
at org.elasticsearch.index.shard.service.InternalIndexShard.completionStats(InternalIndexShard.java:536)
at org.elasticsearch.indices.InternalIndicesService.stats(InternalIndicesService.java:299)
at org.elasticsearch.node.service.NodeService.stats(NodeService.java:165)
at org.elasticsearch.action.admin.cluster.node.stats.TransportNodesStatsAction.nodeOperation(TransportNodesStatsAction.java:100)
at org.elasticsearch.action.admin.cluster.node.stats.TransportNodesStatsAction.nodeOperation(TransportNodesStatsAction.java:43)
at org.elasticsearch.action.support.nodes.TransportNodesOperationAction$NodeTransportHandler.messageReceived(TransportNodesOperationAction.java:280)
at org.elasticsearch.action.support.nodes.TransportNodesOperationAction$NodeTransportHandler.messageReceived(TransportNodesOperationAction.java:271)
at org.elasticsearch.transport.netty.MessageChannelHandler$RequestHandler.run(MessageChannelHandler.java:269)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

@btiernay

This comment has been minimized.

Copy link

btiernay commented Sep 5, 2013

What version are you experiencing this on?

@rdeaton

This comment has been minimized.

Copy link
Author

rdeaton commented Sep 5, 2013

Master from within the last 24-hours or so.

@ghost ghost assigned s1monw Sep 5, 2013

@s1monw

This comment has been minimized.

Copy link
Contributor

s1monw commented Sep 5, 2013

it seems like this shard is starting up right now but the engine is not started yet while the stats are requested. I will push a fix for this soon.

s1monw added a commit to s1monw/elasticsearch that referenced this issue Sep 5, 2013

Return empty completion stats if engine throws an exception
If the index shard is not started yet the underlying engine can
throw an exception since not everything is initialized. This can
happen if a shard is just about starting up or recovering / initalizing
and stats are requested.

Closes elastic#3619

@s1monw s1monw closed this in 764a519 Sep 5, 2013

s1monw added a commit that referenced this issue Sep 5, 2013

Return empty completion stats if engine throws an exception
If the index shard is not started yet the underlying engine can
throw an exception since not everything is initialized. This can
happen if a shard is just about starting up or recovering / initalizing
and stats are requested.

Closes #3619

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

Return empty completion stats if engine throws an exception
If the index shard is not started yet the underlying engine can
throw an exception since not everything is initialized. This can
happen if a shard is just about starting up or recovering / initalizing
and stats are requested.

Closes elastic#3619
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.