[
https://issues.apache.org/jira/browse/IGNITE-9822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16643050#comment-16643050
]
ASF GitHub Bot commented on IGNITE-9822:
----------------------------------------
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/4930
IGNITE-9822 Fix WAL archiver stop logic
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9822
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4930.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 #4930
----
commit fc6b1b4fd4bccadf850f73e3286f593e6d8c2617
Author: Alexey Goncharuk <alexey.goncharuk@...>
Date: 2018-10-09T09:31:18Z
IGNITE-9822 Fix WAL archiver stop logic
----
> 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)
