[ https://issues.apache.org/jira/browse/IGNITE-21599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17820063#comment-17820063 ]
Stephen Darlington edited comment on IGNITE-21599 at 2/23/24 1:40 PM: ---------------------------------------------------------------------- Repro: # Start Ignite 2 node (with ignite.sh) # Start AI3 node (ignite3db start) # Initialise AI3 cluster # AI3 node dies There are a bunch of warnings, but the only error I see is: 2024-02-23 13:31:04:208 +0000 [ERROR][%defaultNode%start-0][MetaStorageLeaderElectionListener] Unable to start Idle Safe Time scheduler was (Author: sdarlington): Repro: # Start Ignite 2 / GG 8 node (with ignite.sh) # Start GG9 node (ignite3db start) # Initialise GG9 cluster # GG9 node dies There are a bunch of warnings, but the only error I see is: 2024-02-23 13:31:04:208 +0000 [ERROR][%defaultNode%start-0][MetaStorageLeaderElectionListener] Unable to start Idle Safe Time scheduler > Detect AI2 running and add an error to the log > ---------------------------------------------- > > Key: IGNITE-21599 > URL: https://issues.apache.org/jira/browse/IGNITE-21599 > Project: Ignite > Issue Type: Task > Reporter: Igor Gusev > Priority: Major > Labels: ignite-3 > > Currently, it is impossible to run AI2 and AI3 in the same VM. If you try to > start AI3 node, it will stop without any specific error message for debugging > purpose. > We should check for AI2 so that users know why the node failed to start. -- This message was sent by Atlassian Jira (v8.20.10#820010)