Re: Partition reserve/release asymmetry

2020-01-10 Thread Anton Vinogradov
Everything is fine. Merged to master branch. On Fri, Jan 10, 2020 at 9:48 AM Anton Vinogradov wrote: > >> Does the issue reproduce in > >> subsequent runs? > Unfortunately no. > We performed 30+ runs without "success". > > >> I think we can add an assertion to > >>

Re: Partition reserve/release asymmetry

2020-01-09 Thread Anton Vinogradov
>> Does the issue reproduce in >> subsequent runs? Unfortunately no. We performed 30+ runs without "success". >> I think we can add an assertion to >> GridDhtLocalPartition#destroy() method to check that reservations is 0 Ok, I will check and merge in case of success. Created the Issue to handle

Re: Partition reserve/release asymmetry

2020-01-09 Thread Alexey Goncharuk
Hello Anton, Thanks for digging into this. The logic with checking the reservations count seems fishy to me as well, so I have no objections with the suggested change. This "if" statement does not answer why the partition was being destroyed during the commit, though. Does the issue reproduce in

Partition reserve/release asymmetry

2020-01-08 Thread Anton Vinogradov
Folks, Yardstick run (opt-serial-put-get-1-backup) failed with interesting exception: Critical system error detected. Will be handled accordingly to configured handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet