Re: Question: different setting for nodes.

2020-02-06 Thread Ilya Kasnacheev
Hello! How about we introduce a *developer warning* about this inconsistency, see what happens in a release with this warning, and then maybe eventually turn it into error? Please note that plain error will be breaking existing code which should make it blocker for minor releases. Regards, -- I

Re: Question: different setting for nodes.

2020-02-06 Thread Alexey Goncharuk
Nikolay, This sounds like a philosophical question :) By rigid I mean inability to change some properties without whole cluster restart, and I do think it's bad. I have a good example in mind - the number of threads running rebalance. Originally, we added a validation check for this configuration

Re: Question: different setting for nodes.

2020-02-06 Thread Nikolay Izhikov
Hello, Alexey. Sorry, my question is not related to the current discussion > this makes the cluster configuration rigid; Is it a bad thing to make cluster node configuration rigid? > 6 февр. 2020 г., в 12:20, Alexey Goncharuk > написал(а): > > Vladimir, > > In current implementation the fl

Re: Question: different setting for nodes.

2020-02-06 Thread Alexey Goncharuk
Vladimir, In current implementation the flag does not change if data is kept or cleared from memory - after deactivation the internal structures are cleared and only data region is kept allocated. If you add a validation for this flag, you forbid users to do a rolling cluster restart and enable/di

Re: Question: different setting for nodes.

2020-02-05 Thread Maxim Muzafarov
Folks, I think it's a common problem for such system properties (which may be different on different nodes and which may lead to unpredictable cluster behaviour). The same mentioned by Ivan here [1]. Is it better to validate (somehow) all system properties, for instance, started with IGNITE_ pre

Re: Question: different setting for nodes.

2020-02-05 Thread Nikolay Izhikov
Vladimir. This looks like a bug to me. Can you, please, prepare the simple reproducer for this issue and it’s consequences? > 5 февр. 2020 г., в 17:08, Vladimir Steshin написал(а): > > Hi, folks. > > > > I recently found that one node might be started with flag > reuse-memory-on-deactivat

Question: different setting for nodes.

2020-02-05 Thread Vladimir Steshin
Hi, folks. I recently found that one node might be started with flag reuse-memory-on-deactivate [1] set off while another node might be configured with the flag enabled. This ability hinders prediction of cluster behavior on deactivation/activation. One node keeps data in memory, other doesn’t.