[
https://issues.apache.org/jira/browse/KUDU-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17291940#comment-17291940
]
ASF subversion and git services commented on KUDU-2233:
-------------------------------------------------------
Commit 930fe5bf8f02f97061bddcfa4199ab5a25f15419 in kudu's branch
refs/heads/master from Andrew Wong
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=930fe5b ]
test: add more natural test for KUDU-2233
I have a patch in-flight that touches an area of the code around where
we expect the infamous KUDU-2233 crash. Before merging it, I'd like to
ensure the graceful handling of this corruption is unaffected,
especially in cases where data has previously been corrupted and we've
just upgraded to a newer version of Kudu.
This patch adds such a test case, where data is corrupted but does not
result in a crash, and the tserver is restarted with bits that handle
corruption gracefully. In doing so, this patch also adds an off switch
to all of the guardrails we installed for KUDU-2233.
Change-Id: Icac3ad0a1b6bb9b17d5b6a901dc5bba79c0840fa
Reviewed-on: http://gerrit.cloudera.org:8080/17114
Reviewed-by: Alexey Serbin <aser...@cloudera.com>
Tested-by: Andrew Wong <aw...@cloudera.com>
> Check failure during compactions: pv_delete_redo != nullptr
> -----------------------------------------------------------
>
> Key: KUDU-2233
> URL: https://issues.apache.org/jira/browse/KUDU-2233
> Project: Kudu
> Issue Type: Bug
> Components: tablet, tserver
> Affects Versions: 1.4.0
> Reporter: Andrew Wong
> Assignee: Andrew Wong
> Priority: Major
> Fix For: 1.7.0
>
>
> There have been a couple of reports of a check failure during compactions at
> least from 1.4, pasted below:
> {noformat}
> F1201 14:55:37.052140 10508 compaction.cc:756] Check failed: pv_delete_redo
> != nullptr
> *
> **
> *** Check failure stack trace: ***
> Wrote minidump to
> /var/log/kudu/minidumps/kudu-tserver/215cde39-7795-0885-0b51038d-771d875e.dmp
> *** Aborted at 1512161737 (unix time) try "date -d @1512161737" if you are
> using GNU date ***
> PC: @ 0x3ec3632625 (unknown)
> *** SIGABRT (@0x3b98eec0000028e3) received by PID 10467 (TID 0x7f8b02c58700)
> from PID 10467; stack trace: ***
> @ 0x3ec3a0f7e0 (unknown)
> @ 0x3ec3632625 (unknown)
> @ 0x3ec3633e05 (unknown)
> @ 0x1b53f59 (unknown)
> @ 0x8b9f6d google::LogMessage::Fail()
> @ 0x8bbe2d google::LogMessage::SendToLog()
> @ 0x8b9aa9 google::LogMessage::Flush()
> @ 0x8bc8cf google::LogMessageFatal::~LogMessageFatal()
> @ 0x9db0fe kudu::tablet::FlushCompactionInput()
> @ 0x9a056a kudu::tablet::Tablet::DoMergeCompactionOrFlush()
> @ 0x9a372d kudu::tablet::Tablet::Compact()
> @ 0x9bd8d1 kudu::tablet::CompactRowSetsOp::Perform()
> @ 0x1b4145f kudu::MaintenanceManager::LaunchOp()
> @ 0x1b8da06 kudu::ThreadPool::DispatchThread()
> @ 0x1b888ea kudu::Thread::SuperviseThread()
> @ 0x3ec3a07aa1 (unknown)
> @ 0x3ec36e893d (unknown)
> @ 0x0 (unknown)}}
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
