[
https://issues.apache.org/jira/browse/IGNITE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-13346:
-------------------------------------
Fix Version/s: (was: 2.10)
> “Joining persistence node to in-memory cluster couldn't be allowed”
> Verification is too strict
> ----------------------------------------------------------------------------------------------
>
> Key: IGNITE-13346
> URL: https://issues.apache.org/jira/browse/IGNITE-13346
> Project: Ignite
> Issue Type: Improvement
> Components: persistence
> Affects Versions: 2.8.1
> Reporter: YuJue Li
> Priority: Major
>
> 1.Start a node that turns on persistence and then activate
> 2.Start visor and connect to cluster
> 3.Stop the node and restart the node
> 4.the node start failer and the exception are as folloews:
> Caused by: class org.apache.ignite.spi.IgniteSpiException: Joining
> persistence node to in-memory cluster couldn't be allowed due to baseline
> auto-adjust is enabled and timeout equal to 0
> I think there may be problems with the verification logic here. There are two
> possible solutions:
> 1.Relax the restrictions and exclude the client nodes.
> 2.Point out the IP address corresponding to the in-memory cluster node, which
> is convenient for troubleshooting.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
