May be let second node to finish join and enter the ring, but start rebalance after all lock will be released.
2017-05-19 12:30 GMT+03:00 ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > If we acquired a lock and a new node is joining cluster, should it wait for > lock release? > May be it could proceed joining ? > The question comes from my ticket > https://issues.apache.org/jira/browse/IGNITE-2671 > > чт, 18 мая 2017 г. в 20:05, Alexey Goncharuk <alexey.goncha...@gmail.com>: > > > Hi Aleksey, > > > > The main purpose of this method is to wait for all ongoing updates > > (transactional and atomic), initiated on the previous topology version, > to > > finish to prevent inconsistencies during rebalancing and to prevent two > > different simultaneous owners of the same lock. > > > > We will be adding documentation pages on Apache Ignite wiki which will > > explain transactions mechanics in greater detail. > > > > Hope this helps, > > AG > > > > 2017-05-18 16:50 GMT+03:00 ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > > > > > Hi Igntrs! > > > What is the point of waiting partition release in the end of > > > GridDhtPartitionsExchangeFuture#init() method ? > > > In what scenarious do we need it ? > > > -- > > > > > > *Best Regards,* > > > > > > *Kuznetsov Aleksey* > > > > > > -- > > *Best Regards,* > > *Kuznetsov Aleksey* >
