You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Mikhail Pochatkin (Jira)" <ji...@apache.org> on 2023/04/13 09:47:00 UTC

[jira] [Updated] (IGNITE-19189) Ignite node re-writes configuration file on start

     [ https://issues.apache.org/jira/browse/IGNITE-19189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mikhail Pochatkin updated IGNITE-19189:
---------------------------------------
    Epic Link: IGNITE-19280

> Ignite node re-writes configuration file on start
> -------------------------------------------------
>
>                 Key: IGNITE-19189
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19189
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Ivan Bessonov
>            Priority: Major
>              Labels: ignite-3
>
> The way it works right now:
>  * we start the node
>  * we read the content of configuration file
>  * we apply the content as a single change
>  * this change is writing the content back into file
> This makes it impossible to run the node with read-only configuration file.
> I think that making {{LocalFileConfigurationStorage}} aware of the bootstrap procedure is not too bad of a solution. Basically, all we need is to ignore the first call of {{{}LocalFileConfigurationStorage#saveValues{}}}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)