[
https://issues.apache.org/jira/browse/IGNITE-21386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Gusakov updated IGNITE-21386:
------------------------------------
Description:
At the moment, runtime updates for storage profiles configurations is now
working by two reasons:
- The node attributes will be updated only after the node restart anyway. So
there is no actual meaning to add the storage regions in runtime, because the
node will not be marked as an target for this storage profile until node restart
- [minor] At the moment InjectConfiguration mechanism is not provide the
configuration change triggers. So, if storage engine configuration will listen
configuration in runtime - all InjectConfiguration based tests with concrete
storage profile configurations will fail.
> Fix hot loading for storage profiles if needed
> ----------------------------------------------
>
> Key: IGNITE-21386
> URL: https://issues.apache.org/jira/browse/IGNITE-21386
> Project: Ignite
> Issue Type: Improvement
> Reporter: Kirill Gusakov
> Priority: Major
> Labels: ignite-3
>
> At the moment, runtime updates for storage profiles configurations is now
> working by two reasons:
> - The node attributes will be updated only after the node restart anyway. So
> there is no actual meaning to add the storage regions in runtime, because the
> node will not be marked as an target for this storage profile until node
> restart
> - [minor] At the moment InjectConfiguration mechanism is not provide the
> configuration change triggers. So, if storage engine configuration will
> listen configuration in runtime - all InjectConfiguration based tests with
> concrete storage profile configurations will fail.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
