[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469898#comment-13469898
]
Hudson commented on HBASE-6769:
---
Integrated in HBase-0.94-security-on-Hadoop-23 #8 (See
[https://builds.apache.org/job/HBase-0.94-security-on-Hadoop-23/8/])
HBASE-6769 HRS.multi eats NoSuchColumnFamilyException (Elliott Clark)
(Revision 1384378)
Result = FAILURE
larsh :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/HConstants.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java
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.94.2, 0.96.0
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
[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13454679#comment-13454679
]
Hadoop QA commented on HBASE-6769:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12544945/HBASE-6769-0.94-1.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 6 new or modified tests.
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2856//console
This message is automatically generated.
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
[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13454683#comment-13454683
]
Lars Hofhansl commented on HBASE-6769:
--
+1 on 0.94 patch as well.
This comment is weird, as it refers to a non existing exception.
{code}
+ // Don't send a FailedSanityCheckException as older clients will
not know about
+ // that class being a subclass of DoNotRetryIOException
+ // and will retry mutations that will never succeed.
{code}
Don't post a new patch :) ... I'll change the comment on commit:
{code}
// Use generic DoNotRetryIOException so that older clients know how to deal
with it.
{code}
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
[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13454685#comment-13454685
]
Elliott Clark commented on HBASE-6769:
--
haha yeah I guess I have more context than 0.94 source would give a reader.
Sorry about that.
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
[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13454709#comment-13454709
]
Elliott Clark commented on HBASE-6769:
--
All tests passed locally for 0.94.
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
[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13454986#comment-13454986
]
Jean-Daniel Cryans commented on HBASE-6769:
---
Great work Elliott.
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
[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455011#comment-13455011
]
Hudson commented on HBASE-6769:
---
Integrated in HBase-TRUNK #3327 (See
[https://builds.apache.org/job/HBase-TRUNK/3327/])
HBASE-6769 HRS.multi eats NoSuchColumnFamilyException (Elliott Clark)
(Revision 1384377)
Result = FAILURE
larsh :
Files :
*
/hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/FailedSanityCheckException.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java
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
[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455015#comment-13455015
]
Hudson commented on HBASE-6769:
---
Integrated in HBase-0.94 #467 (See
[https://builds.apache.org/job/HBase-0.94/467/])
HBASE-6769 HRS.multi eats NoSuchColumnFamilyException (Elliott Clark)
(Revision 1384378)
Result = FAILURE
larsh :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/HConstants.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java
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
[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455035#comment-13455035
]
Hudson commented on HBASE-6769:
---
Integrated in HBase-0.94-security #52 (See
[https://builds.apache.org/job/HBase-0.94-security/52/])
HBASE-6769 HRS.multi eats NoSuchColumnFamilyException (Elliott Clark)
(Revision 1384378)
Result = SUCCESS
larsh :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/HConstants.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java
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
[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455511#comment-13455511
]
Hudson commented on HBASE-6769:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #172 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/172/])
HBASE-6769 HRS.multi eats NoSuchColumnFamilyException (Elliott Clark)
(Revision 1384377)
Result = FAILURE
larsh :
Files :
*
/hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/FailedSanityCheckException.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java
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
[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13454555#comment-13454555
]
Lars Hofhansl commented on HBASE-6769:
--
Sigh... Yeah, I'll hold 0.94.2 for this.
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
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
[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13454601#comment-13454601
]
Hadoop QA commented on HBASE-6769:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12544923/HBASE-6769-0.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 6 new or modified tests.
+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.
+1 javadoc. The javadoc tool did not generate any warning messages.
-1 javac. The patch appears to cause mvn compile goal to fail.
-1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2854//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2854//console
This message is automatically generated.
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.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
[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13454611#comment-13454611
]
Lars Hofhansl commented on HBASE-6769:
--
+1 on patch. Need a 0.94 version as well. I'm happy to make one.
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.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
[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13454622#comment-13454622
]
Elliott Clark commented on HBASE-6769:
--
I'll get a 0.94 patch tonight so you can cut an rc whenever. I just wanted
jenkins to take a crack at it first.
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.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
[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13454639#comment-13454639
]
Lars Hofhansl commented on HBASE-6769:
--
Thanks Elliot! Did you forget to add FailedSanityCheckException to the 0.94
patch? If the same as in 0.96 I'll just add it at commit.
Will the new exception cause compatibility issues in old 0.92.x and 0.94.{0|1}
clients? I don't think so... Just making sure.
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.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
[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13454642#comment-13454642
]
Hadoop QA commented on HBASE-6769:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12544939/HBASE-6769-0.94-0.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 6 new or modified tests.
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2855//console
This message is automatically generated.
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.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
[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13454646#comment-13454646
]
Elliott Clark commented on HBASE-6769:
--
Yes I totally forgot to git add the FailedSanityCheckException.
I just spun up a local 0.94 build and a 0.92.1 hbase shell. resulting in:
{code}
1.9.3-p194 :001 list
TABLE
0 row(s) in 0.7450 seconds
1.9.3-p194 :002 create 'test_table', 'd'
0 row(s) in 0.1560 seconds
1.9.3-p194 :003 put 'test_table', 'rk', 'b:1', '0'
ERROR: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException:
Failed 1 action:
org.apache.hadoop.hbase.regionserver.NoSuchColumnFamilyException: Column family
b does not exist in region
test_table,,1347513173188.d9d026b9ac9c899bd21cff52682905bd. in table {NAME =
'test_table', FAMILIES = [{NAME = 'd', BLOOMFILTER = 'NONE',
REPLICATION_SCOPE = '0', COMPRESSION = 'NONE', VERSIONS = '3', TTL =
'2147483647', MIN_VERSIONS = '0', BLOCKSIZE = '65536', IN_MEMORY = 'false',
BLOCKCACHE = 'true'}]}
at
org.apache.hadoop.hbase.regionserver.HRegionServer.multi(HRegionServer.java:3470)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.hadoop.hbase.ipc.WritableRpcEngine$Server.call(WritableRpcEngine.java:364)
at
org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1400)
: 1 time, servers with issues: android-c6740ac93630ee19:57140,
Here is some help for this command:
Put a cell 'value' at specified table/row/column and optionally
timestamp coordinates. To put a cell value into table 't1' at
row 'r1' under column 'c1' marked with the time 'ts1', do:
hbase put 't1', 'r1', 'c1', 'value', ts1
{code}
So it looks like everything works well.
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.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
[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13454652#comment-13454652
]
Elliott Clark commented on HBASE-6769:
--
Hmmm so looking at the logs. While the client does seem to function it's
re-trying multiple times if the error is the new exception. So looks like
since the client can't determine that the new exception class is a sub class of
DoNotRetryIOException, all of the reties are being issued.
I'll post a new 0.94 patch.
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.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
[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13454654#comment-13454654
]
Lars Hofhansl commented on HBASE-6769:
--
Yep... I was thinking that something like this can happen. Maybe in 0.94 we
just go without the new exception and just throw DoNotRetryException when the
timestamp check fails...? That is the current behavior anyway.
(but we do throw NoSuchColumnFamilyException in case of a wrong CF)
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.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
[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13454656#comment-13454656
]
Elliott Clark commented on HBASE-6769:
--
Keeping the exception and using it in hregion but not using it when sending
data to the client makes the try/catch logic a little cleaner to read. But does
add a class that's no used for much. I'm up for whichever you think would be
best.
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.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
[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13454658#comment-13454658
]
Lars Hofhansl commented on HBASE-6769:
--
Either way's fine. Leaning slightly towards less code for 0.94.
But if you think readability at the server is improved even if that exception
is ultimately not passed to the client... go for it :)
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.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
