Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

Ivan, I think your version is better, because it handles cases when several nodes are left sequentially, so no needs to shrink baseline for each node left. New version also saves some resources using internal scheduler. 2018-04-18 20:41 GMT+03:00 Ivan Rakov : > I can suggest an improvement to Ba

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

I can suggest an improvement to BaselineWatcher by Pavel. I've added a new version to https://issues.apache.org/jira/browse/IGNITE-8241 comments. Pavel, what do you think? Best Regards, Ivan Rakov On 17.04.2018 20:47, Denis Magda wrote: Thanks, Pavel! Alexey, Ivan, could you check that there

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

On Tue, Apr 17, 2018 at 4:38 PM, Denis Magda wrote: > Dmitriy, > > We don't want to disable the baseline topology for the scenario discussed > here. The goal is to make it more flexible by triggering the rebalancing in > some circumstances. > > As for the SAFE or AGGRESSIVE policies, haven't seen

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

Dmitriy, We don't want to disable the baseline topology for the scenario discussed here. The goal is to make it more flexible by triggering the rebalancing in some circumstances. As for the SAFE or AGGRESSIVE policies, haven't seen the discussion on the dev. So, not sure what it's intended for (u

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

On Tue, Apr 17, 2018 at 10:47 AM, Denis Magda wrote: > Thanks, Pavel! > > Alexey, Ivan, could you check that there are no any pitfalls in the example > and it can be used as a template for our users? > https://issues.apache.org/jira/secure/attachment/ > 12919452/BaselineWatcher.java Denis, I th

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

Thanks, Pavel! Alexey, Ivan, could you check that there are no any pitfalls in the example and it can be used as a template for our users? https://issues.apache.org/jira/secure/attachment/12919452/BaselineWatcher.java -- Denis On Tue, Apr 17, 2018 at 10:40 AM, Pavel Kovalenko wrote: > Denis, >

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

Denis, I've attached example how to manage baseline automatically (It's named BaselineWatcher). It's just an concept and doesn't cover all possible cases, but might be good for a start. 2018-04-13 2:14 GMT+03:00 Denis Magda : > Pavel, thanks for the suggestions. They would definitely work out. I

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

Pavel, thanks for the suggestions. They would definitely work out. I would document the one with the event subscription: https://issues.apache.org/jira/browse/IGNITE-8241 Could you help preparing a sample code snippet with such a listener that will be added to the doc? I know that there are some c

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

Guys, I also heard complaints about absence of option to automatically change baseline topology. They absolutely make sense. What Pavel suggested will work as a workaround. I think, in future releases we should give user an option to enable a similar behavior via Ignite Configuration. It may b

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

Denis, It's just one of the ways to implement it. We also can subscribe on node join / fail events to properly track downtime of a node. 2018-04-12 19:38 GMT+03:00 Pavel Kovalenko : > Denis, > > Using our API we can implement this task as follows: > Do each minute: > 1) Get all alive server node

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

Denis, Using our API we can implement this task as follows: Do each minute: 1) Get all alive server nodes consistent ids => ignite().context().discovery().aliveServerNodes() => mapToConsistentIds(). 2) Get current baseline topology => ignite().cluster().currentBaselineTopology() 3) For each node i

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

Pavel, Val, So, it means that the rebalancing will be initiated only after an administrator remove the failed node from the topology, right? Next, imagine that you are that IT administrator who has to automate the rebalancing activation if the node failed and not recovered within 1 minute. What w

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

Denis, In case of incomplete baseline topology IgniteCache.rebalance() will do nothing, because this event doesn't trigger partitions exchange or affinity change, so states of existing partitions are hold. 2018-04-11 22:27 GMT+03:00 Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Denis,

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

Denis, In my understanding, in this case you should remove node from BLT and that will trigger the rebalancing, no? -Val On Wed, Apr 11, 2018 at 12:23 PM, Denis Magda wrote: > Igniters, > > As we know the rebalancing doesn't happen if one of the nodes goes down, > thus, shrinking the baseline

Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

Igniters, As we know the rebalancing doesn't happen if one of the nodes goes down, thus, shrinking the baseline topology. It complies with our assumption that the node should be recovered soon and there is no need to waste CPU/memory/networking resources of the cluster shifting the data around. H