Compactions must fail if column tracker gets columns out of order
-----------------------------------------------------------------
Key: HBASE-4476
URL: https://issues.apache.org/jira/browse/HBASE-4476
Project: HBase
Issue Type: Bug
Reporter: Mikhail Bautin
Assignee: Mikhail Bautin
Fix For: 0.92.0, 0.94.0
We found this in ScanWildcardColumnTracker:
// new col < oldcol
// if (cmp < 0) {
// WARNING: This means that very likely an edit for some other family
// was incorrectly stored into the store for this one. Continue, but
// complain.
LOG.error("ScanWildcardColumnTracker.checkColumn ran " +
"into a column actually smaller than the previous column: " +
This went under the radar in our dark launch cluster when a column family name
was misspelled first, but then was "renamed" by renaming directories in the
HBase storage directory tree. We ended up with inconsistent data, but
compactions still succeeded most of the time, likely discarding part of input
data.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
