ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignite TC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9822) Correct WAL archiver termination is incorrectly reported as critical thread termination
Date Tue, 09 Oct 2018 16:10:00 GMT

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

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

{panel:title=No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All|http://ci.ignite.apache.org/viewLog.html?buildId=2041213&amp;buildTypeId=IgniteTests24Java8_RunAll]

> Correct WAL archiver termination is incorrectly reported as critical thread termination
> ---------------------------------------------------------------------------------------
>
>                 Key: IGNITE-9822
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9822
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Alexey Goncharuk
>            Assignee: Alexey Goncharuk
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>             Fix For: 2.8
>
>
> PDS Indexing suite is failing with exit code=130. The cause is WAL-archiver exiting and
the exit is incorrectly treated as unexpected worker termination.
> The cause appears to be IGNITE-9744. WAL archiver is changed to be a GridWorker, but
thread stop logic was not changed, as a result {{w.isCancelled()}} returns {{false}} and this
is treated as an unexpected worker termination. 



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

Mime
View raw message