[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliott Clark updated HBASE-6769:
---------------------------------
Attachment: HBASE-6769-0.94-1.patch
Here's the patch without the FailedSanityCheckException. I put in comments
around everywhere that catches the exception so hopefully that will keep things
sane.
TestHRegion and TestFromClientSide are both passing on my machine locally.
Running the rest of the suite right now.
> HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
> -----------------------------------------------------------
>
> Key: HBASE-6769
> URL: https://issues.apache.org/jira/browse/HBASE-6769
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0, 0.94.1
> Reporter: Jean-Daniel Cryans
> Assignee: Elliott Clark
> Priority: Critical
> Fix For: 0.96.0, 0.94.2
>
> Attachments: HBASE-6769-0.94-0.patch, HBASE-6769-0.94-1.patch,
> HBASE-6769-0.patch
>
>
> I think this is a pretty major usability regression, since HBASE-5021 this is
> what you get in the client when using a wrong family:
> {noformat}
> 2012-09-11 09:45:29,634 WARN
> org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed 1
> action: DoNotRetryIOException: 1 time, servers with issues: sfor3s44:10304,
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchCallback(HConnectionManager.java:1601)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1377)
> at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:916)
> at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:772)
> at org.apache.hadoop.hbase.client.HTable.put(HTable.java:747)
> {noformat}
> Then you have to log on the server to understand what failed.
> Since everything is now a multi call, even single puts in the shell fail like
> this.
> This is present since 0.94.0
> Assigning to Elliott because he asked.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
