[jira] [Resolved] (HBASE-4476) Compactions must fail if column tracker gets columns out of order

["stack (Resolved) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-4476.
--------------------------

      Resolution: Fixed
    Hadoop Flags: Reviewed

Committed branch and trunk.  Thanks for the fixup Mikhail.
                
> 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
>
>         Attachments: HBASE-4476_v2_2011-09-27_17_38_48.patch
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira