[jira] [Commented] (HBASE-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664965#comment-13664965 ] Hudson commented on HBASE-7649: --- Integrated in hbase-0.95 #210 (See [https://builds.apache.org/job/hbase-0.95/210/]) HBASE-7649 ADDENDUM client retry timeout doesn't need to do x2 fallback when going to different server (Revision 1485514) Result = SUCCESS sershe : Files : * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client, MTTR >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.95.1 > > Attachments: HBASE-7649-ADDENDUM-v0.patch, HBASE-7649-v0.patch, > HBASE-7649-v1.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v2.patch, HBASE-7649-v3.patch, HBASE-7649-v4.patch, > HBASE-7649-v5.patch, HBASE-7649-v6.patch, HBASE-7649-v7.patch, > HBASE-7649-v8.1.patch, HBASE-7649-v8.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664932#comment-13664932 ] Hudson commented on HBASE-7649: --- Integrated in HBase-TRUNK #4138 (See [https://builds.apache.org/job/HBase-TRUNK/4138/]) HBASE-7649 ADDENDUM client retry timeout doesn't need to do x2 fallback when going to different server (Revision 1485513) Result = SUCCESS sershe : Files : * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client, MTTR >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.95.1 > > Attachments: HBASE-7649-ADDENDUM-v0.patch, HBASE-7649-v0.patch, > HBASE-7649-v1.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v2.patch, HBASE-7649-v3.patch, HBASE-7649-v4.patch, > HBASE-7649-v5.patch, HBASE-7649-v6.patch, HBASE-7649-v7.patch, > HBASE-7649-v8.1.patch, HBASE-7649-v8.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664895#comment-13664895 ] Hudson commented on HBASE-7649: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #539 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/539/]) HBASE-7649 ADDENDUM client retry timeout doesn't need to do x2 fallback when going to different server (Revision 1485513) Result = FAILURE sershe : Files : * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client, MTTR >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.95.1 > > Attachments: HBASE-7649-ADDENDUM-v0.patch, HBASE-7649-v0.patch, > HBASE-7649-v1.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v2.patch, HBASE-7649-v3.patch, HBASE-7649-v4.patch, > HBASE-7649-v5.patch, HBASE-7649-v6.patch, HBASE-7649-v7.patch, > HBASE-7649-v8.1.patch, HBASE-7649-v8.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664853#comment-13664853 ] Hudson commented on HBASE-7649: --- Integrated in hbase-0.95-on-hadoop2 #108 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/108/]) HBASE-7649 ADDENDUM client retry timeout doesn't need to do x2 fallback when going to different server (Revision 1485514) Result = FAILURE sershe : Files : * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client, MTTR >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.95.1 > > Attachments: HBASE-7649-ADDENDUM-v0.patch, HBASE-7649-v0.patch, > HBASE-7649-v1.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v2.patch, HBASE-7649-v3.patch, HBASE-7649-v4.patch, > HBASE-7649-v5.patch, HBASE-7649-v6.patch, HBASE-7649-v7.patch, > HBASE-7649-v8.1.patch, HBASE-7649-v8.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664687#comment-13664687 ] stack commented on HBASE-7649: -- [~sershe] non-transferable currency (smile) > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client, MTTR >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.95.1 > > Attachments: HBASE-7649-ADDENDUM-v0.patch, HBASE-7649-v0.patch, > HBASE-7649-v1.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v2.patch, HBASE-7649-v3.patch, HBASE-7649-v4.patch, > HBASE-7649-v5.patch, HBASE-7649-v6.patch, HBASE-7649-v7.patch, > HBASE-7649-v8.1.patch, HBASE-7649-v8.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664640#comment-13664640 ] Sergey Shelukhin commented on HBASE-7649: - are these +1s transferable to other JIRAs? ;) > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client, MTTR >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.95.1 > > Attachments: HBASE-7649-ADDENDUM-v0.patch, HBASE-7649-v0.patch, > HBASE-7649-v1.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v2.patch, HBASE-7649-v3.patch, HBASE-7649-v4.patch, > HBASE-7649-v5.patch, HBASE-7649-v6.patch, HBASE-7649-v7.patch, > HBASE-7649-v8.1.patch, HBASE-7649-v8.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664470#comment-13664470 ] stack commented on HBASE-7649: -- +1+1+1+1+1+1+1+1+1, one for each byte. > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client, MTTR >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.95.1 > > Attachments: HBASE-7649-ADDENDUM-v0.patch, HBASE-7649-v0.patch, > HBASE-7649-v1.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v2.patch, HBASE-7649-v3.patch, HBASE-7649-v4.patch, > HBASE-7649-v5.patch, HBASE-7649-v6.patch, HBASE-7649-v7.patch, > HBASE-7649-v8.1.patch, HBASE-7649-v8.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664407#comment-13664407 ] Nicolas Liochon commented on HBASE-7649: +1 :-) > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client, MTTR >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.95.1 > > Attachments: HBASE-7649-ADDENDUM-v0.patch, HBASE-7649-v0.patch, > HBASE-7649-v1.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v2.patch, HBASE-7649-v3.patch, HBASE-7649-v4.patch, > HBASE-7649-v5.patch, HBASE-7649-v6.patch, HBASE-7649-v7.patch, > HBASE-7649-v8.1.patch, HBASE-7649-v8.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664392#comment-13664392 ] Sergey Shelukhin commented on HBASE-7649: - ping for addendum? it's a 9-byte patch. Log message is rare and simple so isTraceEnabled check is not needed > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client, MTTR >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.95.1 > > Attachments: HBASE-7649-ADDENDUM-v0.patch, HBASE-7649-v0.patch, > HBASE-7649-v1.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v2.patch, HBASE-7649-v3.patch, HBASE-7649-v4.patch, > HBASE-7649-v5.patch, HBASE-7649-v6.patch, HBASE-7649-v7.patch, > HBASE-7649-v8.1.patch, HBASE-7649-v8.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13663380#comment-13663380 ] Sergey Shelukhin commented on HBASE-7649: - This downgrades the message to trace. This value can change, and depends on # of retries. > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client, MTTR >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.95.1 > > Attachments: HBASE-7649-ADDENDUM-v0.patch, HBASE-7649-v0.patch, > HBASE-7649-v1.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v2.patch, HBASE-7649-v3.patch, HBASE-7649-v4.patch, > HBASE-7649-v5.patch, HBASE-7649-v6.patch, HBASE-7649-v7.patch, > HBASE-7649-v8.1.patch, HBASE-7649-v8.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13663185#comment-13663185 ] Sergey Shelukhin commented on HBASE-7649: - Woops, that was my debugging message, it was not supposed to go in on INFO level. Let me submit addendum > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client, MTTR >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.95.1 > > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch, > HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch, > HBASE-7649-v6.patch, HBASE-7649-v7.patch, HBASE-7649-v8.1.patch, > HBASE-7649-v8.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[
https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13663170#comment-13663170
]
Jean-Daniel Cryans commented on HBASE-7649:
---
I'm I the only one annoyed by all the new log lines about the server tracker
timeout? Here's an example:
{noformat}
2013-05-21 10:41:53,774 INFO [TestClient-3]
client.HConnectionManager$HConnectionImplementation: Server tracker timeout is
71226ms
2013-05-21 10:41:53,781 DEBUG [TestClient-3] client.MetaScanner: Scanning
.META. starting at row=TestTable,,00 for max=10 with caching=10
2013-05-21 10:41:53,781 DEBUG [TestClient-3] client.ClientScanner: Creating
scanner over .META. starting at key 'TestTable,,00'
2013-05-21 10:41:53,781 DEBUG [TestClient-3] client.ClientScanner: Advancing
internal scanner to startKey at 'TestTable,,00'
2013-05-21 10:41:53,783 INFO [TestClient-0]
client.HConnectionManager$HConnectionImplementation: Server tracker timeout is
71226ms
2013-05-21 10:41:53,789 INFO [TestClient-1]
client.HConnectionManager$HConnectionImplementation: Server tracker timeout is
71226ms
2013-05-21 10:41:53,795 DEBUG [TestClient-3] client.ClientScanner: Finished
scanning region {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '', ENCODED =>
1028785192,}
2013-05-21 10:41:53,795 DEBUG [TestClient-3]
client.HConnectionManager$HConnectionImplementation: Cached location for
TestTable,,1369157955242.fea0073c2c0fcf1de74eb20960ca9f0d. is 172.22.3.126:50468
2013-05-21 10:41:53,797 INFO [TestClient-2]
client.HConnectionManager$HConnectionImplementation: Server tracker timeout is
71226ms
2013-05-21 10:41:53,799 INFO [TestClient-4]
client.HConnectionManager$HConnectionImplementation: Server tracker timeout is
71226ms
{noformat}
Is that value even supposed to change?
> client retry timeout doesn't need to do x2 fallback when going to different
> server
> --
>
> Key: HBASE-7649
> URL: https://issues.apache.org/jira/browse/HBASE-7649
> Project: HBase
> Issue Type: Improvement
> Components: Client, MTTR
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Fix For: 0.95.1
>
> Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch,
> HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch,
> HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch,
> HBASE-7649-v6.patch, HBASE-7649-v7.patch, HBASE-7649-v8.1.patch,
> HBASE-7649-v8.patch
>
>
> See HBASE-7520. When we go to server A, get a bunch of failures, then finally
> learn the region is on B it doesn't make sense to wait for 30 seconds before
> going to B.
--
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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623580#comment-13623580 ] Hudson commented on HBASE-7649: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #478 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/478/]) HBASE-7649 client retry timeout doesn't need to do x2 fallback when going to different server (Revision 1464798) Result = FAILURE sershe : Files : * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java * /hbase/trunk/hbase-it/src/test/java/org/apache/hadoop/hbase/IngestIntegrationTestBase.java * /hbase/trunk/hbase-it/src/test/java/org/apache/hadoop/hbase/IntegrationTestRebalanceAndKillServersTargeted.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestHCM.java > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client, MTTR >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.95.1 > > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch, > HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch, > HBASE-7649-v6.patch, HBASE-7649-v7.patch, HBASE-7649-v8.1.patch, > HBASE-7649-v8.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623563#comment-13623563 ] Hudson commented on HBASE-7649: --- Integrated in hbase-0.95-on-hadoop2 #56 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/56/]) HBASE-7649 client retry timeout doesn't need to do x2 fallback when going to different server (Revision 1464799) Result = FAILURE sershe : Files : * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java * /hbase/branches/0.95/hbase-it/src/test/java/org/apache/hadoop/hbase/IngestIntegrationTestBase.java * /hbase/branches/0.95/hbase-it/src/test/java/org/apache/hadoop/hbase/IntegrationTestRebalanceAndKillServersTargeted.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestHCM.java > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client, MTTR >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.95.1 > > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch, > HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch, > HBASE-7649-v6.patch, HBASE-7649-v7.patch, HBASE-7649-v8.1.patch, > HBASE-7649-v8.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623318#comment-13623318 ] Hudson commented on HBASE-7649: --- Integrated in hbase-0.95 #126 (See [https://builds.apache.org/job/hbase-0.95/126/]) HBASE-7649 client retry timeout doesn't need to do x2 fallback when going to different server (Revision 1464799) Result = FAILURE sershe : Files : * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java * /hbase/branches/0.95/hbase-it/src/test/java/org/apache/hadoop/hbase/IngestIntegrationTestBase.java * /hbase/branches/0.95/hbase-it/src/test/java/org/apache/hadoop/hbase/IntegrationTestRebalanceAndKillServersTargeted.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestHCM.java > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client, MTTR >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.95.1 > > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch, > HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch, > HBASE-7649-v6.patch, HBASE-7649-v7.patch, HBASE-7649-v8.1.patch, > HBASE-7649-v8.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623292#comment-13623292 ] Hudson commented on HBASE-7649: --- Integrated in HBase-TRUNK #4016 (See [https://builds.apache.org/job/HBase-TRUNK/4016/]) HBASE-7649 client retry timeout doesn't need to do x2 fallback when going to different server (Revision 1464798) Result = SUCCESS sershe : Files : * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java * /hbase/trunk/hbase-it/src/test/java/org/apache/hadoop/hbase/IngestIntegrationTestBase.java * /hbase/trunk/hbase-it/src/test/java/org/apache/hadoop/hbase/IntegrationTestRebalanceAndKillServersTargeted.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestHCM.java > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client, MTTR >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.95.1 > > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch, > HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch, > HBASE-7649-v6.patch, HBASE-7649-v7.patch, HBASE-7649-v8.1.patch, > HBASE-7649-v8.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[
https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621645#comment-13621645
]
Hadoop QA commented on HBASE-7649:
--
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12576891/HBASE-7649-v8.1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 new
or modified tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5121//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5121//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5121//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5121//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5121//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5121//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5121//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5121//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5121//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5121//console
This message is automatically generated.
> client retry timeout doesn't need to do x2 fallback when going to different
> server
> --
>
> Key: HBASE-7649
> URL: https://issues.apache.org/jira/browse/HBASE-7649
> Project: HBase
> Issue Type: Improvement
> Components: Client, MTTR
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Fix For: 0.95.1
>
> Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch,
> HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch,
> HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch,
> HBASE-7649-v6.patch, HBASE-7649-v7.patch, HBASE-7649-v8.1.patch,
> HBASE-7649-v8.patch
>
>
> See HBASE-7520. When we go to server A, get a bunch of failures, then finally
> learn the region is on B it doesn't make sense to wait for 30 seconds before
> going to B.
--
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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621558#comment-13621558 ] Sergey Shelukhin commented on HBASE-7649: - TestHCM fails due to using reflection on the field I rename 0_o I will fix tomorrow due to some local git clone shortage. > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client, MTTR >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.95.1 > > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch, > HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch, > HBASE-7649-v6.patch, HBASE-7649-v7.patch, HBASE-7649-v8.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[
https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621394#comment-13621394
]
Hadoop QA commented on HBASE-7649:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12576839/HBASE-7649-v8.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 new
or modified tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.client.TestHCM
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5115//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5115//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5115//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5115//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5115//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5115//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5115//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5115//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5115//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5115//console
This message is automatically generated.
> client retry timeout doesn't need to do x2 fallback when going to different
> server
> --
>
> Key: HBASE-7649
> URL: https://issues.apache.org/jira/browse/HBASE-7649
> Project: HBase
> Issue Type: Improvement
> Components: Client, MTTR
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Fix For: 0.95.0
>
> Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch,
> HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch,
> HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch,
> HBASE-7649-v6.patch, HBASE-7649-v7.patch, HBASE-7649-v8.patch
>
>
> See HBASE-7520. When we go to server A, get a bunch of failures, then finally
> learn the region is on B it doesn't make sense to wait for 30 seconds before
> going to B.
--
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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621292#comment-13621292 ] Nicolas Liochon commented on HBASE-7649: I read the code, looking for stuff like multithreading issue. Haven't found any. Code is clean. I'm ok with what the patch is doing, there is a unit test. So +1 for commit :-). > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client, MTTR >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.95.0 > > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch, > HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch, > HBASE-7649-v6.patch, HBASE-7649-v7.patch, HBASE-7649-v8.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621272#comment-13621272 ] Sergey Shelukhin commented on HBASE-7649: - Some feedback from r, also updated r > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client, MTTR >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.95.0 > > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch, > HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch, > HBASE-7649-v6.patch, HBASE-7649-v7.patch, HBASE-7649-v8.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621139#comment-13621139 ] Sergey Shelukhin commented on HBASE-7649: - Note - r is not updated, I will rebase patch and update it soon > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client, MTTR >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.95.0 > > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch, > HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch, > HBASE-7649-v6.patch, HBASE-7649-v7.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617835#comment-13617835 ] Sergey Shelukhin commented on HBASE-7649: - ping? > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch, > HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch, > HBASE-7649-v6.patch, HBASE-7649-v7.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[
https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613305#comment-13613305
]
Hadoop QA commented on HBASE-7649:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12575408/HBASE-7649-v7.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 new
or modified tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:red}-1 site{color}. The patch appears to cause mvn site goal to
fail.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.regionserver.TestAtomicOperation
org.apache.hadoop.hbase.master.TestTableLockManager
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5003//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5003//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5003//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5003//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5003//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5003//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5003//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5003//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5003//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5003//console
This message is automatically generated.
> client retry timeout doesn't need to do x2 fallback when going to different
> server
> --
>
> Key: HBASE-7649
> URL: https://issues.apache.org/jira/browse/HBASE-7649
> Project: HBase
> Issue Type: Improvement
> Components: Client
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch,
> HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch,
> HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch,
> HBASE-7649-v6.patch, HBASE-7649-v7.patch
>
>
> See HBASE-7520. When we go to server A, get a bunch of failures, then finally
> learn the region is on B it doesn't make sense to wait for 30 seconds before
> going to B.
--
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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1361#comment-1361 ] Sergey Shelukhin commented on HBASE-7649: - Both of these tests pass on local... > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch, > HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch, > HBASE-7649-v6.patch, HBASE-7649-v7.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610375#comment-13610375 ] Nicolas Liochon commented on HBASE-7649: bq. Interesting question is whether this should be on by default. imho, when we think that a setting is globally better than another, we should make it the default. If you implemented this it's because you think it's better, so it's should be the default... > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch, > HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch, > HBASE-7649-v6.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[
https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13609653#comment-13609653
]
Hadoop QA commented on HBASE-7649:
--
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12574889/HBASE-7649-v6.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 new
or modified tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/4951//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4951//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4951//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4951//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4951//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4951//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4951//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4951//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4951//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4951//console
This message is automatically generated.
> client retry timeout doesn't need to do x2 fallback when going to different
> server
> --
>
> Key: HBASE-7649
> URL: https://issues.apache.org/jira/browse/HBASE-7649
> Project: HBase
> Issue Type: Improvement
> Components: Client
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch,
> HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch,
> HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch,
> HBASE-7649-v6.patch
>
>
> See HBASE-7520. When we go to server A, get a bunch of failures, then finally
> learn the region is on B it doesn't make sense to wait for 30 seconds before
> going to B.
--
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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13609528#comment-13609528 ] Sergey Shelukhin commented on HBASE-7649: - I will run integration tests, probably tomorrow. Interesting question is whether this should be on by default. > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch, > HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch, > HBASE-7649-v6.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[
https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587569#comment-13587569
]
Sergey Shelukhin commented on HBASE-7649:
-
Ok, if this is not perfect, I don't know what is :) I will see if patch can be
separated into 2 features, then attach here and/or in the spinoff JIRA.
{code}
2013-02-25 17:22:48,825 TRACE [HBaseWriterThread_2]
client.HConnectionManager$HConnectionImplementation$Process(2189): Retrying due
to errors: Error from [10.11.3.82:4] for
[21fbc36d7ebdf028791fd50c01cffeda-34284]java.util.concurrent.ExecutionException:
org.apache.hadoop.hbase.RegionMovedException: Region moved to:
hostname=10.11.3.82 port=50002 startCode=1361841634800. As of
locationSeqNum=80819.
2013-02-25 17:22:48,825 TRACE [HBaseWriterThread_2]
client.HConnectionManager$HConnectionImplementation$Process(2054): Will retry
requests to [10.11.3.82:50002] after delay of [0] for rows
[21fbc36d7ebdf028791fd50c01cffeda-34284;]
2013-02-25 17:22:48,828 TRACE [HBaseWriterThread_2]
client.HConnectionManager$HConnectionImplementation$Process(2189): Retrying due
to errors: Error from [10.11.3.82:50002] for
[21fbc36d7ebdf028791fd50c01cffeda-34284]java.util.concurrent.ExecutionException:
org.apache.hadoop.hbase.RegionOpeningException:
org.apache.hadoop.hbase.RegionOpeningException: Region is being opened:
520d395629415d8de9dd15d701344420
2013-02-25 17:22:48,829 TRACE [HBaseWriterThread_2]
client.HConnectionManager$HConnectionImplementation$Process(2054): Will retry
requests to [10.11.3.82:50002] after delay of [1003] for rows
[21fbc36d7ebdf028791fd50c01cffeda-34284;]
{code}
> client retry timeout doesn't need to do x2 fallback when going to different
> server
> --
>
> Key: HBASE-7649
> URL: https://issues.apache.org/jira/browse/HBASE-7649
> Project: HBase
> Issue Type: Improvement
> Components: Client
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch,
> HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch,
> HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch
>
>
> See HBASE-7520. When we go to server A, get a bunch of failures, then finally
> learn the region is on B it doesn't make sense to wait for 30 seconds before
> going to B.
--
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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[
https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584856#comment-13584856
]
Ted Yu commented on HBASE-7649:
---
{code}
+public class HRegionCacheLocation extends HRegionLocation {
{code}
Add javadoc for the class along with annotation for audience.
For checkIfOpenGracePeriodExpired():
{code}
+if (openingTime == null) {
+ openingTime = now;
+ return false;
{code}
When would user call checkIfOpenGracePeriodExpired() before setting openingTime
?
One question is about the type of openingTime field. Method parameters are all
long. Does the field have to be Long ?
For NotServingRegionException.java, is the following import needed ?
{code}
+import org.apache.hadoop.ipc.RemoteException;
{code}
{code}
+ public static final String RETRIES_BY_SERVER =
"hbase.client.retries.by.server";
{code}
To signify that the config key carries a boolean value, can it be named
"hbase.client.retries.byserver.enable" ?
{code}
+ public static final String SERVER_OPEN_REGION_GRACE_PERIOD
+= "hbase.client.retries.openregion.graceperiod";
+ public static final Long DEFAULT_SERVER_OPEN_REGION_GRACE_PERIOD = 1L;
{code}
The above constants can be private.
For HRegionServer.java :
{code}
+if (isOpening != null && isOpening.booleanValue()) {
+ throw new RegionOpeningException("Region is being opened: " +
encodedRegionName);
+} else {
{code}
nit: the 'else' is not needed.
> client retry timeout doesn't need to do x2 fallback when going to different
> server
> --
>
> Key: HBASE-7649
> URL: https://issues.apache.org/jira/browse/HBASE-7649
> Project: HBase
> Issue Type: Improvement
> Components: Client
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch,
> HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch,
> HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch
>
>
> See HBASE-7520. When we go to server A, get a bunch of failures, then finally
> learn the region is on B it doesn't make sense to wait for 30 seconds before
> going to B.
--
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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[
https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584789#comment-13584789
]
Hadoop QA commented on HBASE-7649:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12570541/HBASE-7649-v5.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 27 new
or modified tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces lines longer than
100
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/4500//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4500//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4500//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4500//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4500//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4500//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4500//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4500//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4500//console
This message is automatically generated.
> client retry timeout doesn't need to do x2 fallback when going to different
> server
> --
>
> Key: HBASE-7649
> URL: https://issues.apache.org/jira/browse/HBASE-7649
> Project: HBase
> Issue Type: Improvement
> Components: Client
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch,
> HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch,
> HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch
>
>
> See HBASE-7520. When we go to server A, get a bunch of failures, then finally
> learn the region is on B it doesn't make sense to wait for 30 seconds before
> going to B.
--
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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572628#comment-13572628 ] Sergey Shelukhin commented on HBASE-7649: - org.apache.hadoop.hbase.TestZooKeeper passes on local. > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch, > HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v3.patch, HBASE-7649-v4.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[
https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572104#comment-13572104
]
Hadoop QA commented on HBASE-7649:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12568155/HBASE-7649-v4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 12 new
or modified tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.TestZooKeeper
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/4349//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4349//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4349//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4349//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4349//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4349//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4349//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4349//console
This message is automatically generated.
> client retry timeout doesn't need to do x2 fallback when going to different
> server
> --
>
> Key: HBASE-7649
> URL: https://issues.apache.org/jira/browse/HBASE-7649
> Project: HBase
> Issue Type: Improvement
> Components: Client
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch,
> HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch,
> HBASE-7649-v3.patch, HBASE-7649-v4.patch
>
>
> See HBASE-7520. When we go to server A, get a bunch of failures, then finally
> learn the region is on B it doesn't make sense to wait for 30 seconds before
> going to B.
--
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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572073#comment-13572073 ] Sergey Shelukhin commented on HBASE-7649: - latter == (1), so former. > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch, > HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v3.patch, HBASE-7649-v4.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572003#comment-13572003 ] Sergey Shelukhin commented on HBASE-7649: - Ok, I got back to this, there are two approaches possible. 1) The involved one, we can add RegionOpeningException to HRegionServer, same place as RegionMovedException. If client gets that he won't remove entry from cache for some time (say 10 seconds), so it wouldn't go to meta. 2) The hacky, simpler one, purely on client side, after RegionMovedException we can keep a small delay (if we found out from meta and not RME, we should be good because meta means it's already opened). I'd prefer to do (1)... any objections? > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch, > HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v3.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565660#comment-13565660 ] Sergey Shelukhin commented on HBASE-7649: - Hmm, this is a valid concern with new change. Let me think about it. > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch, > HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v3.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565204#comment-13565204 ] nkeywal commented on HBASE-7649: bq. Well, the region can often be opened very quickly, so I think it might make sense to try to go to destination immediately. I am aware of some schemes in certain products where the server tries to calculate backoff time based on request queue under heavy load, and tells the client to back off for that time, but that seems like it's too much of a high hanging fruit right now The bad scenario would be: dead rs -> new rs to early -> meta -> new rs (on time) This makes us as slow as today and adds a call to meta. Even if the open/close is very fast, the common use case is likely to be a continuous flow of writes by the client interrupted by a balance, so the client will get the info at the very beginning of the move. As a consequence, the bad scenario above may be more common that we would like. But I don't have a definitive opinion on the best choice between always waiting and never waiting, so I will follow the general opinion here. > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch, > HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v3.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13564959#comment-13564959 ] Ted Yu commented on HBASE-7649: --- +1 on latest patch. > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch, > HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, > HBASE-7649-v3.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[
https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13564951#comment-13564951
]
Hadoop QA commented on HBASE-7649:
--
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12566860/HBASE-7649-v3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 new
or modified tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/4222//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4222//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4222//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4222//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4222//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4222//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4222//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4222//console
This message is automatically generated.
> client retry timeout doesn't need to do x2 fallback when going to different
> server
> --
>
> Key: HBASE-7649
> URL: https://issues.apache.org/jira/browse/HBASE-7649
> Project: HBase
> Issue Type: Improvement
> Components: Client
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch,
> HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch,
> HBASE-7649-v3.patch
>
>
> See HBASE-7520. When we go to server A, get a bunch of failures, then finally
> learn the region is on B it doesn't make sense to wait for 30 seconds before
> going to B.
--
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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[
https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13563180#comment-13563180
]
Hadoop QA commented on HBASE-7649:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12566571/HBASE-7649-v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 new
or modified tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces lines longer than
100
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/4188//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4188//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4188//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4188//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4188//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4188//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4188//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4188//console
This message is automatically generated.
> client retry timeout doesn't need to do x2 fallback when going to different
> server
> --
>
> Key: HBASE-7649
> URL: https://issues.apache.org/jira/browse/HBASE-7649
> Project: HBase
> Issue Type: Improvement
> Components: Client
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch,
> HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch
>
>
> See HBASE-7520. When we go to server A, get a bunch of failures, then finally
> learn the region is on B it doesn't make sense to wait for 30 seconds before
> going to B.
--
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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[
https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13563085#comment-13563085
]
Hadoop QA commented on HBASE-7649:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12566563/HBASE-7649-v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 12 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4185//console
This message is automatically generated.
> client retry timeout doesn't need to do x2 fallback when going to different
> server
> --
>
> Key: HBASE-7649
> URL: https://issues.apache.org/jira/browse/HBASE-7649
> Project: HBase
> Issue Type: Improvement
> Components: Client
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch,
> HBASE-7649-v2.patch
>
>
> See HBASE-7520. When we go to server A, get a bunch of failures, then finally
> learn the region is on B it doesn't make sense to wait for 30 seconds before
> going to B.
--
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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13563076#comment-13563076 ] Sergey Shelukhin commented on HBASE-7649: - https://reviews.apache.org/r/9113/ > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Improvement > Components: Client >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch, > HBASE-7649-v2.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13563069#comment-13563069 ] Sergey Shelukhin commented on HBASE-7649: - Well, the region can often be opened very quickly, so I think it might make sense to try to go to destination immediately. I am aware of some schemes in certain products where the server tries to calculate backoff time based on request queue under heavy load, and tells the client to back off for that time, but that seems like it's too much of a high hanging fruit right now :) > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562484#comment-13562484 ] nkeywal commented on HBASE-7649: bq. Probably it works better with time based failure, not retry based. Agreed, time based failure are quite interesting (I was the JIRA you created). Linked to this, one option would be to send back to the client the time when the region was moved. Then the client can do stuff like 'if the region was moved more than 10 seconds ago, I can go to the new server" > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[
https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562340#comment-13562340
]
Hadoop QA commented on HBASE-7649:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12566446/HBASE-7649-v1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 new
or modified tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces lines longer than
100
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.regionserver.wal.TestHLog
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/4175//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4175//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4175//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4175//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4175//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4175//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4175//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4175//console
This message is automatically generated.
> client retry timeout doesn't need to do x2 fallback when going to different
> server
> --
>
> Key: HBASE-7649
> URL: https://issues.apache.org/jira/browse/HBASE-7649
> Project: HBase
> Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch
>
>
> See HBASE-7520. When we go to server A, get a bunch of failures, then finally
> learn the region is on B it doesn't make sense to wait for 30 seconds before
> going to B.
--
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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561882#comment-13561882 ] Sergey Shelukhin commented on HBASE-7649: - doesn't work very well with many failures from many servers for the same region, can fail super fast (4-6sec). I will tweak it and make it configurable on/off. Probably it works better with time based failure, not retry based. > client retry timeout doesn't need to do x2 fallback when going to different > server > -- > > Key: HBASE-7649 > URL: https://issues.apache.org/jira/browse/HBASE-7649 > Project: HBase > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: HBASE-7649-v0.patch > > > See HBASE-7520. When we go to server A, get a bunch of failures, then finally > learn the region is on B it doesn't make sense to wait for 30 seconds before > going to B. -- 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[
https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561275#comment-13561275
]
Ted Yu commented on HBASE-7649:
---
{code}
+ private final Map errorsByServer =
+ new HashMap();
{code}
Can we have a better name for the map - errorsByRegionLocation ?
HRegionLocation has regionInfo beyond server information. Consider extracting
server information and make key type ServerName for the above map.
> client retry timeout doesn't need to do x2 fallback when going to different
> server
> --
>
> Key: HBASE-7649
> URL: https://issues.apache.org/jira/browse/HBASE-7649
> Project: HBase
> Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HBASE-7649-v0.patch
>
>
> See HBASE-7520. When we go to server A, get a bunch of failures, then finally
> learn the region is on B it doesn't make sense to wait for 30 seconds before
> going to B.
--
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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[
https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561273#comment-13561273
]
Hadoop QA commented on HBASE-7649:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12566215/HBASE-7649-v0.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 3 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.regionserver.wal.TestHLogSplitCompressed
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at
org.apache.hadoop.hbase.client.TestAdmin.testForceSplitMultiFamily(TestAdmin.java:875)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/4153//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4153//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4153//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4153//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4153//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4153//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4153//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4153//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4153//console
This message is automatically generated.
> client retry timeout doesn't need to do x2 fallback when going to different
> server
> --
>
> Key: HBASE-7649
> URL: https://issues.apache.org/jira/browse/HBASE-7649
> Project: HBase
> Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HBASE-7649-v0.patch
>
>
> See HBASE-7520. When we go to server A, get a bunch of failures, then finally
> learn the region is on B it doesn't make sense to wait for 30 seconds before
> going to B.
--
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
