ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-10671) Double initialization of segmentAware and FileArchiver lead to race breaking file compression.
Date Thu, 13 Dec 2018 16:13:00 GMT

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

ASF GitHub Bot commented on IGNITE-10671:
-----------------------------------------

GitHub user voropava opened a pull request:

    https://github.com/apache/ignite/pull/5665

    IGNITE-10671 Introduced state machine to handle lifecycle of start/ac…

    …tivate/stop.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-10671

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/5665.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 #5665
    
----
commit 467a0916286482ffa41362e5f88307695912048c
Author: Pavel Voronkin <pvoronkin@...>
Date:   2018-12-13T16:10:01Z

    IGNITE-10671 Introduced state machine to handle lifecycle of start/activate/stop.

----


> 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
>         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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message