Ivan Zlenko created IGNITE-26852:
------------------------------------
Summary: Storage Profile Verification
Key: IGNITE-26852
URL: https://issues.apache.org/jira/browse/IGNITE-26852
Project: Ignite
Issue Type: Epic
Reporter: Ivan Zlenko
Our current storage profile implementation allows nodes within a live topology
to have inconsistent storage engine configurations under the same profile name.
This creates serious problems:
* A single storage profile can map to different engines across nodes (e.g.,
aipersist on one node, rocksdb on another)
* When tables are created using such a profile, behavior becomes unpredictable
and varies by node
* Critical scenarios like mixing aipersist and aimem engines under the same
profile can lead to data loss
*Proposed Solution:*
Implement validation to prevent nodes from joining the topology if their
storage profile configuration conflicts with existing nodes. Specifically,
reject nodes where the same profile name maps to different storage engines than
what's already established in the cluster.
*Example:*
* Node A: profile_x → rocksdb
* Node B attempts to join: profile_x → aipersist
* Result: Node B should be rejected from the topology
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
