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

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

{panel:title=Branch: [pull/12859/head] Base: [master] : Possible Blockers 
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Disk Page Compressions 1{color} [[tests 
1|https://ci2.ignite.apache.org/viewLog.html?buildId=8915777]]
* IgnitePdsCompressionTestSuite: 
DurableBackgroundTasksProcessorSelfTest.testConvertAfterRestoreIfNeeded - Test 
has low fail rate in base branch 0,0% and is not flaky

{panel}
{panel:title=Branch: [pull/12859/head] Base: [master] : New Tests 
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Cache 13{color} [[tests 
1|https://ci2.ignite.apache.org/viewLog.html?buildId=8913024]]
* {color:#013220}IgniteCacheTestSuite13: 
SystemViewCacheExpiryPolicyTest.testCacheViewExpiryPolicy[factory=javax.cache.configuration.FactoryBuilder$SingletonFactory@24876a7e,
 actual=SingletonFactory [expiryPlc=EternalExpiryPolicy [create=ETERNAL]]] - 
PASSED{color}

{panel}
[TeamCity *--> Run :: All* 
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8913130&buildTypeId=IgniteTests24Java8_RunAll]

> Automatically enable EVT_CONSISTENCY_VIOLATION event on consistency repair
> --------------------------------------------------------------------------
>
>                 Key: IGNITE-28069
>                 URL: https://issues.apache.org/jira/browse/IGNITE-28069
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Aleksey Plekhanov
>            Assignee: Aleksey Plekhanov
>            Priority: Major
>              Labels: ise
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Currently, consistency repair ({{control.sh --consistency repair}}) requires 
> event EVT_CONSISTENCY_VIOLATION to be enabled statically in configuration, 
> which requires cluster restart on if event was not configured properly (by 
> default). But we can enable this event in runtime during this command 
> execution and avoid cluster restart.



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

Reply via email to