Re: Getting rid of NONE cache rebalance mode

2020-07-28 Thread Ivan Pavlukhin
Alexey, Thank you for the response. > I am not sure how expiration relates to the partition ownership - once a > partition moves to a renting state, all entries are eagerly cleaned from the > memory, so there is no need for expiration. It is even better, there is nothing to do with expiration.

Re: Getting rid of NONE cache rebalance mode

2020-07-28 Thread Alexey Goncharuk
Ivan, Sorry for a delay in reply. Yes, I was thinking about the same use-case, and in this particular case an unexpected load on a 3rd-party database manifests itself. I am not sure how expiration relates to the partition ownership - once a partition moves to a renting state, all entries are eager

Re: Getting rid of NONE cache rebalance mode

2020-07-22 Thread Alexei Scherbakov
As a reminder - we already have a ticket for a deprecation of rebalanceDelay as well [1] [1] https://issues.apache.org/jira/browse/IGNITE-12662 ср, 22 июл. 2020 г. в 09:39, Alexei Scherbakov : > Ivan, > My opinion the ASYNC rebalancing is a best approach for off-loading 3-d > party store, and it

Re: Getting rid of NONE cache rebalance mode

2020-07-21 Thread Alexei Scherbakov
Ivan, My opinion the ASYNC rebalancing is a best approach for off-loading 3-d party store, and it provides consistency. +1 for deprecation of NONE in the next release - ignore NONE and use ASYNC instead For those who require absence of rebalancing for some reason still be possible to use rebalance

Re: Getting rid of NONE cache rebalance mode

2020-07-21 Thread Ivan Pavlukhin
Alexey, Thank you for explanation. I feel that I miss a couple bits to understand the picture fully. I am thinking about a case which I tend to call a Memcached use-case. There is a cache over underlying storage with read-through and expiration and without any rebalancing at all. When new nodes en

Re: Getting rid of NONE cache rebalance mode

2020-07-21 Thread Alexey Goncharuk
Ivan, In my understanding this mode does not work at all even in the presence of ForceKeysRequest which is now supposed to fetch values from peers in case of a miss. In this mode we 1) move partitions to OWNING state unconditionally, and 2) choose an arbitrary OWNING node for force keys request. T

Re: Getting rid of NONE cache rebalance mode

2020-07-20 Thread Valentin Kulichenko
+1 for deprecating/removing NONE mode. Alexey, what do you think about the SYNC mode? In my experience, it does not add much value as well. I would go as far as removing the rebalancingMode parameter altogether (probably in 3.0). -Val On Mon, Jul 20, 2020 at 11:09 AM Ivan Pavlukhin wrote: > Al

Re: Getting rid of NONE cache rebalance mode

2020-07-20 Thread Ivan Pavlukhin
Alexey, Igniters, Could you please outline motivation answering following questions? 1. Does this mode generally work correctly today? 2. Can this mode be useful at all? I can imagine that it might be useful in a transparent caching use case (if I did not misunderstand). 2020-07-20 20:39 GMT+03:

Re: Getting rid of NONE cache rebalance mode

2020-07-20 Thread Pavel Tupitsyn
+1 More evidence: https://stackoverflow.com/questions/62902640/apache-ignite-cacherebalancemode-is-not-respected-by-nodes On Mon, Jul 20, 2020 at 8:26 PM Alexey Goncharuk wrote: > Igniters, > > I would like to run the idea of deprecating and probably ignoring the NONE > rebalance mode by the co