Todd Lipcon created KUDU-1477:
---------------------------------
Summary: Pending COMMIT message for failed write operation can
prevent tablet startup
Key: KUDU-1477
URL: https://issues.apache.org/jira/browse/KUDU-1477
Project: Kudu
Issue Type: Bug
Components: tablet
Affects Versions: 0.9.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Critical
I had a workload running which generated a lot of writes for duplicate keys. In
this case, a commit message only has bad statuses, and no mutated stores. This
triggers the following code path:
{code}
if (entry.second->commit().op_type() == WRITE_OP &&
!AreAnyStoresActive(entry.second->commit())) {
DumpReplayStateToLog(state);
TabletSuperBlockPB super;
WARN_NOT_OK(meta_->ToSuperBlock(&super), "Couldn't build
TabletSuperBlockPB.");
return Status::Corruption(Substitute("CommitMsg was pending but it did
not refer "
"to any active memory stores. Commit: $0. TabletMetadata: $1",
entry.second->commit().ShortDebugString(),
super.ShortDebugString()));
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
