You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2022/08/16 15:09:00 UTC

[jira] [Commented] (IGNITE-17531) Tests covers consistency repair at inconsistent cluster with nonfinalized counters

    [ https://issues.apache.org/jira/browse/IGNITE-17531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17580364#comment-17580364 ] 

Ignite TC Bot commented on IGNITE-17531:
----------------------------------------

{panel:title=Branch: [pull/10199/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10199/head] Base: [master] : No new tests found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6561445&amp;buildTypeId=IgniteTests24Java8_RunAll]

> Tests covers consistency repair at inconsistent cluster with nonfinalized counters
> ----------------------------------------------------------------------------------
>
>                 Key: IGNITE-17531
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17531
>             Project: Ignite
>          Issue Type: Sub-task
>            Reporter: Anton Vinogradov
>            Assignee: Anton Vinogradov
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Test must 
> 1) Generate data with missed unordered update counter (gaps)
> 2) Perform restart with rebalance (full or historiical)
> 3) Check consistency on restart using idle_verify
> 4) Fix inconsistency using consistency_repair 
> 5) Check result using idle_verify
> The main goal is to check recovery at production (where cluster may fail under the load) tools and approaches.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)