[
https://issues.apache.org/jira/browse/IGNITE-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15676093#comment-15676093
]
Ksenia Rybakova commented on IGNITE-3358:
-----------------------------------------
One more case, NPE should also be fixed
{noformat}
[02:09:55,475][INFO ][grid-timeout-worker-#7%null%][IgniteKernal]
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=71ff4355, name=null, uptime=01:19:40:080]
^-- H/N/C [hosts=8, nodes=25, CPUs=128]
^-- CPU [cur=3.5%, avg=3.92%, GC=0%]
^-- Heap [used=1303MB, free=68.17%, comm=4096MB]
^-- Non heap [used=46MB, free=63.75%, comm=50MB]
^-- Public thread pool [active=0, idle=0, qSize=0]
^-- System thread pool [active=1, idle=31, qSize=14]
^-- Outbound messages queue [size=1]
[02:09:58,091][WARN ][grid-nio-worker-0-#9%null%][TcpCommunicationSpi] Failed
to process selector key (will close): GridSelectorNioSessionImpl
[selectorIdx=0, queueSize=0, writeBuf=java.nio.DirectByteBuffer[pos=0 lim=32768
cap=32768], re
[02:09:58,092][WARN ][grid-nio-worker-0-#9%null%][TcpCommunicationSpi] Closing
NIO session because of unhandled exception [cls=class
o.a.i.i.util.nio.GridNioException, msg=Connection reset by peer]
[02:09:58,115][WARN ][tcp-comm-worker-#1%null%][TcpCommunicationSpi] Connect
timed out (consider increasing 'failureDetectionTimeout' configuration
property) [addr=/172.25.1.35:47100, failureDetectionTimeout=30000]
[02:09:58,116][WARN ][tcp-comm-worker-#1%null%][TcpCommunicationSpi] Failed to
connect to a remote node (make sure that destination node is alive and
operating system firewall is disabled on local and remote hosts)
[addrs=[/172.25.1.35:4
<02:09:58><benchmark-worker-28><yardstick> The benchmark of random operation
failed.
java.lang.NullPointerException
at
org.apache.ignite.yardstick.IgniteBenchmarkUtils.doInTransaction(IgniteBenchmarkUtils.java:62)
at
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeInTransaction(IgniteCacheRandomOperationBenchmark.java:645)
at
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.test(IgniteCacheRandomOperationBenchmark.java:151)
at
org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:176)
at java.lang.Thread.run(Thread.java:745)
Finishing main test [ts=1479424198130, date=Fri Nov 18 02:09:58 MSK 2016]
ERROR: Shutting down benchmark driver to unexpected exception.
Type '--help' for usage.
java.lang.NullPointerException
at
org.apache.ignite.yardstick.IgniteBenchmarkUtils.doInTransaction(IgniteBenchmarkUtils.java:62)
at
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeInTransaction(IgniteCacheRandomOperationBenchmark.java:645)
at
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.test(IgniteCacheRandomOperationBenchmark.java:151)
at
org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:176)
at java.lang.Thread.run(Thread.java:745)
{noformat}
> Yardstick: log exception that causes driver shutdown
> ----------------------------------------------------
>
> Key: IGNITE-3358
> URL: https://issues.apache.org/jira/browse/IGNITE-3358
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ksenia Rybakova
> Priority: Critical
> Fix For: 1.9
>
>
> Some times driver stops during load test with the errors like:
> {noformat}
> ERROR: The benchmark of random operation failed.
> Type '--help' for usage.
> Finishing main test [ts=1466613716339, date=Wed Jun 22 09:41:56 PDT 2016]
> ERROR: Shutting down benchmark driver to unexpected exception.
> Type '--help' for usage.
> {noformat}
> But there is no info which exactly exception caused this error. If we have
> many exceptions in the log it's impossible to identify the root cause.
> Please, add stack trace of the exception to the error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
