You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vaibhav Shrivastava (Jira)" <ji...@apache.org> on 2023/10/27 11:17:00 UTC
[jira] [Commented] (IGNITE-20690) Ignite client nodes are getting terminated when we stop the ignite server.
[ https://issues.apache.org/jira/browse/IGNITE-20690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780316#comment-17780316 ]
Vaibhav Shrivastava commented on IGNITE-20690:
----------------------------------------------
Hello Team
Is there any update on this?
> Ignite client nodes are getting terminated when we stop the ignite server.
> --------------------------------------------------------------------------
>
> Key: IGNITE-20690
> URL: https://issues.apache.org/jira/browse/IGNITE-20690
> Project: Ignite
> Issue Type: Wish
> Affects Versions: 2.15
> Reporter: Vaibhav Shrivastava
> Priority: Major
>
> Hello Team
> We recently moved our project to ignite 2.15.0 and after some dev testing we found out that after stopping the ignite server all the cluster nodes are getting forcibly terminated.
> {noformat}
> ERROR (Ignite) - Critical system error detected. Will be handled accordingly to configured handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext [type=SEGMENTATION, err=null]]{noformat}
> We want our nodes to wait indefinitely for server to come up.
> Also wanted to know why we are terminating all client nodes is this the default behaviour.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)