baselineAutoAdjust related issue

Hello, community.

Version jdk 17, ignite 2.15.0

When automatic baseline adjustment is enabled, some nodes cannot be added to the baseline topology when the VM where the cluster node resides restarts. You must manually add nodes to the baseline topology. By the way, this problem may occur when the cluster is forcibly restarted, like deleting all ignite pods from Kubernetes.

The following figure shows the example:

Thanks
Wei Cheng

The issue names no source files, tests, or entry points. Start by reproducing the automatic baseline-adjustment behavior in Ignite 2.15.0 during a node or Kubernetes cluster restart, then trace how restarted nodes are handled; done means eligible nodes are added to the baseline topology without manual intervention.

Written by the indexing model from the issue text.