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, -- Ilya Kasnacheev ср, 5 февр. 2020 г. в 18:40, Maxim Muzafarov <mmu...@apache.org>: > 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_ prefix, on all nodes the same way as we > do it for IgniteConfiguration? > > [1] > https://issues.apache.org/jira/browse/IGNITE-12470?focusedCommentId=17004207&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17004207 > > On Wed, 5 Feb 2020 at 17:20, Nikolay Izhikov <nizhi...@apache.org> wrote: > > > > 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 <vlads...@gmail.com> > написал(а): > > > > > > 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. > > > > > > Should we check this flag is set equally on all nodes? Is this an > issue? We > > > might prevent node start if it has different setting. > > > > > > > > > > > > [1] IgniteSystemProperties#IGNITE_REUSE_MEMORY_ON_DEACTIVATE > > >
