[
https://issues.apache.org/jira/browse/IGNITE-25536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtsev updated IGNITE-25536:
-----------------------------------------
Description:
During Ignite start, after all components have been started, we call a special
method that notifies all of the configuration listeners as if all configuration
values have been created in runtime, even though the configuration component
may have been initialized with these values. This logic is cryptic and
inconsistent: no other component, e.g. Meta Storage or Catalog, replays its
notifications on start. Moreover, we don't call these notifications for node
configuration after IGNITE-25425.
It is proposed to remove these notifications for the cluster configuration as
well and update the dependent components to recover their state manually on
component start.
> Do not notify configuration listeners on start
> ----------------------------------------------
>
> Key: IGNITE-25536
> URL: https://issues.apache.org/jira/browse/IGNITE-25536
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksandr Polovtsev
> Assignee: Aleksandr Polovtsev
> Priority: Major
> Labels: ignite-3
>
> During Ignite start, after all components have been started, we call a
> special method that notifies all of the configuration listeners as if all
> configuration values have been created in runtime, even though the
> configuration component may have been initialized with these values. This
> logic is cryptic and inconsistent: no other component, e.g. Meta Storage or
> Catalog, replays its notifications on start. Moreover, we don't call these
> notifications for node configuration after IGNITE-25425.
> It is proposed to remove these notifications for the cluster configuration as
> well and update the dependent components to recover their state manually on
> component start.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
