You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/05/07 23:25:00 UTC
[jira] [Commented] (IGNITE-8429) Unexpected error during incorrect
WAL segment decompression, causes node termination.
[ https://issues.apache.org/jira/browse/IGNITE-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16466609#comment-16466609 ]
ASF GitHub Bot commented on IGNITE-8429:
----------------------------------------
GitHub user glukos opened a pull request:
https://github.com/apache/ignite/pull/3955
IGNITE-8429 Unexpected error during incorrect WAL segment decompressi…
…on, causes node termination
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8429
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3955.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 #3955
----
commit 9b8a8472e3e782d4888de7b9ccb9329de734c21b
Author: Ivan Rakov <iv...@...>
Date: 2018-05-07T23:18:51Z
IGNITE-8429 Unexpected error during incorrect WAL segment decompression, causes node termination
----
> Unexpected error during incorrect WAL segment decompression, causes node termination.
> -------------------------------------------------------------------------------------
>
> Key: IGNITE-8429
> URL: https://issues.apache.org/jira/browse/IGNITE-8429
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Affects Versions: 2.5
> Reporter: Ivan Daschinskiy
> Assignee: Ivan Rakov
> Priority: Critical
> Labels: WAL
> Fix For: 2.5
>
>
> File decompressor failure due to incorrect (zero-length) archived segment.
> 2018-04-30 00:00:02.811 [ERROR][wal-file-decompressor%DPL_GRID%DplGridNodeName][org.apache.ignite.Ignite] Critical system error detected. Will be handled accordingly to configured handler [hnd=class o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread wal-file-decompressor%DPL_GRID%DplGridNodeName is terminated unexpectedly]]
> java.lang.IllegalStateException: Thread wal-file-decompressor%DPL_GRID%DplGridNodeName is terminated unexpectedly
> at org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileDecompressor.run(FileWriteAheadLogManager.java:2104)
> 2018-04-30 00:00:02.812 [ERROR][wal-file-decompressor%DPL_GRID%DplGridNodeName][org.apache.ignite.Ignite] JVM will be halted immediately due to the failure: [failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread wal-file-decompressor%DPL_GRID%DplGridNodeName is terminated unexpectedly]]
> touch 0000000000000754.wal
> zip 0000000000000754.wal.zip 0000000000000754.wal
> ls -l
> -rw-rw-r-- 1 dmitriy dmitriy 0 май 1 16:40 0000000000000754.wal
> -rw-rw-r-- 1 dmitriy dmitriy 190 май 1 16:46 0000000000000754.wal.zip
> Archive: /tmp/temp/0000000000000754.wal.zip
> Length Method Size Cmpr Date Time CRC-32 Name
> -------- ------ ------- ---- ---------- ----- -------- ----
> 0 Stored 0 0% 2018-05-01 16:40 00000000 0000000000000754.wal
> -------- ------- --- -------
> 0 0 0% 1 file
> We should softly handle this situation: print message in log and continue the decompression with next segment.
> We also should handle "skipped" segments and don't delete them in deleteObsoleteRawSegments().
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)