Description
For now, partition store BTree can be destroyed while vacuum in progress regardless partition reservations which causes VacuumTask failure without negative side effect (such as worker failure or any hanging).
VacuumTask successfully catch and log the exception, but further check in afterTest() method reports vacuum failure.
For now vacuum is disabled for this test.
We should fix vacuum failure properly in that case and fix CacheMvccPartitionedSqlQueriesTest.testDistributedJoinSimple() test.
Attachments
Issue Links
- relates to
-
IGNITE-6580 Cluster can fail during concurrent re-balancing and cache destruction
- Open
- links to
GitHub user rkondakov opened a pull request:
https://github.com/apache/ignite/pull/4940
IGNITE-9446: Added cache status check before running vacuum.You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9446
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4940.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4940
commit 6632c69a72fd950bad25b6b1668746d62f2fb461
Author: rkondakov <kondakov87@...>
Date: 2018-10-10T09:11:11Z
IGNITE-9446: Added cache status check before running vacuum.