ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Goncharuk <alexey.goncha...@gmail.com>
Subject Getting rid of NONE cache rebalance mode
Date Mon, 20 Jul 2020 17:25:47 GMT

I would like to run the idea of deprecating and probably ignoring the NONE
rebalance mode by the community. It's in the removal list for Ignite 3.0
[1], but it looks like it still confuses and creates issues for users [2].

What about deprecating it in one of the next releases and even ignoring
this constant in further releases, interpreting it as ASYNC, before Ignite
3.0? I find it hard to believe that any Ignite user actually has
RebalanceMode.NONE set in their configuration due to its absolutely
unpredictable behavior.

Thanks for your thoughts,


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