You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2013/05/21 19:45:19 UTC
[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,,00000000000000 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,,00000000000000'
2013-05-21 10:41:53,781 DEBUG [TestClient-3] client.ClientScanner: Advancing internal scanner to startKey at 'TestTable,,00000000000000'
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