[
https://issues.apache.org/jira/browse/IGNITE-9516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610604#comment-16610604
]
ASF GitHub Bot commented on IGNITE-9516:
----------------------------------------
GitHub user pavlukhin opened a pull request:
https://github.com/apache/ignite/pull/4728
IGNITE-9516: workaround hanging vacuum after test
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9516
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4728.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 #4728
----
commit 1dfc1a5660196a5ce72c2fe559c915f97936cd60
Author: ipavlukhin <vololo100@...>
Date: 2018-09-11T09:11:33Z
fail tests depending on Cache.size for cache API with issue reference, set
timeout for vacuum cleanup after test
----
> Vaccum cannot complete after rebalance
> --------------------------------------
>
> Key: IGNITE-9516
> URL: https://issues.apache.org/jira/browse/IGNITE-9516
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
> Reporter: Ivan Pavlukhin
> Assignee: Ivan Pavlukhin
> Priority: Major
>
> In mvcc tests we wait for full Vacuum cleanup in {{afterTest}} method in a
> sake of tests isolation.
> {{org.apache.ignite.internal.processors.cache.mvcc.CacheMvccTransactionsTest#testRebalanceSimple}}
> hangs waiting Vacuum to complete. Most likely it was broken after
> implementing {{Cache.size}} for SQL operations over mvcc caches. Size for
> Cache API was not implemented properly (see related ticket).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
