You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (JIRA)" <ji...@apache.org> on 2019/01/25 17:35:00 UTC
[jira] [Commented] (IGNITE-11048) Start node with TTL caches causes
failure handler activity
[ https://issues.apache.org/jira/browse/IGNITE-11048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16752483#comment-16752483 ]
Ignite TC Bot commented on IGNITE-11048:
----------------------------------------
{panel:title=--> Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=2907943&buildTypeId=IgniteTests24Java8_RunAll]
> Start node with TTL caches causes failure handler activity
> ----------------------------------------------------------
>
> Key: IGNITE-11048
> URL: https://issues.apache.org/jira/browse/IGNITE-11048
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.7
> Reporter: Sergey Kozlov
> Assignee: Andrey Aleksandrov
> Priority: Critical
> Attachments: 1.xml, ignite-1cecc333.0.log
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 1. Start 1 node with attached config (1.xml)
> 2. Look at node log:
> {noformat}
> [17:04:51,386][INFO][main][GridCacheProcessor] Finished restoring partition state for local groups [groupsProcessed=11, partitionsProcessed=0, time=6135ms]
> [17:04:51,387][INFO][main][GridCacheDatabaseSharedManager] Partition states information after LOGICAL RECOVERY phase:
> [17:04:54,847][SEVERE][nio-acceptor-tcp-comm-#28][G] Blocked system-critical thread has been detected. This can lead to cluster-wide undefined behaviour [threadName=ttl-cleanup-worker, blockedFor=16s]
> [17:04:54,848][WARNING][nio-acceptor-tcp-comm-#28][G] Thread [name="ttl-cleanup-worker-#45", id=74, state=WAITING, blockCnt=0, waitCnt=1]
> [17:04:54,849][SEVERE][nio-acceptor-tcp-comm-#28][] Critical system error detected. Will be handled accordingly to configured handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, super=AbstractFailureHandler [ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext [type=SYSTEM_WORKER_BLOCKED, err=class o.a.i.IgniteException: GridWorker [name=ttl-cleanup-worker, igniteInstanceName=null, finished=false, heartbeatTs=1548252278711]]]
> class org.apache.ignite.IgniteException: GridWorker [name=ttl-cleanup-worker, igniteInstanceName=null, finished=false, heartbeatTs=1548252278711]
> at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1833)
> at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1828)
> at org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:233)
> at org.apache.ignite.internal.util.worker.GridWorker.onIdle(GridWorker.java:297)
> at org.apache.ignite.internal.util.nio.GridNioServer$GridNioAcceptWorker.accept(GridNioServer.java:2938)
> at org.apache.ignite.internal.util.nio.GridNioServer$GridNioAcceptWorker.body(GridNioServer.java:2877)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> [17:04:54,849][WARNING][nio-acceptor-tcp-comm-#28][FailureProcessor] No deadlocked threads detected.
> [17:04:55,030][WARNING][nio-acceptor-tcp-comm-#28][FailureProcessor] Thread dump at 2019/01/23 17:04:55 MSK
> Thread [name="ttl-cleanup-worker-#45", id=74, state=WAITING, blockCnt=0, waitCnt=1]
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
> at o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
> at o.a.i.i.managers.discovery.GridDiscoveryManager.localJoin(GridDiscoveryManager.java:2205)
> at o.a.i.i.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:133)
> ....
> {noformat}
> Note: there's no similar issues for AI 2.5
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)