[jira] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Attachment: HBASE-7649-ADDENDUM-v0.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, 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and 95 > 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Attachment: HBASE-7649-v8.1.patch nothing substantial changed so I am going to commit tomorrow if there are no 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, 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Attachment: HBASE-7649-v8.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, 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Fix Version/s: 0.95.0 > 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Component/s: MTTR > 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 > 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Attachment: HBASE-7649-v7.patch Yeah, I think it's better :) Made true by default... let's see how tests do 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, 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Attachment: HBASE-7649-v6.patch Update 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, 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Status: Patch Available (was: Open) > 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Status: Open (was: Patch Available) Need to get HBASE-7948 in to handle edge case discussed above, then will make smaller 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, 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Status: Patch Available (was: Open) > 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Attachment: HBASE-7649-v5.patch Rebase the patch, some changes. Some fixes were now integrated so I will need to rerun the integration tests to see if there are glitches. > 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Status: Open (was: Patch Available) > 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Attachment: HBASE-7649-v4.patch Preliminary patch for the latter, if no objections I will run integration tests/etc. for it tomorrow. Maybe add test case to TestHCM > 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Attachment: HBASE-7649-v3.patch /r/ feedback, long lines > 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Status: Patch Available (was: Open) > 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Status: Open (was: Patch Available) > 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Attachment: HBASE-7649-v2.patch Sorry for sloppy rebase... test issue (off by one that I fixed elsewhere) > 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Attachment: HBASE-7649-v2.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 > > > 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Issue Type: Improvement (was: Bug) > 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Component/s: Client > 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 > 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Attachment: HBASE-7649-v2.patch Added commented-out logging config. Will upload to /r/ shortly. I think this should be a good patch (incidentally :)) > 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, > 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Status: Patch Available (was: Open) > 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Attachment: HBASE-7649-v1.patch Take 2. I will run some more integration tests on it tomorrow, for now it looks promising :) > 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Status: Open (was: Patch Available) > 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Status: Patch Available (was: Open) > 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] [Updated] (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:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Attachment: HBASE-7649-v0.patch Attaching patch that tracks retries by 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 > > > 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