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 Wed, 23 Aug 2017 01:53:45 GMT
On Tue, Aug 22, 2017 at 4:43 AM, Yakov Zhdanov <yzhdanov@apache.org> wrote:

> >Not really. What if the user configured Ignite from Java API, without any
> >XML. What will be saved? To prevent this ambiguity, I think the cleanest
> >way is to ask user to save the configuration to a file explicitly.
> I think it does not matter too much how the grid was configured. In any
> case IgniteConfiguration object is created. And we will be allowing to
> change only very few parameters that are mostly of primitive type or enum.
> Once changed configuration is saved to metastore. When restarting we should
> apply it by default or allow user to override it with provided one.

I would prefer that users explicitly specify which configuration file to
use on startup. This will prevent any magic. Still think that explicit call
to saveConfigurationFile(...) is the best approach.

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