Just as idea... Can we have reference to read-only "initialConfig" - a config node was started with. And current "mutable via special API" config?
Having this we could show in some management tool what was changed (for example, TeamCity has such functionality - history of who and what was changed in build properties). On Fri, Aug 18, 2017 at 3:57 PM, Yakov Zhdanov <yzhda...@apache.org> wrote: > Here is the list of params that can be changed - https://cwiki.apache.org/ > confluence/display/IGNITE/Allow+Configuration+Settings+Change+At+Runtime > > >No, the Ignite configuration is what Ignite receives on startup. Runtime > >changes are outside of configuration, especially given that if cluster > >restarts, they are likely lost. > > Again, how you provide all-in-one-place current node configuration? Also, > why changes should be lost? In case of persistence they should not be lost, > moreover, nodes joining with previous configuration should pick up current > properties of running nodes. > > >I think providing API is important for users who want to integrate Ignite > >with their own management tools. > > This maybe done via JMX. Currently, I guess we expose only configuration > toString() via it. > > --Yakov > -- Alexey Kuznetsov
