It looks like very useful and natural thing having the parameters change on the fly. Maybe we should design something like OLCC (on-line configuration change) module, which will request different procedures for different bunch of parameters. All the parameters, this way, will be splitted into several groups. For example in the worst case, when all the grid has to be synchronized for particular parameter change, some preparation on the grid has to be performed, than when all the nodes reports readiness, the parameter change could be initiated. On the opposite if it is parameter configured per node, OLCC state machine will work simpler without inter-node communication.
On Mon, Aug 21, 2017 at 4:21 PM, Yakov Zhdanov <yzhda...@apache.org> wrote: > >I see your point. In this case, we should have a special package > containing > >all the runtime config properties. > > Dmitry, I think this will be a mess. > > Igniters, any more opinions? > > --Yakov > -- Alexey Dmitriev, VP Engineering *GridGain Systems* www.gridgain.com
