[jira] [Updated] (HBASE-5845) Single Put should use RetriesExhaustedWithDetailsException in case any exception
[ https://issues.apache.org/jira/browse/HBASE-5845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5845: --- Description: Due to change in HBASE-5824. Put has two exception paths now. It's better to stay the same for easy exception handling. (was: Due to change in HBASE-5824. Put has to exception paths now. It's better to stay the same for easy exception handling.) > Single Put should use RetriesExhaustedWithDetailsException in case any > exception > > > Key: HBASE-5845 > URL: https://issues.apache.org/jira/browse/HBASE-5845 > Project: HBase > Issue Type: Bug >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > > Due to change in HBASE-5824. Put has two exception paths now. It's better > to stay the same for easy exception handling. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5824) HRegion.incrementColumnValue is not used in trunk
[ https://issues.apache.org/jira/browse/HBASE-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5824: --- Status: Patch Available (was: Reopened) Fixed the unit tests. Sorry for that. > HRegion.incrementColumnValue is not used in trunk > - > > Key: HBASE-5824 > URL: https://issues.apache.org/jira/browse/HBASE-5824 > Project: HBase > Issue Type: Bug >Reporter: Elliott Clark >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5824.patch, hbase-5824_v2.patch, > hbase_5824.addendum > > > on 0.94 a call to client.HTable#incrementColumnValue will cause > HRegion#incrementColumnValue. On trunk all calls to > HTable.incrementColumnValue got to HRegion#increment. > My guess is that HTable#incrementColumnValue and HTable#increment serialize > to the same thing over the wire so that the remote HRegionServer no longer > knows which htable method was called. > To repro I checked out trunk and put a break point in > HRegion#incrementColumnValue and then ran TestFromClientSide. The breakpoint > wasn't hit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5824) HRegion.incrementColumnValue is not used in trunk
[ https://issues.apache.org/jira/browse/HBASE-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5824: --- Attachment: hbase_5824.addendum > HRegion.incrementColumnValue is not used in trunk > - > > Key: HBASE-5824 > URL: https://issues.apache.org/jira/browse/HBASE-5824 > Project: HBase > Issue Type: Bug >Reporter: Elliott Clark >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5824.patch, hbase-5824_v2.patch, > hbase_5824.addendum > > > on 0.94 a call to client.HTable#incrementColumnValue will cause > HRegion#incrementColumnValue. On trunk all calls to > HTable.incrementColumnValue got to HRegion#increment. > My guess is that HTable#incrementColumnValue and HTable#increment serialize > to the same thing over the wire so that the remote HRegionServer no longer > knows which htable method was called. > To repro I checked out trunk and put a break point in > HRegion#incrementColumnValue and then ran TestFromClientSide. The breakpoint > wasn't hit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5621) Convert admin protocol of HRegionInterface to PB
[ https://issues.apache.org/jira/browse/HBASE-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5621: --- Attachment: hbase-5621_v3.patch > Convert admin protocol of HRegionInterface to PB > > > Key: HBASE-5621 > URL: https://issues.apache.org/jira/browse/HBASE-5621 > Project: HBase > Issue Type: Sub-task > Components: ipc, master, migration, regionserver >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5621_v3.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5621) Convert admin protocol of HRegionInterface to PB
[ https://issues.apache.org/jira/browse/HBASE-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5621: --- Hadoop Flags: Reviewed Status: Patch Available (was: Open) @Stack, thanks a lot for reviewing it. > Convert admin protocol of HRegionInterface to PB > > > Key: HBASE-5621 > URL: https://issues.apache.org/jira/browse/HBASE-5621 > Project: HBase > Issue Type: Sub-task > Components: ipc, master, migration, regionserver >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5621_v3.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5824) HRegion.incrementColumnValue is not used in trunk
[ https://issues.apache.org/jira/browse/HBASE-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5824: --- Status: Patch Available (was: Open) I added a deprecation annotation to HRegion#incrementColumnValue > HRegion.incrementColumnValue is not used in trunk > - > > Key: HBASE-5824 > URL: https://issues.apache.org/jira/browse/HBASE-5824 > Project: HBase > Issue Type: Bug >Reporter: Elliott Clark >Assignee: Jimmy Xiang > Attachments: hbase-5824.patch, hbase-5824_v2.patch > > > on 0.94 a call to client.HTable#incrementColumnValue will cause > HRegion#incrementColumnValue. On trunk all calls to > HTable.incrementColumnValue got to HRegion#increment. > My guess is that HTable#incrementColumnValue and HTable#increment serialize > to the same thing over the wire so that the remote HRegionServer no longer > knows which htable method was called. > To repro I checked out trunk and put a break point in > HRegion#incrementColumnValue and then ran TestFromClientSide. The breakpoint > wasn't hit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5824) HRegion.incrementColumnValue is not used in trunk
[ https://issues.apache.org/jira/browse/HBASE-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5824: --- Attachment: hbase-5824_v2.patch > HRegion.incrementColumnValue is not used in trunk > - > > Key: HBASE-5824 > URL: https://issues.apache.org/jira/browse/HBASE-5824 > Project: HBase > Issue Type: Bug >Reporter: Elliott Clark >Assignee: Jimmy Xiang > Attachments: hbase-5824.patch, hbase-5824_v2.patch > > > on 0.94 a call to client.HTable#incrementColumnValue will cause > HRegion#incrementColumnValue. On trunk all calls to > HTable.incrementColumnValue got to HRegion#increment. > My guess is that HTable#incrementColumnValue and HTable#increment serialize > to the same thing over the wire so that the remote HRegionServer no longer > knows which htable method was called. > To repro I checked out trunk and put a break point in > HRegion#incrementColumnValue and then ran TestFromClientSide. The breakpoint > wasn't hit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5824) HRegion.incrementColumnValue is not used in trunk
[ https://issues.apache.org/jira/browse/HBASE-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5824: --- Status: Open (was: Patch Available) > HRegion.incrementColumnValue is not used in trunk > - > > Key: HBASE-5824 > URL: https://issues.apache.org/jira/browse/HBASE-5824 > Project: HBase > Issue Type: Bug >Reporter: Elliott Clark >Assignee: Jimmy Xiang > Attachments: hbase-5824.patch, hbase-5824_v2.patch > > > on 0.94 a call to client.HTable#incrementColumnValue will cause > HRegion#incrementColumnValue. On trunk all calls to > HTable.incrementColumnValue got to HRegion#increment. > My guess is that HTable#incrementColumnValue and HTable#increment serialize > to the same thing over the wire so that the remote HRegionServer no longer > knows which htable method was called. > To repro I checked out trunk and put a break point in > HRegion#incrementColumnValue and then ran TestFromClientSide. The breakpoint > wasn't hit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5824) HRegion.incrementColumnValue is not used in trunk
[ https://issues.apache.org/jira/browse/HBASE-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5824: --- Status: Patch Available (was: Open) This patch is to enhance single puts to use mutate directly instead of multiput. For HRegion#incrementColumnValue, I think it is ok not to use it. > HRegion.incrementColumnValue is not used in trunk > - > > Key: HBASE-5824 > URL: https://issues.apache.org/jira/browse/HBASE-5824 > Project: HBase > Issue Type: Bug >Reporter: Elliott Clark >Assignee: Jimmy Xiang > Attachments: hbase-5824.patch > > > on 0.94 a call to client.HTable#incrementColumnValue will cause > HRegion#incrementColumnValue. On trunk all calls to > HTable.incrementColumnValue got to HRegion#increment. > My guess is that HTable#incrementColumnValue and HTable#increment serialize > to the same thing over the wire so that the remote HRegionServer no longer > knows which htable method was called. > To repro I checked out trunk and put a break point in > HRegion#incrementColumnValue and then ran TestFromClientSide. The breakpoint > wasn't hit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5824) HRegion.incrementColumnValue is not used in trunk
[ https://issues.apache.org/jira/browse/HBASE-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5824: --- Attachment: hbase-5824.patch > HRegion.incrementColumnValue is not used in trunk > - > > Key: HBASE-5824 > URL: https://issues.apache.org/jira/browse/HBASE-5824 > Project: HBase > Issue Type: Bug >Reporter: Elliott Clark >Assignee: Jimmy Xiang > Attachments: hbase-5824.patch > > > on 0.94 a call to client.HTable#incrementColumnValue will cause > HRegion#incrementColumnValue. On trunk all calls to > HTable.incrementColumnValue got to HRegion#increment. > My guess is that HTable#incrementColumnValue and HTable#increment serialize > to the same thing over the wire so that the remote HRegionServer no longer > knows which htable method was called. > To repro I checked out trunk and put a break point in > HRegion#incrementColumnValue and then ran TestFromClientSide. The breakpoint > wasn't hit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5620) Convert the client protocol of HRegionInterface to PB
[ https://issues.apache.org/jira/browse/HBASE-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5620: --- Status: Patch Available (was: Reopened) hbase-5620-sec.patch is to fix the security unit test failures. When I ran all tests, I forgot the security part, which has a different RPC engine. > Convert the client protocol of HRegionInterface to PB > - > > Key: HBASE-5620 > URL: https://issues.apache.org/jira/browse/HBASE-5620 > Project: HBase > Issue Type: Sub-task > Components: ipc, master, migration, regionserver >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5620-sec.patch, hbase-5620_v3.patch, > hbase-5620_v4.patch, hbase-5620_v4.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5620) Convert the client protocol of HRegionInterface to PB
[ https://issues.apache.org/jira/browse/HBASE-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5620: --- Attachment: hbase-5620-sec.patch > Convert the client protocol of HRegionInterface to PB > - > > Key: HBASE-5620 > URL: https://issues.apache.org/jira/browse/HBASE-5620 > Project: HBase > Issue Type: Sub-task > Components: ipc, master, migration, regionserver >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5620-sec.patch, hbase-5620_v3.patch, > hbase-5620_v4.patch, hbase-5620_v4.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5777) MiniHBaseCluster cannot start multiple region servers
[ https://issues.apache.org/jira/browse/HBASE-5777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5777: --- Status: Open (was: Patch Available) > MiniHBaseCluster cannot start multiple region servers > - > > Key: HBASE-5777 > URL: https://issues.apache.org/jira/browse/HBASE-5777 > Project: HBase > Issue Type: Test >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Attachments: hbase-5777.patch, hbase-5777_v2.patch > > > MiniHBaseCluster can try to start multiple region servers. But all of them > except one will die in putting up the web UI > because of BindException since HConstants.REGIONSERVER_INFO_PORT_AUTO is set > to false by default. > This issue will make many unit tests depending on multiple region servers > flaky, such as TestAdmin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5777) MiniHBaseCluster cannot start multiple region servers
[ https://issues.apache.org/jira/browse/HBASE-5777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5777: --- Attachment: hbase-5777_v2.patch > MiniHBaseCluster cannot start multiple region servers > - > > Key: HBASE-5777 > URL: https://issues.apache.org/jira/browse/HBASE-5777 > Project: HBase > Issue Type: Test >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Attachments: hbase-5777.patch, hbase-5777_v2.patch > > > MiniHBaseCluster can try to start multiple region servers. But all of them > except one will die in putting up the web UI > because of BindException since HConstants.REGIONSERVER_INFO_PORT_AUTO is set > to false by default. > This issue will make many unit tests depending on multiple region servers > flaky, such as TestAdmin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5620) Convert the client protocol of HRegionInterface to PB
[ https://issues.apache.org/jira/browse/HBASE-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5620: --- Status: Patch Available (was: Open) Minor code change. Fixed a bug. > Convert the client protocol of HRegionInterface to PB > - > > Key: HBASE-5620 > URL: https://issues.apache.org/jira/browse/HBASE-5620 > Project: HBase > Issue Type: Sub-task > Components: ipc, master, migration, regionserver >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5620_v3.patch, hbase-5620_v4.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5620) Convert the client protocol of HRegionInterface to PB
[ https://issues.apache.org/jira/browse/HBASE-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5620: --- Attachment: hbase-5620_v4.patch > Convert the client protocol of HRegionInterface to PB > - > > Key: HBASE-5620 > URL: https://issues.apache.org/jira/browse/HBASE-5620 > Project: HBase > Issue Type: Sub-task > Components: ipc, master, migration, regionserver >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5620_v3.patch, hbase-5620_v4.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5620) Convert the client protocol of HRegionInterface to PB
[ https://issues.apache.org/jira/browse/HBASE-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5620: --- Status: Open (was: Patch Available) > Convert the client protocol of HRegionInterface to PB > - > > Key: HBASE-5620 > URL: https://issues.apache.org/jira/browse/HBASE-5620 > Project: HBase > Issue Type: Sub-task > Components: ipc, master, migration, regionserver >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5620_v3.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5777) MiniHBaseCluster cannot start multiple region servers
[ https://issues.apache.org/jira/browse/HBASE-5777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5777: --- Status: Patch Available (was: Open) > MiniHBaseCluster cannot start multiple region servers > - > > Key: HBASE-5777 > URL: https://issues.apache.org/jira/browse/HBASE-5777 > Project: HBase > Issue Type: Test >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Attachments: hbase-5777.patch > > > MiniHBaseCluster can try to start multiple region servers. But all of them > except one will die in putting up the web UI > because of BindException since HConstants.REGIONSERVER_INFO_PORT_AUTO is set > to false by default. > This issue will make many unit tests depends on multiple region servers > flaky, such as TestAdmin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5777) MiniHBaseCluster cannot start multiple region servers
[ https://issues.apache.org/jira/browse/HBASE-5777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5777: --- Description: MiniHBaseCluster can try to start multiple region servers. But all of them except one will die in putting up the web UI because of BindException since HConstants.REGIONSERVER_INFO_PORT_AUTO is set to false by default. This issue will make many unit tests depending on multiple region servers flaky, such as TestAdmin. was: MiniHBaseCluster can try to start multiple region servers. But all of them except one will die in putting up the web UI because of BindException since HConstants.REGIONSERVER_INFO_PORT_AUTO is set to false by default. This issue will make many unit tests depends on multiple region servers flaky, such as TestAdmin. > MiniHBaseCluster cannot start multiple region servers > - > > Key: HBASE-5777 > URL: https://issues.apache.org/jira/browse/HBASE-5777 > Project: HBase > Issue Type: Test >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Attachments: hbase-5777.patch > > > MiniHBaseCluster can try to start multiple region servers. But all of them > except one will die in putting up the web UI > because of BindException since HConstants.REGIONSERVER_INFO_PORT_AUTO is set > to false by default. > This issue will make many unit tests depending on multiple region servers > flaky, such as TestAdmin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5777) MiniHBaseCluster cannot start multiple region servers
[ https://issues.apache.org/jira/browse/HBASE-5777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5777: --- Attachment: hbase-5777.patch > MiniHBaseCluster cannot start multiple region servers > - > > Key: HBASE-5777 > URL: https://issues.apache.org/jira/browse/HBASE-5777 > Project: HBase > Issue Type: Test >Reporter: Jimmy Xiang > Attachments: hbase-5777.patch > > > MiniHBaseCluster can try to start multiple region servers. But all of them > except one will die in putting up the web UI > because of BindException since HConstants.REGIONSERVER_INFO_PORT_AUTO is set > to false by default. > This issue will make many unit tests depends on multiple region servers > flaky, such as TestAdmin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5620) Convert the client protocol of HRegionInterface to PB
[ https://issues.apache.org/jira/browse/HBASE-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5620: --- Attachment: hbase-5620_v3.patch > Convert the client protocol of HRegionInterface to PB > - > > Key: HBASE-5620 > URL: https://issues.apache.org/jira/browse/HBASE-5620 > Project: HBase > Issue Type: Sub-task > Components: ipc, master, migration, regionserver >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5620_v3.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5620) Convert the client protocol of HRegionInterface to PB
[ https://issues.apache.org/jira/browse/HBASE-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5620: --- Hadoop Flags: Reviewed Status: Patch Available (was: Open) > Convert the client protocol of HRegionInterface to PB > - > > Key: HBASE-5620 > URL: https://issues.apache.org/jira/browse/HBASE-5620 > Project: HBase > Issue Type: Sub-task > Components: ipc, master, migration, regionserver >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5620_v3.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5719) Enhance hbck to sideline overlapped mega regions
[ https://issues.apache.org/jira/browse/HBASE-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5719: --- Attachment: 5719_0.94.patch 5719_0.92.patch 5719_0.90.patch > Enhance hbck to sideline overlapped mega regions > > > Key: HBASE-5719 > URL: https://issues.apache.org/jira/browse/HBASE-5719 > Project: HBase > Issue Type: New Feature > Components: hbck >Affects Versions: 0.94.0, 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: 5719.patch, 5719_0.90.patch, 5719_0.92.patch, > 5719_0.94.patch, hbase-5719.patch, hbase-5719_0.90.patch, > hbase-5719_0.92.patch, hbase-5719_0.94.patch, hbase-5719_v3-new.patch, > hbase-5719_v3.patch > > > If there are too many regions in one overlapped group (by default, more than > 10), hbck currently doesn't merge them since it takes time. > In this case, we can sideline some regions in the group and break the > overlapping to fix the inconsistency. Later on, sidelined regions can be > bulk loaded manually. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5719) Enhance hbck to sideline overlapped mega regions
[ https://issues.apache.org/jira/browse/HBASE-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5719: --- Status: Patch Available (was: Open) > Enhance hbck to sideline overlapped mega regions > > > Key: HBASE-5719 > URL: https://issues.apache.org/jira/browse/HBASE-5719 > Project: HBase > Issue Type: New Feature > Components: hbck >Affects Versions: 0.94.0, 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: 5719.patch, hbase-5719.patch, hbase-5719_0.90.patch, > hbase-5719_0.92.patch, hbase-5719_0.94.patch, hbase-5719_v3-new.patch, > hbase-5719_v3.patch > > > If there are too many regions in one overlapped group (by default, more than > 10), hbck currently doesn't merge them since it takes time. > In this case, we can sideline some regions in the group and break the > overlapping to fix the inconsistency. Later on, sidelined regions can be > bulk loaded manually. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5719) Enhance hbck to sideline overlapped mega regions
[ https://issues.apache.org/jira/browse/HBASE-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5719: --- Status: Open (was: Patch Available) > Enhance hbck to sideline overlapped mega regions > > > Key: HBASE-5719 > URL: https://issues.apache.org/jira/browse/HBASE-5719 > Project: HBase > Issue Type: New Feature > Components: hbck >Affects Versions: 0.94.0, 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: 5719.patch, hbase-5719.patch, hbase-5719_0.90.patch, > hbase-5719_0.92.patch, hbase-5719_0.94.patch, hbase-5719_v3-new.patch, > hbase-5719_v3.patch > > > If there are too many regions in one overlapped group (by default, more than > 10), hbck currently doesn't merge them since it takes time. > In this case, we can sideline some regions in the group and break the > overlapping to fix the inconsistency. Later on, sidelined regions can be > bulk loaded manually. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5719) Enhance hbck to sideline overlapped mega regions
[ https://issues.apache.org/jira/browse/HBASE-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5719: --- Attachment: 5719.patch > Enhance hbck to sideline overlapped mega regions > > > Key: HBASE-5719 > URL: https://issues.apache.org/jira/browse/HBASE-5719 > Project: HBase > Issue Type: New Feature > Components: hbck >Affects Versions: 0.94.0, 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: 5719.patch, hbase-5719.patch, hbase-5719_0.90.patch, > hbase-5719_0.92.patch, hbase-5719_0.94.patch, hbase-5719_v3-new.patch, > hbase-5719_v3.patch > > > If there are too many regions in one overlapped group (by default, more than > 10), hbck currently doesn't merge them since it takes time. > In this case, we can sideline some regions in the group and break the > overlapping to fix the inconsistency. Later on, sidelined regions can be > bulk loaded manually. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5719) Enhance hbck to sideline overlapped mega regions
[ https://issues.apache.org/jira/browse/HBASE-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5719: --- Status: Patch Available (was: Open) > Enhance hbck to sideline overlapped mega regions > > > Key: HBASE-5719 > URL: https://issues.apache.org/jira/browse/HBASE-5719 > Project: HBase > Issue Type: New Feature > Components: hbck >Affects Versions: 0.94.0, 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: 5719.patch, hbase-5719.patch, hbase-5719_0.90.patch, > hbase-5719_0.92.patch, hbase-5719_0.94.patch, hbase-5719_v3-new.patch, > hbase-5719_v3.patch > > > If there are too many regions in one overlapped group (by default, more than > 10), hbck currently doesn't merge them since it takes time. > In this case, we can sideline some regions in the group and break the > overlapping to fix the inconsistency. Later on, sidelined regions can be > bulk loaded manually. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5719) Enhance hbck to sideline overlapped mega regions
[ https://issues.apache.org/jira/browse/HBASE-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5719: --- Status: Open (was: Patch Available) > Enhance hbck to sideline overlapped mega regions > > > Key: HBASE-5719 > URL: https://issues.apache.org/jira/browse/HBASE-5719 > Project: HBase > Issue Type: New Feature > Components: hbck >Affects Versions: 0.94.0, 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5719.patch, hbase-5719_0.90.patch, > hbase-5719_0.92.patch, hbase-5719_0.94.patch, hbase-5719_v3-new.patch, > hbase-5719_v3.patch > > > If there are too many regions in one overlapped group (by default, more than > 10), hbck currently doesn't merge them since it takes time. > In this case, we can sideline some regions in the group and break the > overlapping to fix the inconsistency. Later on, sidelined regions can be > bulk loaded manually. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5719) Enhance hbck to sideline overlapped mega regions
[ https://issues.apache.org/jira/browse/HBASE-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5719: --- Status: Open (was: Patch Available) > Enhance hbck to sideline overlapped mega regions > > > Key: HBASE-5719 > URL: https://issues.apache.org/jira/browse/HBASE-5719 > Project: HBase > Issue Type: New Feature > Components: hbck >Affects Versions: 0.94.0, 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5719.patch, hbase-5719_0.90.patch, > hbase-5719_0.92.patch, hbase-5719_0.94.patch, hbase-5719_v3-new.patch, > hbase-5719_v3.patch > > > If there are too many regions in one overlapped group (by default, more than > 10), hbck currently doesn't merge them since it takes time. > In this case, we can sideline some regions in the group and break the > overlapping to fix the inconsistency. Later on, sidelined regions can be > bulk loaded manually. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5719) Enhance hbck to sideline overlapped mega regions
[ https://issues.apache.org/jira/browse/HBASE-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5719: --- Attachment: hbase-5719_v3-new.patch Try it again. The patch applies fine for me. > Enhance hbck to sideline overlapped mega regions > > > Key: HBASE-5719 > URL: https://issues.apache.org/jira/browse/HBASE-5719 > Project: HBase > Issue Type: New Feature > Components: hbck >Affects Versions: 0.94.0, 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5719.patch, hbase-5719_0.90.patch, > hbase-5719_0.92.patch, hbase-5719_0.94.patch, hbase-5719_v3-new.patch, > hbase-5719_v3.patch > > > If there are too many regions in one overlapped group (by default, more than > 10), hbck currently doesn't merge them since it takes time. > In this case, we can sideline some regions in the group and break the > overlapping to fix the inconsistency. Later on, sidelined regions can be > bulk loaded manually. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5719) Enhance hbck to sideline overlapped mega regions
[ https://issues.apache.org/jira/browse/HBASE-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5719: --- Status: Patch Available (was: Open) > Enhance hbck to sideline overlapped mega regions > > > Key: HBASE-5719 > URL: https://issues.apache.org/jira/browse/HBASE-5719 > Project: HBase > Issue Type: New Feature > Components: hbck >Affects Versions: 0.94.0, 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5719.patch, hbase-5719_0.90.patch, > hbase-5719_0.92.patch, hbase-5719_0.94.patch, hbase-5719_v3-new.patch, > hbase-5719_v3.patch > > > If there are too many regions in one overlapped group (by default, more than > 10), hbck currently doesn't merge them since it takes time. > In this case, we can sideline some regions in the group and break the > overlapping to fix the inconsistency. Later on, sidelined regions can be > bulk loaded manually. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5719) Enhance hbck to sideline overlapped mega regions
[ https://issues.apache.org/jira/browse/HBASE-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5719: --- Hadoop Flags: Reviewed Status: Patch Available (was: Open) > Enhance hbck to sideline overlapped mega regions > > > Key: HBASE-5719 > URL: https://issues.apache.org/jira/browse/HBASE-5719 > Project: HBase > Issue Type: New Feature > Components: hbck >Affects Versions: 0.94.0, 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5719.patch, hbase-5719_0.90.patch, > hbase-5719_0.92.patch, hbase-5719_0.94.patch, hbase-5719_v3.patch > > > If there are too many regions in one overlapped group (by default, more than > 10), hbck currently doesn't merge them since it takes time. > In this case, we can sideline some regions in the group and break the > overlapping to fix the inconsistency. Later on, sidelined regions can be > bulk loaded manually. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5719) Enhance hbck to sideline overlapped mega regions
[ https://issues.apache.org/jira/browse/HBASE-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5719: --- Status: Open (was: Patch Available) > Enhance hbck to sideline overlapped mega regions > > > Key: HBASE-5719 > URL: https://issues.apache.org/jira/browse/HBASE-5719 > Project: HBase > Issue Type: New Feature > Components: hbck >Affects Versions: 0.94.0, 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5719.patch, hbase-5719_0.90.patch, > hbase-5719_0.92.patch, hbase-5719_0.94.patch, hbase-5719_v3.patch > > > If there are too many regions in one overlapped group (by default, more than > 10), hbck currently doesn't merge them since it takes time. > In this case, we can sideline some regions in the group and break the > overlapping to fix the inconsistency. Later on, sidelined regions can be > bulk loaded manually. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5719) Enhance hbck to sideline overlapped mega regions
[ https://issues.apache.org/jira/browse/HBASE-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5719: --- Attachment: hbase-5719_v3.patch hbase-5719_0.94.patch hbase-5719_0.92.patch hbase-5719_0.90.patch > Enhance hbck to sideline overlapped mega regions > > > Key: HBASE-5719 > URL: https://issues.apache.org/jira/browse/HBASE-5719 > Project: HBase > Issue Type: New Feature > Components: hbck >Affects Versions: 0.94.0, 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5719.patch, hbase-5719_0.90.patch, > hbase-5719_0.92.patch, hbase-5719_0.94.patch, hbase-5719_v3.patch > > > If there are too many regions in one overlapped group (by default, more than > 10), hbck currently doesn't merge them since it takes time. > In this case, we can sideline some regions in the group and break the > overlapping to fix the inconsistency. Later on, sidelined regions can be > bulk loaded manually. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5759) HBaseClient throws NullPointerException when EOFException should be used.
[ https://issues.apache.org/jira/browse/HBASE-5759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5759: --- Status: Patch Available (was: Open) There is a trailing space. Please remove it before commit it. Thanks. > HBaseClient throws NullPointerException when EOFException should be used. > - > > Key: HBASE-5759 > URL: https://issues.apache.org/jira/browse/HBASE-5759 > Project: HBase > Issue Type: Bug >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Trivial > Attachments: hbase-5759.patch > > > When a RPC data input stream is closed, protobuf doesn't raise an > EOFException, it returns a null RpcResponse object. > We need to check if the response is null before trying to access it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5759) HBaseClient throws NullPointerException when EOFException should be used.
[ https://issues.apache.org/jira/browse/HBASE-5759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5759: --- Attachment: hbase-5759.patch > HBaseClient throws NullPointerException when EOFException should be used. > - > > Key: HBASE-5759 > URL: https://issues.apache.org/jira/browse/HBASE-5759 > Project: HBase > Issue Type: Bug >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Trivial > Attachments: hbase-5759.patch > > > When a RPC data input stream is closed, protobuf doesn't raise an > EOFException, it returns a null RpcResponse object. > We need to check if the response is null before trying to access it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5755) Region sever looking for master forever with cached stale data.
[ https://issues.apache.org/jira/browse/HBASE-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5755: --- Attachment: hbase-5755.patch The other solution is to update ZookeeperNodeTracker.getData to pull data from ZK anyway when this.data is null or empty, which means the contract is different though. > Region sever looking for master forever with cached stale data. > --- > > Key: HBASE-5755 > URL: https://issues.apache.org/jira/browse/HBASE-5755 > Project: HBase > Issue Type: Bug >Affects Versions: 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5755.patch > > > When the master address tracker doesn't have the master address ZK data, or > the cached data is wrong, region server should not use the cached data. > It should pull the data from ZK directly again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5755) Region sever looking for master forever with cached stale data.
[ https://issues.apache.org/jira/browse/HBASE-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5755: --- Status: Patch Available (was: Open) > Region sever looking for master forever with cached stale data. > --- > > Key: HBASE-5755 > URL: https://issues.apache.org/jira/browse/HBASE-5755 > Project: HBase > Issue Type: Bug >Affects Versions: 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5755.patch > > > When the master address tracker doesn't have the master address ZK data, or > the cached data is wrong, region server should not use the cached data. > It should pull the data from ZK directly again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5740) Compaction interruption may be due to balacing
[ https://issues.apache.org/jira/browse/HBASE-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5740: --- Status: Patch Available (was: Open) > Compaction interruption may be due to balacing > -- > > Key: HBASE-5740 > URL: https://issues.apache.org/jira/browse/HBASE-5740 > Project: HBase > Issue Type: Bug >Affects Versions: 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Trivial > Fix For: 0.96.0 > > Attachments: hbase-5740.patch, hbase-5740_v2.patch > > > Currently, the log shows > Aborting compaction of store LOG in region because user requested stop. > But it is actually because of balancing. > Currently, there is no way to figure out who closed the region. So it is > better to change the message to say it is because of user, or balancing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5740) Compaction interruption may be due to balacing
[ https://issues.apache.org/jira/browse/HBASE-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5740: --- Attachment: hbase-5740_v2.patch > Compaction interruption may be due to balacing > -- > > Key: HBASE-5740 > URL: https://issues.apache.org/jira/browse/HBASE-5740 > Project: HBase > Issue Type: Bug >Affects Versions: 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Trivial > Fix For: 0.96.0 > > Attachments: hbase-5740.patch, hbase-5740_v2.patch > > > Currently, the log shows > Aborting compaction of store LOG in region because user requested stop. > But it is actually because of balancing. > Currently, there is no way to figure out who closed the region. So it is > better to change the message to say it is because of user, or balancing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5740) Compaction interruption may be due to balacing
[ https://issues.apache.org/jira/browse/HBASE-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5740: --- Status: Open (was: Patch Available) > Compaction interruption may be due to balacing > -- > > Key: HBASE-5740 > URL: https://issues.apache.org/jira/browse/HBASE-5740 > Project: HBase > Issue Type: Bug >Affects Versions: 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Trivial > Fix For: 0.96.0 > > Attachments: hbase-5740.patch, hbase-5740_v2.patch > > > Currently, the log shows > Aborting compaction of store LOG in region because user requested stop. > But it is actually because of balancing. > Currently, there is no way to figure out who closed the region. So it is > better to change the message to say it is because of user, or balancing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5740) Compaction interruption may be due to balacing
[ https://issues.apache.org/jira/browse/HBASE-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5740: --- Description: Currently, the log shows Aborting compaction of store LOG in region because user requested stop. But it is actually because of balancing. Currently, there is no way to figure out who closed the region. So it is better to change the message to say it is because of user, or balancing. was: Currently, the log shows Aborting compaction of store LOG in region CCS_ACCOUNT_LOG_HBASE02_01,scm01 IDNWNoA0002765 00061395804,1328855408473.8b68adefea8dbc8c77a97ce88cf657a6. because user requested stop. But it is actually because of balancing. Currently, there is no way to figure out who closed the region. So it is better to change the message to say it is because of user, or balancing. > Compaction interruption may be due to balacing > -- > > Key: HBASE-5740 > URL: https://issues.apache.org/jira/browse/HBASE-5740 > Project: HBase > Issue Type: Bug >Affects Versions: 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Trivial > Fix For: 0.96.0 > > Attachments: hbase-5740.patch > > > Currently, the log shows > Aborting compaction of store LOG in region because user requested stop. > But it is actually because of balancing. > Currently, there is no way to figure out who closed the region. So it is > better to change the message to say it is because of user, or balancing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5740) Compaction interruption may be due to balacing
[ https://issues.apache.org/jira/browse/HBASE-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5740: --- Status: Patch Available (was: Open) > Compaction interruption may be due to balacing > -- > > Key: HBASE-5740 > URL: https://issues.apache.org/jira/browse/HBASE-5740 > Project: HBase > Issue Type: Bug >Affects Versions: 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Trivial > Fix For: 0.96.0 > > Attachments: hbase-5740.patch > > > Currently, the log shows > Aborting compaction of store LOG in region CCS_ACCOUNT_LOG_HBASE02_01,scm01 > IDNWNoA0002765 00061395804,1328855408473.8b68adefea8dbc8c77a97ce88cf657a6. > because user requested stop. > But it is actually because of balancing. > Currently, there is no way to figure out who closed the region. So it is > better to change the message to say it is because of user, or balancing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5740) Compaction interruption may be due to balacing
[ https://issues.apache.org/jira/browse/HBASE-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5740: --- Attachment: hbase-5740.patch > Compaction interruption may be due to balacing > -- > > Key: HBASE-5740 > URL: https://issues.apache.org/jira/browse/HBASE-5740 > Project: HBase > Issue Type: Bug >Affects Versions: 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Trivial > Fix For: 0.96.0 > > Attachments: hbase-5740.patch > > > Currently, the log shows > Aborting compaction of store LOG in region CCS_ACCOUNT_LOG_HBASE02_01,scm01 > IDNWNoA0002765 00061395804,1328855408473.8b68adefea8dbc8c77a97ce88cf657a6. > because user requested stop. > But it is actually because of balancing. > Currently, there is no way to figure out who closed the region. So it is > better to change the message to say it is because of user, or balancing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5734) Change hbck sideline root
[ https://issues.apache.org/jira/browse/HBASE-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5734: --- Attachment: hbase-5734.patch > Change hbck sideline root > - > > Key: HBASE-5734 > URL: https://issues.apache.org/jira/browse/HBASE-5734 > Project: HBase > Issue Type: Improvement > Components: hbck >Affects Versions: 0.94.0, 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Trivial > Fix For: 0.96.0 > > Attachments: hbase-5734.patch > > > Currently hbck sideline root is the root which can run into permission issue. > We can change it to /hbck -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5734) Change hbck sideline root
[ https://issues.apache.org/jira/browse/HBASE-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5734: --- Status: Patch Available (was: Open) > Change hbck sideline root > - > > Key: HBASE-5734 > URL: https://issues.apache.org/jira/browse/HBASE-5734 > Project: HBase > Issue Type: Improvement > Components: hbck >Affects Versions: 0.94.0, 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Trivial > Fix For: 0.96.0 > > Attachments: hbase-5734.patch > > > Currently hbck sideline root is the root which can run into permission issue. > We can change it to /hbck -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5734) Change hbck sideline root
[ https://issues.apache.org/jira/browse/HBASE-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5734: --- Component/s: hbck > Change hbck sideline root > - > > Key: HBASE-5734 > URL: https://issues.apache.org/jira/browse/HBASE-5734 > Project: HBase > Issue Type: Improvement > Components: hbck >Affects Versions: 0.94.0, 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Trivial > Fix For: 0.96.0 > > > Currently hbck sideline root is the root which can run into permission issue. > We can change it to /hbck -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5719) Enhance hbck to sideline overlapped mega regions
[ https://issues.apache.org/jira/browse/HBASE-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5719: --- Status: Patch Available (was: Open) > Enhance hbck to sideline overlapped mega regions > > > Key: HBASE-5719 > URL: https://issues.apache.org/jira/browse/HBASE-5719 > Project: HBase > Issue Type: New Feature > Components: hbck >Affects Versions: 0.94.0, 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5719.patch > > > If there are too many regions in one overlapped group (by default, more than > 10), hbck currently doesn't merge them since it takes time. > In this case, we can sideline some regions in the group and break the > overlapping to fix the inconsistency. Later on, sidelined regions can be > bulk loaded manually. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5719) Enhance hbck to sideline overlapped mega regions
[ https://issues.apache.org/jira/browse/HBASE-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5719: --- Attachment: hbase-5719.patch > Enhance hbck to sideline overlapped mega regions > > > Key: HBASE-5719 > URL: https://issues.apache.org/jira/browse/HBASE-5719 > Project: HBase > Issue Type: New Feature > Components: hbck >Affects Versions: 0.94.0, 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5719.patch > > > If there are too many regions in one overlapped group (by default, more than > 10), hbck currently doesn't merge them since it takes time. > In this case, we can sideline some regions in the group and break the > overlapping to fix the inconsistency. Later on, sidelined regions can be > bulk loaded manually. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5619) Create PB protocols for HRegionInterface
[ https://issues.apache.org/jira/browse/HBASE-5619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5619: --- Status: Patch Available (was: Open) I reverted the pom file change, and checked in the generated protobuf classes. > Create PB protocols for HRegionInterface > > > Key: HBASE-5619 > URL: https://issues.apache.org/jira/browse/HBASE-5619 > Project: HBase > Issue Type: Sub-task > Components: ipc, master, migration, regionserver >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5619.patch, hbase-5619_v3.patch, > hbase-5619_v4.patch, hbase-5619_v5.patch > > > Subtask of HBase-5443, separate HRegionInterface into admin protocol and > client protocol, create the PB protocol buffer files -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5619) Create PB protocols for HRegionInterface
[ https://issues.apache.org/jira/browse/HBASE-5619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5619: --- Status: Open (was: Patch Available) > Create PB protocols for HRegionInterface > > > Key: HBASE-5619 > URL: https://issues.apache.org/jira/browse/HBASE-5619 > Project: HBase > Issue Type: Sub-task > Components: ipc, master, migration, regionserver >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5619.patch, hbase-5619_v3.patch, > hbase-5619_v4.patch, hbase-5619_v5.patch > > > Subtask of HBase-5443, separate HRegionInterface into admin protocol and > client protocol, create the PB protocol buffer files -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5619) Create PB protocols for HRegionInterface
[ https://issues.apache.org/jira/browse/HBASE-5619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5619: --- Attachment: hbase-5619_v5.patch > Create PB protocols for HRegionInterface > > > Key: HBASE-5619 > URL: https://issues.apache.org/jira/browse/HBASE-5619 > Project: HBase > Issue Type: Sub-task > Components: ipc, master, migration, regionserver >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5619.patch, hbase-5619_v3.patch, > hbase-5619_v4.patch, hbase-5619_v5.patch > > > Subtask of HBase-5443, separate HRegionInterface into admin protocol and > client protocol, create the PB protocol buffer files -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5619) Create PB protocols for HRegionInterface
[ https://issues.apache.org/jira/browse/HBASE-5619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5619: --- Status: Patch Available (was: Open) > Create PB protocols for HRegionInterface > > > Key: HBASE-5619 > URL: https://issues.apache.org/jira/browse/HBASE-5619 > Project: HBase > Issue Type: Sub-task > Components: ipc, master, migration, regionserver >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5619.patch, hbase-5619_v3.patch, > hbase-5619_v4.patch > > > Subtask of HBase-5443, separate HRegionInterface into admin protocol and > client protocol, create the PB protocol buffer files -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5619) Create PB protocols for HRegionInterface
[ https://issues.apache.org/jira/browse/HBASE-5619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5619: --- Status: Open (was: Patch Available) > Create PB protocols for HRegionInterface > > > Key: HBASE-5619 > URL: https://issues.apache.org/jira/browse/HBASE-5619 > Project: HBase > Issue Type: Sub-task > Components: ipc, master, migration, regionserver >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5619.patch, hbase-5619_v3.patch, > hbase-5619_v4.patch > > > Subtask of HBase-5443, separate HRegionInterface into admin protocol and > client protocol, create the PB protocol buffer files -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5619) Create PB protocols for HRegionInterface
[ https://issues.apache.org/jira/browse/HBASE-5619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5619: --- Attachment: hbase-5619_v4.patch > Create PB protocols for HRegionInterface > > > Key: HBASE-5619 > URL: https://issues.apache.org/jira/browse/HBASE-5619 > Project: HBase > Issue Type: Sub-task > Components: ipc, master, migration, regionserver >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5619.patch, hbase-5619_v3.patch, > hbase-5619_v4.patch > > > Subtask of HBase-5443, separate HRegionInterface into admin protocol and > client protocol, create the PB protocol buffer files -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5619) Create PB protocols for HRegionInterface
[ https://issues.apache.org/jira/browse/HBASE-5619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5619: --- Attachment: hbase-5619_v3.patch > Create PB protocols for HRegionInterface > > > Key: HBASE-5619 > URL: https://issues.apache.org/jira/browse/HBASE-5619 > Project: HBase > Issue Type: Sub-task > Components: ipc, master, migration, regionserver >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5619.patch, hbase-5619_v3.patch > > > Subtask of HBase-5443, separate HRegionInterface into admin protocol and > client protocol, create the PB protocol buffer files -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5619) Create PB protocols for HRegionInterface
[ https://issues.apache.org/jira/browse/HBASE-5619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5619: --- Status: Patch Available (was: Open) > Create PB protocols for HRegionInterface > > > Key: HBASE-5619 > URL: https://issues.apache.org/jira/browse/HBASE-5619 > Project: HBase > Issue Type: Sub-task > Components: ipc, master, migration, regionserver >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5619.patch, hbase-5619_v3.patch > > > Subtask of HBase-5443, separate HRegionInterface into admin protocol and > client protocol, create the PB protocol buffer files -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5619) Create PB protocols for HRegionInterface
[ https://issues.apache.org/jira/browse/HBASE-5619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5619: --- Status: Open (was: Patch Available) > Create PB protocols for HRegionInterface > > > Key: HBASE-5619 > URL: https://issues.apache.org/jira/browse/HBASE-5619 > Project: HBase > Issue Type: Sub-task > Components: ipc, master, migration, regionserver >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5619.patch, hbase-5619_v3.patch > > > Subtask of HBase-5443, separate HRegionInterface into admin protocol and > client protocol, create the PB protocol buffer files -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5619) Create PB protocols for HRegionInterface
[ https://issues.apache.org/jira/browse/HBASE-5619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5619: --- Status: Patch Available (was: Open) > Create PB protocols for HRegionInterface > > > Key: HBASE-5619 > URL: https://issues.apache.org/jira/browse/HBASE-5619 > Project: HBase > Issue Type: Sub-task > Components: ipc, master, migration, regionserver >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5619.patch > > > Subtask of HBase-5443, separate HRegionInterface into admin protocol and > client protocol, create the PB protocol buffer files -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5619) Create PB protocols for HRegionInterface
[ https://issues.apache.org/jira/browse/HBASE-5619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5619: --- Attachment: hbase-5619.patch > Create PB protocols for HRegionInterface > > > Key: HBASE-5619 > URL: https://issues.apache.org/jira/browse/HBASE-5619 > Project: HBase > Issue Type: Sub-task > Components: ipc, master, migration, regionserver >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: hbase-5619.patch > > > Subtask of HBase-5443, separate HRegionInterface into admin protocol and > client protocol, create the PB protocol buffer files -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5443) Add PB-based calls to HRegionInterface
[ https://issues.apache.org/jira/browse/HBASE-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5443: --- Issue Type: Task (was: Sub-task) Parent: (was: HBASE-5305) > Add PB-based calls to HRegionInterface > -- > > Key: HBASE-5443 > URL: https://issues.apache.org/jira/browse/HBASE-5443 > Project: HBase > Issue Type: Task > Components: ipc, master, migration, regionserver >Reporter: Todd Lipcon >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: region_java-proto-mapping.pdf > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5324) Hbck fix dryrun/plan
[ https://issues.apache.org/jira/browse/HBASE-5324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5324: --- Fix Version/s: (was: 0.94.0) 0.96.0 Moved to 0.96 > Hbck fix dryrun/plan > - > > Key: HBASE-5324 > URL: https://issues.apache.org/jira/browse/HBASE-5324 > Project: HBase > Issue Type: New Feature > Components: hbck >Affects Versions: 0.94.0 >Reporter: Jimmy Xiang > Fix For: 0.96.0 > > > Hbck fix should have a dryrun option, or show the planned operations/steps at > first, then start the actual fix after confirmed by the user. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5443) Add PB-based calls to HRegionInterface
[ https://issues.apache.org/jira/browse/HBASE-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5443: --- Attachment: region_java-proto-mapping.pdf In the attached region_java-proto-mapping.pdf file, I have the first draft of proto rpc methods to the java interface mapping. Please review, especially the following questions: 1. Should we combine put and delete to one method? Their signatures are kind of the same. 2. mutateRow(regionName, RowMutations) For multiple puts or deletes, the new put/delete can support as long as there are no mixed puts and deletes. Do we have to support mixed puts and deletes in RPC? Can we separate them in HBaseClient? 3. multi(MultiAction) This one is too complicated. I think we should not put this in RPC. We can separate them in HBaseClient and call corresponding puts/deletes/gets? > Add PB-based calls to HRegionInterface > -- > > Key: HBASE-5443 > URL: https://issues.apache.org/jira/browse/HBASE-5443 > Project: HBase > Issue Type: Sub-task > Components: ipc, master, migration, regionserver >Reporter: Todd Lipcon >Assignee: Jimmy Xiang > Attachments: region_java-proto-mapping.pdf > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4403) Adopt interface stability/audience classifications from Hadoop
[ https://issues.apache.org/jira/browse/HBASE-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-4403: --- Status: Patch Available (was: Open) > Adopt interface stability/audience classifications from Hadoop > -- > > Key: HBASE-4403 > URL: https://issues.apache.org/jira/browse/HBASE-4403 > Project: HBase > Issue Type: Task >Affects Versions: 0.92.0, 0.90.5 >Reporter: Todd Lipcon >Assignee: Jimmy Xiang > Fix For: 0.94.0 > > Attachments: hbase-4403-interface.txt, hbase-4403-interface_v2.txt, > hbase-4403-interface_v3.txt, hbase-4403-nowhere-near-done.txt, > hbase-4403.patch, hbase-4403.patch > > > As HBase gets more widely used, we need to be more explicit about which APIs > are stable and not expected to break between versions, which APIs are still > evolving, etc. We also have many public classes that are really internal to > the RS or Master and not meant to be used by users. Hadoop has adopted a > classification scheme for audience (public, private, or limited-private) as > well as stability (stable, evolving, unstable). I think we should copy these > annotations to HBase and start to classify our public classes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4403) Adopt interface stability/audience classifications from Hadoop
[ https://issues.apache.org/jira/browse/HBASE-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-4403: --- Status: Open (was: Patch Available) > Adopt interface stability/audience classifications from Hadoop > -- > > Key: HBASE-4403 > URL: https://issues.apache.org/jira/browse/HBASE-4403 > Project: HBase > Issue Type: Task >Affects Versions: 0.92.0, 0.90.5 >Reporter: Todd Lipcon >Assignee: Jimmy Xiang > Fix For: 0.94.0 > > Attachments: hbase-4403-interface.txt, hbase-4403-interface_v2.txt, > hbase-4403-interface_v3.txt, hbase-4403-nowhere-near-done.txt, > hbase-4403.patch, hbase-4403.patch > > > As HBase gets more widely used, we need to be more explicit about which APIs > are stable and not expected to break between versions, which APIs are still > evolving, etc. We also have many public classes that are really internal to > the RS or Master and not meant to be used by users. Hadoop has adopted a > classification scheme for audience (public, private, or limited-private) as > well as stability (stable, evolving, unstable). I think we should copy these > annotations to HBase and start to classify our public classes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4403) Adopt interface stability/audience classifications from Hadoop
[ https://issues.apache.org/jira/browse/HBASE-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-4403: --- Attachment: hbase-4403.patch > Adopt interface stability/audience classifications from Hadoop > -- > > Key: HBASE-4403 > URL: https://issues.apache.org/jira/browse/HBASE-4403 > Project: HBase > Issue Type: Task >Affects Versions: 0.90.5, 0.92.0 >Reporter: Todd Lipcon >Assignee: Jimmy Xiang > Fix For: 0.94.0 > > Attachments: hbase-4403-interface.txt, hbase-4403-interface_v2.txt, > hbase-4403-interface_v3.txt, hbase-4403-nowhere-near-done.txt, > hbase-4403.patch, hbase-4403.patch > > > As HBase gets more widely used, we need to be more explicit about which APIs > are stable and not expected to break between versions, which APIs are still > evolving, etc. We also have many public classes that are really internal to > the RS or Master and not meant to be used by users. Hadoop has adopted a > classification scheme for audience (public, private, or limited-private) as > well as stability (stable, evolving, unstable). I think we should copy these > annotations to HBase and start to classify our public classes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4403) Adopt interface stability/audience classifications from Hadoop
[ https://issues.apache.org/jira/browse/HBASE-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-4403: --- Fix Version/s: 0.94.0 Status: Patch Available (was: Open) > Adopt interface stability/audience classifications from Hadoop > -- > > Key: HBASE-4403 > URL: https://issues.apache.org/jira/browse/HBASE-4403 > Project: HBase > Issue Type: Task >Affects Versions: 0.92.0, 0.90.5 >Reporter: Todd Lipcon >Assignee: Jimmy Xiang > Fix For: 0.94.0 > > Attachments: hbase-4403-interface.txt, hbase-4403-interface_v2.txt, > hbase-4403-interface_v3.txt, hbase-4403-nowhere-near-done.txt, > hbase-4403.patch > > > As HBase gets more widely used, we need to be more explicit about which APIs > are stable and not expected to break between versions, which APIs are still > evolving, etc. We also have many public classes that are really internal to > the RS or Master and not meant to be used by users. Hadoop has adopted a > classification scheme for audience (public, private, or limited-private) as > well as stability (stable, evolving, unstable). I think we should copy these > annotations to HBase and start to classify our public classes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4403) Adopt interface stability/audience classifications from Hadoop
[ https://issues.apache.org/jira/browse/HBASE-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-4403: --- Attachment: hbase-4403-interface_v3.txt hbase-4403.patch > Adopt interface stability/audience classifications from Hadoop > -- > > Key: HBASE-4403 > URL: https://issues.apache.org/jira/browse/HBASE-4403 > Project: HBase > Issue Type: Task >Affects Versions: 0.90.5, 0.92.0 >Reporter: Todd Lipcon >Assignee: Jimmy Xiang > Fix For: 0.94.0 > > Attachments: hbase-4403-interface.txt, hbase-4403-interface_v2.txt, > hbase-4403-interface_v3.txt, hbase-4403-nowhere-near-done.txt, > hbase-4403.patch > > > As HBase gets more widely used, we need to be more explicit about which APIs > are stable and not expected to break between versions, which APIs are still > evolving, etc. We also have many public classes that are really internal to > the RS or Master and not meant to be used by users. Hadoop has adopted a > classification scheme for audience (public, private, or limited-private) as > well as stability (stable, evolving, unstable). I think we should copy these > annotations to HBase and start to classify our public classes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4403) Adopt interface stability/audience classifications from Hadoop
[ https://issues.apache.org/jira/browse/HBASE-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-4403: --- Attachment: hbase-4403-interface_v2.txt I got some distraction. Here is the v2 I have so far. I already added MiniZookeeper cluster as public, Evolving. I'd like to add MiniHBaseCluster as well but it is in test folder. Do we classify those classes in test folder? Should we move them to the main folder? > Adopt interface stability/audience classifications from Hadoop > -- > > Key: HBASE-4403 > URL: https://issues.apache.org/jira/browse/HBASE-4403 > Project: HBase > Issue Type: Task >Affects Versions: 0.90.5, 0.92.0 >Reporter: Todd Lipcon >Assignee: Jimmy Xiang > Attachments: hbase-4403-interface.txt, hbase-4403-interface_v2.txt, > hbase-4403-nowhere-near-done.txt > > > As HBase gets more widely used, we need to be more explicit about which APIs > are stable and not expected to break between versions, which APIs are still > evolving, etc. We also have many public classes that are really internal to > the RS or Master and not meant to be used by users. Hadoop has adopted a > classification scheme for audience (public, private, or limited-private) as > well as stability (stable, evolving, unstable). I think we should copy these > annotations to HBase and start to classify our public classes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4403) Adopt interface stability/audience classifications from Hadoop
[ https://issues.apache.org/jira/browse/HBASE-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-4403: --- Attachment: hbase-4403-interface.txt > Adopt interface stability/audience classifications from Hadoop > -- > > Key: HBASE-4403 > URL: https://issues.apache.org/jira/browse/HBASE-4403 > Project: HBase > Issue Type: Task >Affects Versions: 0.90.5, 0.92.0 >Reporter: Todd Lipcon >Assignee: Jimmy Xiang > Attachments: hbase-4403-interface.txt, > hbase-4403-nowhere-near-done.txt > > > As HBase gets more widely used, we need to be more explicit about which APIs > are stable and not expected to break between versions, which APIs are still > evolving, etc. We also have many public classes that are really internal to > the RS or Master and not meant to be used by users. Hadoop has adopted a > classification scheme for audience (public, private, or limited-private) as > well as stability (stable, evolving, unstable). I think we should copy these > annotations to HBase and start to classify our public classes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5410) Deprecate check_meta.rb
[ https://issues.apache.org/jira/browse/HBASE-5410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5410: --- Description: We should depreate check_meta.rb and suggest users to use hbck instead. hbck should give more accurate region hole information. Should we remove check_meta.rb from both 92 and 94? was: We should depreate check_meta.rb and suggest users to use hbck instead. hbck should give more accurate region hole information. Should we remove check_meta.rb in 92 and 94? > Deprecate check_meta.rb > --- > > Key: HBASE-5410 > URL: https://issues.apache.org/jira/browse/HBASE-5410 > Project: HBase > Issue Type: Task >Reporter: Jimmy Xiang >Priority: Trivial > > We should depreate check_meta.rb and suggest users to use hbck instead. > hbck should give more accurate region hole information. > Should we remove check_meta.rb from both 92 and 94? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5394) Add ability to include Protobufs in HbaseObjectWritable
[ https://issues.apache.org/jira/browse/HBASE-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5394: --- Hadoop Flags: (was: Reviewed) Status: Patch Available (was: Open) > Add ability to include Protobufs in HbaseObjectWritable > --- > > Key: HBASE-5394 > URL: https://issues.apache.org/jira/browse/HBASE-5394 > Project: HBase > Issue Type: Improvement >Affects Versions: 0.94.0 >Reporter: Zhihong Yu >Assignee: Jimmy Xiang > Fix For: 0.94.0 > > Attachments: hbase-5394.txt > > > This is a port of HADOOP-7379 > This is to add the cases to HbaseObjectWritable to handle subclasses of > Message, the superclass of codegenned protobufs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5394) Add ability to include Protobufs in HbaseObjectWritable
[ https://issues.apache.org/jira/browse/HBASE-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5394: --- Status: Open (was: Patch Available) > Add ability to include Protobufs in HbaseObjectWritable > --- > > Key: HBASE-5394 > URL: https://issues.apache.org/jira/browse/HBASE-5394 > Project: HBase > Issue Type: Improvement >Affects Versions: 0.94.0 >Reporter: Zhihong Yu >Assignee: Jimmy Xiang > Fix For: 0.94.0 > > Attachments: hbase-5394.txt > > > This is a port of HADOOP-7379 > This is to add the cases to HbaseObjectWritable to handle subclasses of > Message, the superclass of codegenned protobufs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5394) Add ability to include Protobufs in HbaseObjectWritable
[ https://issues.apache.org/jira/browse/HBASE-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5394: --- Affects Version/s: 0.94.0 Fix Version/s: 0.94.0 > Add ability to include Protobufs in HbaseObjectWritable > --- > > Key: HBASE-5394 > URL: https://issues.apache.org/jira/browse/HBASE-5394 > Project: HBase > Issue Type: Improvement >Affects Versions: 0.94.0 >Reporter: Zhihong Yu >Assignee: Jimmy Xiang > Fix For: 0.94.0 > > Attachments: hbase-5394.txt > > > This is a port of HADOOP-7379 > This is to add the cases to HbaseObjectWritable to handle subclasses of > Message, the superclass of codegenned protobufs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5394) Add ability to include Protobufs in HbaseObjectWritable
[ https://issues.apache.org/jira/browse/HBASE-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5394: --- Hadoop Flags: Reviewed Status: Patch Available (was: Open) > Add ability to include Protobufs in HbaseObjectWritable > --- > > Key: HBASE-5394 > URL: https://issues.apache.org/jira/browse/HBASE-5394 > Project: HBase > Issue Type: Improvement >Reporter: Zhihong Yu >Assignee: Jimmy Xiang > Attachments: hbase-5394.txt > > > This is a port of HADOOP-7379 > This is to add the cases to HbaseObjectWritable to handle subclasses of > Message, the superclass of codegenned protobufs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5394) Add ability to include Protobufs in HbaseObjectWritable
[ https://issues.apache.org/jira/browse/HBASE-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5394: --- Attachment: hbase-5394.txt > Add ability to include Protobufs in HbaseObjectWritable > --- > > Key: HBASE-5394 > URL: https://issues.apache.org/jira/browse/HBASE-5394 > Project: HBase > Issue Type: Improvement >Reporter: Zhihong Yu >Assignee: Jimmy Xiang > Attachments: hbase-5394.txt > > > This is a port of HADOOP-7379 > This is to add the cases to HbaseObjectWritable to handle subclasses of > Message, the superclass of codegenned protobufs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5327) Print a message when an invalid hbase.rootdir is passed
[
https://issues.apache.org/jira/browse/HBASE-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Xiang updated HBASE-5327:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Print a message when an invalid hbase.rootdir is passed
> ---
>
> Key: HBASE-5327
> URL: https://issues.apache.org/jira/browse/HBASE-5327
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.90.5
>Reporter: Jean-Daniel Cryans
>Assignee: Jimmy Xiang
> Fix For: 0.94.0, 0.90.6, 0.92.1
>
> Attachments: hbase-5327.txt, hbase-5327_v2.txt
>
>
> As seen on the mailing list:
> http://comments.gmane.org/gmane.comp.java.hadoop.hbase.user/24124
> If hbase.rootdir doesn't specify a folder on hdfs we crash while opening a
> path to .oldlogs:
> {noformat}
> 2012-02-02 23:07:26,292 FATAL org.apache.hadoop.hbase.master.HMaster:
> Unhandled exception. Starting shutdown.
> java.lang.IllegalArgumentException: java.net.URISyntaxException: Relative
> path in absolute URI: hdfs://sv4r11s38:9100.oldlogs
> at org.apache.hadoop.fs.Path.initialize(Path.java:148)
> at org.apache.hadoop.fs.Path.(Path.java:71)
> at org.apache.hadoop.fs.Path.(Path.java:50)
> at
> org.apache.hadoop.hbase.master.MasterFileSystem.(MasterFileSystem.java:112)
> at
> org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:448)
> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:326)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.net.URISyntaxException: Relative path in absolute URI:
> hdfs://sv4r11s38:9100.oldlogs
> at java.net.URI.checkPath(URI.java:1787)
> at java.net.URI.(URI.java:735)
> at org.apache.hadoop.fs.Path.initialize(Path.java:145)
> ... 6 more
> {noformat}
> It could also crash anywhere else, this just happens to be the first place we
> use hbase.rootdir. We need to verify that it's an actual folder.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5398) HBase shell disable_all/enable_all/drop_all promp wrong tables for confirmation
[ https://issues.apache.org/jira/browse/HBASE-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5398: --- Description: When using hbase shell to disable_all/enable_all/drop_all tables, the tables prompted for confirmation are wrong. For example, disable_all 'test*' will ask form confirmation to diable tables like: mytest1 test123 Fortunately, these tables will not be disabled actually since Java pattern doesn't match this way. was: When using hbase shell to disable_all/enable_all/drop_all tables, the tables prompted for confirmation are wrong. For example, disable_all 'test*' will show confirmation for diable tables like: mytest1 test123 Fortunately, these tables will not be disable actually since Java pattern doesn't match this way. > HBase shell disable_all/enable_all/drop_all promp wrong tables for > confirmation > --- > > Key: HBASE-5398 > URL: https://issues.apache.org/jira/browse/HBASE-5398 > Project: HBase > Issue Type: Bug > Components: scripts >Affects Versions: 0.94.0, 0.92.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.94.0, 0.92.0 > > Attachments: hbase-5398.patch > > > When using hbase shell to disable_all/enable_all/drop_all tables, the tables > prompted for confirmation are wrong. > For example, disable_all 'test*' > will ask form confirmation to diable tables like: > mytest1 > test123 > Fortunately, these tables will not be disabled actually since Java pattern > doesn't match this way. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5398) HBase shell disable_all/enable_all/drop_all promp wrong tables for confirmation
[ https://issues.apache.org/jira/browse/HBASE-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5398: --- Status: Patch Available (was: Open) > HBase shell disable_all/enable_all/drop_all promp wrong tables for > confirmation > --- > > Key: HBASE-5398 > URL: https://issues.apache.org/jira/browse/HBASE-5398 > Project: HBase > Issue Type: Bug > Components: scripts >Affects Versions: 0.92.0, 0.94.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.94.0, 0.92.0 > > Attachments: hbase-5398.patch > > > When using hbase shell to disable_all/enable_all/drop_all tables, the tables > prompted for confirmation are wrong. > For example, disable_all 'test*' > will show confirmation for diable tables like: > mytest1 > test123 > Fortunately, these tables will not be disable actually since Java pattern > doesn't match this way. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5398) HBase shell disable_all/enable_all/drop_all promp wrong tables for confirmation
[ https://issues.apache.org/jira/browse/HBASE-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5398: --- Attachment: hbase-5398.patch > HBase shell disable_all/enable_all/drop_all promp wrong tables for > confirmation > --- > > Key: HBASE-5398 > URL: https://issues.apache.org/jira/browse/HBASE-5398 > Project: HBase > Issue Type: Bug > Components: scripts >Affects Versions: 0.94.0, 0.92.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.94.0, 0.92.0 > > Attachments: hbase-5398.patch > > > When using hbase shell to disable_all/enable_all/drop_all tables, the tables > prompted for confirmation are wrong. > For example, disable_all 'test*' > will show confirmation for diable tables like: > mytest1 > test123 > Fortunately, these tables will not be disable actually since Java pattern > doesn't match this way. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5376) Add more logging to triage HBASE-5312: Closed parent region present in Hlog.lastSeqWritten
[ https://issues.apache.org/jira/browse/HBASE-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5376: --- Attachment: hbase-5376.txt I added some warnings. Anywhere else should I add too? > Add more logging to triage HBASE-5312: Closed parent region present in > Hlog.lastSeqWritten > -- > > Key: HBASE-5376 > URL: https://issues.apache.org/jira/browse/HBASE-5376 > Project: HBase > Issue Type: Sub-task >Reporter: Jimmy Xiang >Priority: Minor > Fix For: 0.90.7 > > Attachments: hbase-5376.txt > > > It is hard to find out what exactly caused HBASE-5312. Some logging will be > helpful to shine some lights. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5327) Print a message when an invalid hbase.rootdir is passed
[
https://issues.apache.org/jira/browse/HBASE-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Xiang updated HBASE-5327:
---
Attachment: hbase-5327_v2.txt
> Print a message when an invalid hbase.rootdir is passed
> ---
>
> Key: HBASE-5327
> URL: https://issues.apache.org/jira/browse/HBASE-5327
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.90.5
>Reporter: Jean-Daniel Cryans
>Assignee: Jimmy Xiang
> Fix For: 0.94.0, 0.90.7, 0.92.1
>
> Attachments: hbase-5327.txt, hbase-5327_v2.txt
>
>
> As seen on the mailing list:
> http://comments.gmane.org/gmane.comp.java.hadoop.hbase.user/24124
> If hbase.rootdir doesn't specify a folder on hdfs we crash while opening a
> path to .oldlogs:
> {noformat}
> 2012-02-02 23:07:26,292 FATAL org.apache.hadoop.hbase.master.HMaster:
> Unhandled exception. Starting shutdown.
> java.lang.IllegalArgumentException: java.net.URISyntaxException: Relative
> path in absolute URI: hdfs://sv4r11s38:9100.oldlogs
> at org.apache.hadoop.fs.Path.initialize(Path.java:148)
> at org.apache.hadoop.fs.Path.(Path.java:71)
> at org.apache.hadoop.fs.Path.(Path.java:50)
> at
> org.apache.hadoop.hbase.master.MasterFileSystem.(MasterFileSystem.java:112)
> at
> org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:448)
> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:326)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.net.URISyntaxException: Relative path in absolute URI:
> hdfs://sv4r11s38:9100.oldlogs
> at java.net.URI.checkPath(URI.java:1787)
> at java.net.URI.(URI.java:735)
> at org.apache.hadoop.fs.Path.initialize(Path.java:145)
> ... 6 more
> {noformat}
> It could also crash anywhere else, this just happens to be the first place we
> use hbase.rootdir. We need to verify that it's an actual folder.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5327) Print a message when an invalid hbase.rootdir is passed
[
https://issues.apache.org/jira/browse/HBASE-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Xiang updated HBASE-5327:
---
Status: Patch Available (was: Open)
I tested the patch and it can detect the error mentioned in the description and
abort the master with error message saying it is not a valid hdfs file path.
> Print a message when an invalid hbase.rootdir is passed
> ---
>
> Key: HBASE-5327
> URL: https://issues.apache.org/jira/browse/HBASE-5327
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.90.5
>Reporter: Jean-Daniel Cryans
>Assignee: Jimmy Xiang
> Fix For: 0.94.0, 0.90.7, 0.92.1
>
> Attachments: hbase-5327.txt
>
>
> As seen on the mailing list:
> http://comments.gmane.org/gmane.comp.java.hadoop.hbase.user/24124
> If hbase.rootdir doesn't specify a folder on hdfs we crash while opening a
> path to .oldlogs:
> {noformat}
> 2012-02-02 23:07:26,292 FATAL org.apache.hadoop.hbase.master.HMaster:
> Unhandled exception. Starting shutdown.
> java.lang.IllegalArgumentException: java.net.URISyntaxException: Relative
> path in absolute URI: hdfs://sv4r11s38:9100.oldlogs
> at org.apache.hadoop.fs.Path.initialize(Path.java:148)
> at org.apache.hadoop.fs.Path.(Path.java:71)
> at org.apache.hadoop.fs.Path.(Path.java:50)
> at
> org.apache.hadoop.hbase.master.MasterFileSystem.(MasterFileSystem.java:112)
> at
> org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:448)
> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:326)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.net.URISyntaxException: Relative path in absolute URI:
> hdfs://sv4r11s38:9100.oldlogs
> at java.net.URI.checkPath(URI.java:1787)
> at java.net.URI.(URI.java:735)
> at org.apache.hadoop.fs.Path.initialize(Path.java:145)
> ... 6 more
> {noformat}
> It could also crash anywhere else, this just happens to be the first place we
> use hbase.rootdir. We need to verify that it's an actual folder.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5327) Print a message when an invalid hbase.rootdir is passed
[
https://issues.apache.org/jira/browse/HBASE-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Xiang updated HBASE-5327:
---
Attachment: hbase-5327.txt
> Print a message when an invalid hbase.rootdir is passed
> ---
>
> Key: HBASE-5327
> URL: https://issues.apache.org/jira/browse/HBASE-5327
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.90.5
>Reporter: Jean-Daniel Cryans
>Assignee: Jimmy Xiang
> Fix For: 0.94.0, 0.90.7, 0.92.1
>
> Attachments: hbase-5327.txt
>
>
> As seen on the mailing list:
> http://comments.gmane.org/gmane.comp.java.hadoop.hbase.user/24124
> If hbase.rootdir doesn't specify a folder on hdfs we crash while opening a
> path to .oldlogs:
> {noformat}
> 2012-02-02 23:07:26,292 FATAL org.apache.hadoop.hbase.master.HMaster:
> Unhandled exception. Starting shutdown.
> java.lang.IllegalArgumentException: java.net.URISyntaxException: Relative
> path in absolute URI: hdfs://sv4r11s38:9100.oldlogs
> at org.apache.hadoop.fs.Path.initialize(Path.java:148)
> at org.apache.hadoop.fs.Path.(Path.java:71)
> at org.apache.hadoop.fs.Path.(Path.java:50)
> at
> org.apache.hadoop.hbase.master.MasterFileSystem.(MasterFileSystem.java:112)
> at
> org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:448)
> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:326)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.net.URISyntaxException: Relative path in absolute URI:
> hdfs://sv4r11s38:9100.oldlogs
> at java.net.URI.checkPath(URI.java:1787)
> at java.net.URI.(URI.java:735)
> at org.apache.hadoop.fs.Path.initialize(Path.java:145)
> ... 6 more
> {noformat}
> It could also crash anywhere else, this just happens to be the first place we
> use hbase.rootdir. We need to verify that it's an actual folder.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5221) bin/hbase script doesn't look for Hadoop jars in the right place in trunk layout
[ https://issues.apache.org/jira/browse/HBASE-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5221: --- Status: Patch Available (was: Open) > bin/hbase script doesn't look for Hadoop jars in the right place in trunk > layout > > > Key: HBASE-5221 > URL: https://issues.apache.org/jira/browse/HBASE-5221 > Project: HBase > Issue Type: Bug >Affects Versions: 0.92.0 >Reporter: Todd Lipcon >Assignee: Jimmy Xiang > Attachments: hbase-5221.txt > > > Running against an 0.24.0-SNAPSHOT hadoop: > ls: cannot access > /home/todd/ha-demo/hadoop-0.24.0-SNAPSHOT/hadoop-common*.jar: No such file or > directory > ls: cannot access /home/todd/ha-demo/hadoop-0.24.0-SNAPSHOT/hadoop-hdfs*.jar: > No such file or directory > ls: cannot access > /home/todd/ha-demo/hadoop-0.24.0-SNAPSHOT/hadoop-mapred*.jar: No such file or > directory > The jars are rooted deeper in the heirarchy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5221) bin/hbase script doesn't look for Hadoop jars in the right place in trunk layout
[ https://issues.apache.org/jira/browse/HBASE-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5221: --- Attachment: hbase-5221.txt > bin/hbase script doesn't look for Hadoop jars in the right place in trunk > layout > > > Key: HBASE-5221 > URL: https://issues.apache.org/jira/browse/HBASE-5221 > Project: HBase > Issue Type: Bug >Affects Versions: 0.92.0 >Reporter: Todd Lipcon >Assignee: Jimmy Xiang > Attachments: hbase-5221.txt > > > Running against an 0.24.0-SNAPSHOT hadoop: > ls: cannot access > /home/todd/ha-demo/hadoop-0.24.0-SNAPSHOT/hadoop-common*.jar: No such file or > directory > ls: cannot access /home/todd/ha-demo/hadoop-0.24.0-SNAPSHOT/hadoop-hdfs*.jar: > No such file or directory > ls: cannot access > /home/todd/ha-demo/hadoop-0.24.0-SNAPSHOT/hadoop-mapred*.jar: No such file or > directory > The jars are rooted deeper in the heirarchy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5310) HConnectionManager server cache key enhancement
[ https://issues.apache.org/jira/browse/HBASE-5310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5310: --- Resolution: Fixed Status: Resolved (was: Patch Available) > HConnectionManager server cache key enhancement > --- > > Key: HBASE-5310 > URL: https://issues.apache.org/jira/browse/HBASE-5310 > Project: HBase > Issue Type: Improvement > Components: client >Affects Versions: 0.94.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > Fix For: 0.94.0 > > Attachments: hbase-5310.txt > > > HConnectionManager uses deprecated HServerAddress to create server cache key > which needs to resolve the address every time. > It should be better to use HRegionLocation.getHostnamePort() instead. > In our cluster we have some DNS issue, resolving an address fails sometime > which kills the application since it is a runtime > exception IllegalArgumentException thrown at > HServerAddress.getResolvedAddress. This change will fix this issue as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5310) HConnectionManager cache server name enhancement
[ https://issues.apache.org/jira/browse/HBASE-5310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5310: --- Status: Patch Available (was: Open) > HConnectionManager cache server name enhancement > > > Key: HBASE-5310 > URL: https://issues.apache.org/jira/browse/HBASE-5310 > Project: HBase > Issue Type: Improvement > Components: client >Affects Versions: 0.94.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > Fix For: 0.94.0 > > Attachments: hbase-5310.txt > > > HConnectionManager uses deprecated HServerAddress to create server cache key > which needs to resolve the address every time. > It should be better to use HRegionLocation.getHostnamePort() instead. > In our cluster we have some DNS issue, resolving an address fails sometime > which kills the application since it is a runtime > exception IllegalArgumentException thrown at > HServerAddress.getResolvedAddress. This change will fix this issue as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5310) HConnectionManager cache server name enhancement
[ https://issues.apache.org/jira/browse/HBASE-5310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5310: --- Attachment: hbase-5310.txt > HConnectionManager cache server name enhancement > > > Key: HBASE-5310 > URL: https://issues.apache.org/jira/browse/HBASE-5310 > Project: HBase > Issue Type: Improvement > Components: client >Affects Versions: 0.94.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > Fix For: 0.94.0 > > Attachments: hbase-5310.txt > > > HConnectionManager uses deprecated HServerAddress to create server cache key > which needs to resolve the address every time. > It should be better to use HRegionLocation.getHostnamePort() instead. > In our cluster we have some DNS issue, resolving an address fails sometime > which kills the application since it is a runtime > exception IllegalArgumentException thrown at > HServerAddress.getResolvedAddress. This change will fix this issue as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5239) Suppress hbase file or dir doesn't exist warning
[ https://issues.apache.org/jira/browse/HBASE-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5239: --- Resolution: Duplicate Status: Resolved (was: Patch Available) It's better to fix it properly, using HBASE-5221 instead. > Suppress hbase file or dir doesn't exist warning > > > Key: HBASE-5239 > URL: https://issues.apache.org/jira/browse/HBASE-5239 > Project: HBase > Issue Type: Improvement >Affects Versions: 0.92.0, 0.94.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Trivial > Attachments: 5239.txt > > > I got these warnings in running hbase shell. It causes some confusion. > I think it is safe to suppress them. > ls: cannot access .../hadoop-common*.jar: No such file or directory > ls: cannot access .../hadoop-hdfs*.jar: No such file or directory > ls: cannot access .../hadoop-mapred*.jar: No such file or directory -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5239) Suppress hbase file or dir doesn't exist warning
[ https://issues.apache.org/jira/browse/HBASE-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5239: --- Status: Patch Available (was: Open) > Suppress hbase file or dir doesn't exist warning > > > Key: HBASE-5239 > URL: https://issues.apache.org/jira/browse/HBASE-5239 > Project: HBase > Issue Type: Improvement >Affects Versions: 0.92.0, 0.94.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Trivial > Attachments: 5239.txt > > > I got these warnings in running hbase shell. It causes some confusion. > I think it is safe to suppress them. > ls: cannot access .../hadoop-common*.jar: No such file or directory > ls: cannot access .../hadoop-hdfs*.jar: No such file or directory > ls: cannot access .../hadoop-mapred*.jar: No such file or directory -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5239) Suppress hbase file or dir doesn't exist warning
[ https://issues.apache.org/jira/browse/HBASE-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5239: --- Attachment: 5239.txt > Suppress hbase file or dir doesn't exist warning > > > Key: HBASE-5239 > URL: https://issues.apache.org/jira/browse/HBASE-5239 > Project: HBase > Issue Type: Improvement >Affects Versions: 0.92.0, 0.94.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Trivial > Attachments: 5239.txt > > > I got these warnings in running hbase shell. It causes some confusion. > I think it is safe to suppress them. > ls: cannot access .../hadoop-common*.jar: No such file or directory > ls: cannot access .../hadoop-hdfs*.jar: No such file or directory > ls: cannot access .../hadoop-mapred*.jar: No such file or directory -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5150) Failure in a thread may not fail a test, clean up log splitting test
[ https://issues.apache.org/jira/browse/HBASE-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5150: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Failure in a thread may not fail a test, clean up log splitting test > > > Key: HBASE-5150 > URL: https://issues.apache.org/jira/browse/HBASE-5150 > Project: HBase > Issue Type: Test >Affects Versions: 0.94.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > Fix For: 0.94.0 > > Attachments: hbase-5150.txt, hbase_5150_v3.patch > > > This is to clean up some tests for HBASE-5081. The Assert.fail method in a > separate thread will terminate the thread, but may not fail the test. > We can use callable, so that we can get the error in getting the result. > Some documentation to explain the test will be helpful too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5196) Failure in region split after PONR could cause region hole
[ https://issues.apache.org/jira/browse/HBASE-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5196: --- Attachment: hbase-5196_0.90.txt > Failure in region split after PONR could cause region hole > -- > > Key: HBASE-5196 > URL: https://issues.apache.org/jira/browse/HBASE-5196 > Project: HBase > Issue Type: Bug > Components: master, regionserver >Affects Versions: 0.92.0, 0.94.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.92.0, 0.94.0 > > Attachments: 5196-v2.txt, hbase-5196_0.90.txt > > > If region split fails after PONR, it relies on the master ServerShutdown > handler to fix it. However, if the master doesn't get a chance to fix it. > There will be a hole in the region chain. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5150) Fail in a thread may not fail a test, clean up log splitting test
[ https://issues.apache.org/jira/browse/HBASE-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5150: --- Attachment: hbase_5150_v3.patch > Fail in a thread may not fail a test, clean up log splitting test > - > > Key: HBASE-5150 > URL: https://issues.apache.org/jira/browse/HBASE-5150 > Project: HBase > Issue Type: Test >Affects Versions: 0.94.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > Attachments: hbase-5150.txt, hbase_5150_v3.patch > > > This is to clean up some tests for HBASE-5081. The Assert.fail method in a > separate thread will terminate the thread, but may not fail the test. > We can use callable, so that we can get the error in getting the result. > Some documentation to explain the test will be helpful too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5150) Fail in a thread may not fail a test, clean up log splitting test
[ https://issues.apache.org/jira/browse/HBASE-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5150: --- Status: Open (was: Patch Available) > Fail in a thread may not fail a test, clean up log splitting test > - > > Key: HBASE-5150 > URL: https://issues.apache.org/jira/browse/HBASE-5150 > Project: HBase > Issue Type: Test >Affects Versions: 0.94.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > Attachments: hbase-5150.txt, hbase_5150_v3.patch > > > This is to clean up some tests for HBASE-5081. The Assert.fail method in a > separate thread will terminate the thread, but may not fail the test. > We can use callable, so that we can get the error in getting the result. > Some documentation to explain the test will be helpful too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5150) Fail in a thread may not fail a test, clean up log splitting test
[ https://issues.apache.org/jira/browse/HBASE-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5150: --- Status: Patch Available (was: Open) Patch diff3. > Fail in a thread may not fail a test, clean up log splitting test > - > > Key: HBASE-5150 > URL: https://issues.apache.org/jira/browse/HBASE-5150 > Project: HBase > Issue Type: Test >Affects Versions: 0.94.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > Attachments: hbase-5150.txt, hbase_5150_v3.patch > > > This is to clean up some tests for HBASE-5081. The Assert.fail method in a > separate thread will terminate the thread, but may not fail the test. > We can use callable, so that we can get the error in getting the result. > Some documentation to explain the test will be helpful too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5150) Fail in a thread may not fail a test, clean up log splitting test
[ https://issues.apache.org/jira/browse/HBASE-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5150: --- Status: Patch Available (was: Open) > Fail in a thread may not fail a test, clean up log splitting test > - > > Key: HBASE-5150 > URL: https://issues.apache.org/jira/browse/HBASE-5150 > Project: HBase > Issue Type: Test >Affects Versions: 0.94.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > Attachments: hbase-5150.txt > > > This is to clean up some tests for HBASE-5081. The Assert.fail method in a > separate thread will terminate the thread, but may not fail the test. > We can use callable, so that we can get the error in getting the result. > Some documentation to explain the test will be helpful too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5150) Fail in a thread may not fail a test, clean up log splitting test
[ https://issues.apache.org/jira/browse/HBASE-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5150: --- Attachment: hbase-5150.txt > Fail in a thread may not fail a test, clean up log splitting test > - > > Key: HBASE-5150 > URL: https://issues.apache.org/jira/browse/HBASE-5150 > Project: HBase > Issue Type: Test >Affects Versions: 0.94.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > Attachments: hbase-5150.txt > > > This is to clean up some tests for HBASE-5081. The Assert.fail method in a > separate thread will terminate the thread, but may not fail the test. > We can use callable, so that we can get the error in getting the result. > Some documentation to explain the test will be helpful too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5081) Distributed log splitting deleteNode races against splitLog retry
[ https://issues.apache.org/jira/browse/HBASE-5081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-5081: --- Attachment: distributed_log_splitting_screenshot3.png After restart, it still doesn't work. See the attached 3rd screen shot. Probably we should commit this one and open a new Jira. @Stack, to reproduce it, you can set these properties and run bigtop TestLoadAndVerify: hbase.hregion.max.filesize 1048576 hbase.master.distributed.log.splitting true io.file.buffer.size 131072 Hadoop setting hbase.balancer.period 2000 Period at which the region balancer runs in the Master. hbase.hregion.memstore.flush.size 262144 > Distributed log splitting deleteNode races against splitLog retry > -- > > Key: HBASE-5081 > URL: https://issues.apache.org/jira/browse/HBASE-5081 > Project: HBase > Issue Type: Bug > Components: wal >Affects Versions: 0.92.0, 0.94.0 >Reporter: Jimmy Xiang >Assignee: Prakash Khemani > Fix For: 0.92.0 > > Attachments: > 0001-HBASE-5081-jira-Distributed-log-splitting-deleteNode.patch, > 0001-HBASE-5081-jira-Distributed-log-splitting-deleteNode.patch, > 0001-HBASE-5081-jira-Distributed-log-splitting-deleteNode.patch, > 0001-HBASE-5081-jira-Distributed-log-splitting-deleteNode.patch, > 0001-HBASE-5081-jira-Distributed-log-splitting-deleteNode.patch, > 0001-HBASE-5081-jira-Distributed-log-splitting-deleteNode.patch, > 0001-HBASE-5081-jira-Distributed-log-splitting-deleteNode.patch, > 5081-deleteNode-with-while-loop.txt, > HBASE-5081-jira-Distributed-log-splitting-deleteNode.patch, > distributed-log-splitting-screenshot.png, > distributed_log_splitting_screen_shot2.png, > distributed_log_splitting_screenshot3.png, hbase-5081-patch-v6.txt, > hbase-5081-patch-v7.txt, hbase-5081_patch_for_92_v4.txt, > hbase-5081_patch_v5.txt, patch_for_92.txt, patch_for_92_v2.txt, > patch_for_92_v3.txt > > > Recently, during 0.92 rc testing, we found distributed log splitting hangs > there forever. Please see attached screen shot. > I looked into it and here is what happened I think: > 1. One rs died, the servershutdownhandler found it out and started the > distributed log splitting; > 2. All three tasks failed, so the three tasks were deleted, asynchronously; > 3. Servershutdownhandler retried the log splitting; > 4. During the retrial, it created these three tasks again, and put them in a > hashmap (tasks); > 5. The asynchronously deletion in step 2 finally happened for one task, in > the callback, it removed one > task in the hashmap; > 6. One of the newly submitted tasks' zookeeper watcher found out that task is > unassigned, and it is not > in the hashmap, so it created a new orphan task. > 7. All three tasks failed, but that task created in step 6 is an orphan so > the batch.err counter was one short, > so the log splitting hangs there and keeps waiting for the last task to > finish which is never going to happen. > So I think the problem is step 2. The fix is to make deletion sync, instead > of async, so that the retry will have > a clean start. > Async deleteNode will mess up with split log retrial. In extreme situation, > if async deleteNode doesn't happen > soon enough, some node created during the retrial could be deleted. > deleteNode should be sync. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
