[
https://issues.apache.org/jira/browse/IGNITE-12074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16907655#comment-16907655
]
Andrey Kuznetsov edited comment on IGNITE-12074 at 8/14/19 9:56 PM:
--------------------------------------------------------------------
By default, {{systemWorkerBlockedTimeout}} is equal to
{{failureDetectionTimeout}}, so the latter affects blocked system workers
detection. It looks like you need to increase {{systemWorkerBlockedTimeout}}.
BTW, it's better to ask such a question at Ignite Users mailing list before
creating an issue.
was (Author: andrey-kuznetsov):
By default, {{systemWorkerBlockedTimeout}} is equal to
{{failureDetectionTimeout}}, so the latter affects blocked system workers
detection. It looks like you need to increase {{systemWorkerBlockedTimeout}}.
BTW, the it's better to ask such a question at Ignite Users mailing list before
creating an issue.
> setFailureDetectionTimeout causes Critical system error detected in log
> -----------------------------------------------------------------------
>
> Key: IGNITE-12074
> URL: https://issues.apache.org/jira/browse/IGNITE-12074
> Project: Ignite
> Issue Type: Bug
> Reporter: chin
> Priority: Major
>
> If I do
> setFailureDetectionTimeout(4000);
> then the log is filled with this
> {noformat}
> 2019-08-13T15:59:17.792 SEVERE
> org.apache.ignite.internal.processors.failure.FailureProcessor.process
> DataGrid :: Critical system error detected. Will be handled accordingly to
> configured handler [hnd=StopNodeFailureHandler [super=AbstractFailureHandler
> [ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED]]], failureCtx=FailureContext
> [type=SYSTEM_WORKER_BLOCKED, err=class o.a.i.IgniteException: GridWorker
> [name=partition-exchanger,
> igniteInstanceName=GwClientDGConnectionService-1565726338232--1-[abc],
> finished=false, heartbeatTs=1565726352914]]]
> class org.apache.ignite.IgniteException: GridWorker
> [name=partition-exchanger,
> igniteInstanceName=GwClientDGConnectionService-1565726338232--1-[abc],
> finished=false, heartbeatTs=1565726352914]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1831)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1826)
> 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.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:221)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> 2019-08-13T15:59:17.792 WARNING
> org.apache.ignite.internal.util.IgniteUtils.dumpThreads
> DataGrid :: No deadlocked threads detected.{noformat}
> The nodes are all on my local machine so there's no network latency or
> anything.
> Despite the logs, there doesn't seem to be any issue with the app running.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
