You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2021/03/15 14:20:00 UTC
[jira] [Commented] (IGNITE-14079) Add test for checking partition
eviction order
[ https://issues.apache.org/jira/browse/IGNITE-14079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301670#comment-17301670 ]
Maxim Muzafarov commented on IGNITE-14079:
------------------------------------------
Folks, the build failing with the following error:
https://travis-ci.com/github/apache/ignite/jobs/491166984
{code}
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:java (default) on project apache-ignite: An exception occured while executing the Java class. null: InvocationTargetException: All test classes must be include in any test suite or mark with the @Ignore annotation.
[ERROR] List of non-suited classes (1 items):
[ERROR] org.apache.ignite.internal.processors.cache.distributed.dht.topology.PartitionEvictionOrderTest
{code}
Can you please fix?
> Add test for checking partition eviction order
> ----------------------------------------------
>
> Key: IGNITE-14079
> URL: https://issues.apache.org/jira/browse/IGNITE-14079
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.9.1
> Reporter: Mirza Aliev
> Assignee: Mirza Aliev
> Priority: Major
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Add test to check that {{CacheRebalanceMode#SYNC}} caches are evicted before {{CacheRebalanceMode#ASYNC}}. It is important because otherwise can lead to significant start-up delays. Ignite can send some fat {{ASYNC}} cache groups for eviction first and after this only add system cache, which is {{SYNC}}, for eviction as result sys cache will wait in queue and node startup will be blocked until fat partitions will be evicted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)