[
https://issues.apache.org/jira/browse/IGNITE-10671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726578#comment-16726578
]
Ignite TC Bot commented on IGNITE-10671:
----------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper (Discovery) 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2609722]]
* GridCachePartitionedNodeRestartTest.testRestartWithTxFourNodesNoBackups (last
started)
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2609783&buildTypeId=IgniteTests24Java8_RunAll]
> Double initialization of segmentAware and FileArchiver lead to race breaking
> file compression.
> ----------------------------------------------------------------------------------------------
>
> Key: IGNITE-10671
> URL: https://issues.apache.org/jira/browse/IGNITE-10671
> Project: Ignite
> Issue Type: Bug
> Reporter: Pavel Voronkin
> Assignee: Pavel Voronkin
> Priority: Critical
> Fix For: 2.8
>
> Attachments: WalCompactionSwitchOverTest.java
>
>
> Race is painful when you switch your cluster from walCompaction=false to
> walCompaction=true.
> The same FileCompressor instance will use different segmentAwares due to
> start0() is called twice which leads to inconsistent behaviour and errors
> during compaction, basically we will try to archive files twice concurrently.
> See reproducer in attachment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
