ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: Ignite: configuration changes at runtime
Date Sat, 19 Aug 2017 14:53:45 GMT
On Fri, Aug 18, 2017 at 1:57 AM, Yakov Zhdanov <yzhdanov@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 see your point. In this case, we should have a special package containing
all the runtime config properties.

> >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.

All the SomethingConfigRuintime interfaces should be exposed via JMX

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message