[
https://issues.apache.org/jira/browse/IGNITE-12600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032269#comment-17032269
]
Ilya Kasnacheev commented on IGNITE-12600:
------------------------------------------
[~akalashnikov] It will cause nodes to fail during cluster start-up, which is
not tolerable.
I think you are thinking of a developer scenario where nodes are started in
sequential, controlled fashion, and it is possible to call APIs between nodes'
start-up.
This is not the case with e.g. K8S where nodes are started totally
independently and out of control.
My point, auto-adjust can wreck a cluster before any API calls can be
realistically made by user.
> 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)
