IndexOutOfBoundsException in X-Pack 5.3

[wyukawa]

Hi, I use X-Pack 5.3. But the following error occurred.

[2017-04-09T09:00:51,252][ERROR][o.e.x.m.c.n.NodeStatsCollector] [...] collector [node-stats-collector] failed to collect data
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.rangeCheck(ArrayList.java:653) ~[?:1.8.0_121]
at java.util.ArrayList.get(ArrayList.java:429) ~[?:1.8.0_121]
at org.elasticsearch.xpack.monitoring.collector.node.NodeStatsCollector.doCollect(NodeStatsCollector.java:73) ~[x-pack-5.3.0.jar:5.3.0]
at org.elasticsearch.xpack.monitoring.collector.Collector.collect(Collector.java:83) [x-pack-5.3.0.jar:5.3.0]
at org.elasticsearch.xpack.monitoring.MonitoringService$MonitoringExecution$1.doRun(MonitoringService.java:195) [x-pack-5.3.0.jar:5.3.0]
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) [elasticsearch-5.3.0.jar:5.3.0]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_121]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_121]
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:544) [elasticsearch-5.3.0.jar:5.3.0]

[Marius_Dragomir]

Hello,
What is the rest of the setup?
Usually that error occurs when you don't get data from the node for monitoring and stats. It should just skip that collection, but it shouldn't interfere with anything else.

[wyukawa]

hmm, actually, although this error occurred, X-Pack 5.3 seems to work well.

But I thinks it's better to skip that collection.

If engineers see IndexOutOfBoundsException, they consider this problem as bug.

[Marius_Dragomir]

Yes, I agree we need to improve our error message handling across the stack, but you can only do so much with so little time. There are a few meta issues regarding this and work is progressing on them, but they're not very high priority.