You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2018/10/09 16:14:00 UTC
[jira] [Resolved] (IGNITE-9822) Correct WAL archiver termination is
incorrectly reported as critical thread termination
[ https://issues.apache.org/jira/browse/IGNITE-9822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Goncharuk resolved IGNITE-9822.
--------------------------------------
Resolution: Fixed
Merged to master.
> 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)