[
https://issues.apache.org/jira/browse/IGNITE-12600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17031391#comment-17031391
]
Anton Kalashnikov commented on IGNITE-12600:
--------------------------------------------
[~ilyak] I don't know Ignite supports a mixed cluster or not. But
specifically, this message which you provided in the description is not a bug.
This guard message which tells the user that auto-adjust is enabled right now
and timeout equal to 0 what is the default for the in-memory cluster. But when
the user added to cluster the persistent node it's very dangerous to leave
these settings untouchable because it can lead to lost data. So the user can
disable the auto-adjust, added the node and enable it again or the user can
just disable it constantly or change the timeout. Maybe it is not a good
solution for such a case but nobody proposed a better solution.
> Baseline auto-adjust makes it impossible to assemble mixed persistence
> clusters
> -------------------------------------------------------------------------------
>
> Key: IGNITE-12600
> URL: https://issues.apache.org/jira/browse/IGNITE-12600
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Reporter: Ilya Kasnacheev
> Priority: Major
>
> If you try to start a cluster of two nodes, where A only has default
> non-persistent region, and B also has a persistent non-default region, it
> will fail with:
> {code}
> 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
> {code}
> However, there seem to be no configuration settings to actually disable this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
