[jira] [Updated] (HBASE-22808) HBCK Report showed the offline regions which belong to disabled table
[ https://issues.apache.org/jira/browse/HBASE-22808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22808: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed the addendum patch to branch-2.2. > HBCK Report showed the offline regions which belong to disabled table > - > > Key: HBASE-22808 > URL: https://issues.apache.org/jira/browse/HBASE-22808 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6 > > Attachments: HBASE-22808.branch-2.2.001.patch > > > For disabled table, the regions were offline and the info:server may be an > unknownserver. The HBCK report should not show these regions in UI. Because > these regions no need to fix. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-15666) shaded dependencies for hbase-testing-util
[ https://issues.apache.org/jira/browse/HBASE-15666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-15666: --- Status: Patch Available (was: Reopened) > shaded dependencies for hbase-testing-util > -- > > Key: HBASE-15666 > URL: https://issues.apache.org/jira/browse/HBASE-15666 > Project: HBase > Issue Type: New Feature > Components: test >Affects Versions: 1.2.0, 1.1.0 >Reporter: Sean Busbey >Assignee: Balazs Meszaros >Priority: Critical > Fix For: 3.0.0, 1.5.0, 2.3.0, 2.2.1, 2.1.6, 1.4.11 > > Attachments: HBASE-15666.branch-2.addendum.patch > > > Folks that make use of our shaded client but then want to test things using > the hbase-testing-util end up getting all of our dependencies again in the > test scope. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-15666) shaded dependencies for hbase-testing-util
[ https://issues.apache.org/jira/browse/HBASE-15666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-15666: --- Attachment: HBASE-15666.branch-2.addendum.patch > shaded dependencies for hbase-testing-util > -- > > Key: HBASE-15666 > URL: https://issues.apache.org/jira/browse/HBASE-15666 > Project: HBase > Issue Type: New Feature > Components: test >Affects Versions: 1.1.0, 1.2.0 >Reporter: Sean Busbey >Assignee: Balazs Meszaros >Priority: Critical > Fix For: 3.0.0, 1.5.0, 2.3.0, 2.2.1, 2.1.6, 1.4.11 > > Attachments: HBASE-15666.branch-2.addendum.patch > > > Folks that make use of our shaded client but then want to test things using > the hbase-testing-util end up getting all of our dependencies again in the > test scope. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Reopened] (HBASE-15666) shaded dependencies for hbase-testing-util
[ https://issues.apache.org/jira/browse/HBASE-15666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang reopened HBASE-15666: The patch for branch-2 broken the maven build. Need to change the version from 3.0.0-SNAPSHOT to 2.3.0-SNAPSHOT. > shaded dependencies for hbase-testing-util > -- > > Key: HBASE-15666 > URL: https://issues.apache.org/jira/browse/HBASE-15666 > Project: HBase > Issue Type: New Feature > Components: test >Affects Versions: 1.1.0, 1.2.0 >Reporter: Sean Busbey >Assignee: Balazs Meszaros >Priority: Critical > Fix For: 3.0.0, 1.5.0, 2.3.0, 2.2.1, 2.1.6, 1.4.11 > > > Folks that make use of our shaded client but then want to test things using > the hbase-testing-util end up getting all of our dependencies again in the > test scope. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Comment Edited] (HBASE-22738) Fallback to default group to choose RS when there are no RS in current group
[ https://issues.apache.org/jira/browse/HBASE-22738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16902965#comment-16902965 ] Guanghao Zhang edited comment on HBASE-22738 at 8/8/19 1:21 PM: In my option, rs group feature is enabled as default in future. So there will have a overall cluster balancer to fix the wrong assigns and this cannot be disabled by user. User only config the balancer for rsgroup inside and enable or disable it. And availability is more important than the correctness of regions location. So if no regionservers in group, fallback to default rsgroup. If no regionservers in default rsgroup, fallback to any rsgroup which have online regionservers. Maybe sort them by regionserver number or load. was (Author: zghaobac): In my option, rs group feature is enabled as default in future. So there will have a overall cluster balancer to fix the wrong assigns. And availability is more important than the correctness of regions location. So if no regionservers in group, fallback to default rsgroup. If no regionservers in default rsgroup, fallback to any rsgroup which have online regionservers. Maybe sort them by regionserver number or load. > Fallback to default group to choose RS when there are no RS in current group > > > Key: HBASE-22738 > URL: https://issues.apache.org/jira/browse/HBASE-22738 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Priority: Major > > We configure one regionserver for hbase system table. But when rolling > upgrade, you need move the region to other regionservers. But because there > are no other regionservers in this group, you cannot move the region... > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22738) Fallback to default group to choose RS when there are no RS in current group
[ https://issues.apache.org/jira/browse/HBASE-22738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16902965#comment-16902965 ] Guanghao Zhang commented on HBASE-22738: In my option, rs group feature is enabled as default in future. So there will have a overall cluster balancer to fix the wrong assigns. And availability is more important than the correctness of regions location. So if no regionservers in group, fallback to default rsgroup. If no regionservers in default rsgroup, fallback to any rsgroup which have online regionservers. Maybe sort them by regionserver number or load. > Fallback to default group to choose RS when there are no RS in current group > > > Key: HBASE-22738 > URL: https://issues.apache.org/jira/browse/HBASE-22738 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Priority: Major > > We configure one regionserver for hbase system table. But when rolling > upgrade, you need move the region to other regionservers. But because there > are no other regionservers in this group, you cannot move the region... > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22738) Fallback to default group to choose RS when there are no RS in current group
[ https://issues.apache.org/jira/browse/HBASE-22738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16902957#comment-16902957 ] Guanghao Zhang commented on HBASE-22738: [~HB-CY] Can you share KuaiShou's idea here? > Fallback to default group to choose RS when there are no RS in current group > > > Key: HBASE-22738 > URL: https://issues.apache.org/jira/browse/HBASE-22738 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Priority: Major > > We configure one regionserver for hbase system table. But when rolling > upgrade, you need move the region to other regionservers. But because there > are no other regionservers in this group, you cannot move the region... > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22808) HBCK Report showed the offline regions which belong to disabled table
[ https://issues.apache.org/jira/browse/HBASE-22808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16902856#comment-16902856 ] Guanghao Zhang commented on HBASE-22808: branch-2.2 missed createRegionDir method and broken the ut. > HBCK Report showed the offline regions which belong to disabled table > - > > Key: HBASE-22808 > URL: https://issues.apache.org/jira/browse/HBASE-22808 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6 > > Attachments: HBASE-22808.branch-2.2.001.patch > > > For disabled table, the regions were offline and the info:server may be an > unknownserver. The HBCK report should not show these regions in UI. Because > these regions no need to fix. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22808) HBCK Report showed the offline regions which belong to disabled table
[ https://issues.apache.org/jira/browse/HBASE-22808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22808: --- Status: Patch Available (was: Reopened) > HBCK Report showed the offline regions which belong to disabled table > - > > Key: HBASE-22808 > URL: https://issues.apache.org/jira/browse/HBASE-22808 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6 > > Attachments: HBASE-22808.branch-2.2.001.patch > > > For disabled table, the regions were offline and the info:server may be an > unknownserver. The HBCK report should not show these regions in UI. Because > these regions no need to fix. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Reopened] (HBASE-22808) HBCK Report showed the offline regions which belong to disabled table
[ https://issues.apache.org/jira/browse/HBASE-22808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang reopened HBASE-22808: Attached a addendum patch for branch-2.2. > HBCK Report showed the offline regions which belong to disabled table > - > > Key: HBASE-22808 > URL: https://issues.apache.org/jira/browse/HBASE-22808 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6 > > Attachments: HBASE-22808.branch-2.2.001.patch > > > For disabled table, the regions were offline and the info:server may be an > unknownserver. The HBCK report should not show these regions in UI. Because > these regions no need to fix. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22808) HBCK Report showed the offline regions which belong to disabled table
[ https://issues.apache.org/jira/browse/HBASE-22808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22808: --- Attachment: HBASE-22808.branch-2.2.001.patch > HBCK Report showed the offline regions which belong to disabled table > - > > Key: HBASE-22808 > URL: https://issues.apache.org/jira/browse/HBASE-22808 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6 > > Attachments: HBASE-22808.branch-2.2.001.patch > > > For disabled table, the regions were offline and the info:server may be an > unknownserver. The HBCK report should not show these regions in UI. Because > these regions no need to fix. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (HBASE-22808) HBCK Report showed the offline regions which belong to disabled table
[ https://issues.apache.org/jira/browse/HBASE-22808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang resolved HBASE-22808. Resolution: Fixed Fix Version/s: 2.1.6 2.2.1 2.0.6 2.3.0 3.0.0 Pushed to branch-2.0+. Thanks [~stack] for reviewing. > HBCK Report showed the offline regions which belong to disabled table > - > > Key: HBASE-22808 > URL: https://issues.apache.org/jira/browse/HBASE-22808 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6 > > > For disabled table, the regions were offline and the info:server may be an > unknownserver. The HBCK report should not show these regions in UI. Because > these regions no need to fix. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22808) HBCK Report showed the offline regions which belong to disabled table
[ https://issues.apache.org/jira/browse/HBASE-22808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16902610#comment-16902610 ] Guanghao Zhang commented on HBASE-22808: The unknown servers had same problem, too. [~stack] Please review the pull request. Thanks. > HBCK Report showed the offline regions which belong to disabled table > - > > Key: HBASE-22808 > URL: https://issues.apache.org/jira/browse/HBASE-22808 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > > For disabled table, the regions were offline and the info:server may be an > unknownserver. The HBCK report should not show these regions in UI. Because > these regions no need to fix. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (HBASE-22807) HBCK Report showed wrong orphans regions on FileSystem
[ https://issues.apache.org/jira/browse/HBASE-22807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang resolved HBASE-22807. Resolution: Fixed Fix Version/s: 2.1.6 2.2.1 2.0.6 2.3.0 3.0.0 Pushed to branch-2.0+. Thanks [~jatsakthi] for reviewing. > HBCK Report showed wrong orphans regions on FileSystem > -- > > Key: HBASE-22807 > URL: https://issues.apache.org/jira/browse/HBASE-22807 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6 > > > It showed .tabledesc and .tmp as orphans regions. Need to use > FSUtils.getRegionDirs(fs, tableDir) instead of > fs.listStatus(tableDir.getPath()). -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22807) HBCK Report showed wrong orphans regions on FileSystem
[ https://issues.apache.org/jira/browse/HBASE-22807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22807: --- Description: It showed .tabledesc and .tmp as orphans regions. Need to use FSUtils.getRegionDirs(fs, tableDir) instead of fs.listStatus(tableDir.getPath()). > HBCK Report showed wrong orphans regions on FileSystem > -- > > Key: HBASE-22807 > URL: https://issues.apache.org/jira/browse/HBASE-22807 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > > It showed .tabledesc and .tmp as orphans regions. Need to use > FSUtils.getRegionDirs(fs, tableDir) instead of > fs.listStatus(tableDir.getPath()). -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22808) HBCK Report showed the offline regions which belong to disabled table
[ https://issues.apache.org/jira/browse/HBASE-22808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16901756#comment-16901756 ] Guanghao Zhang commented on HBASE-22808: [~stack] Feel free to take it sir. :-) > HBCK Report showed the offline regions which belong to disabled table > - > > Key: HBASE-22808 > URL: https://issues.apache.org/jira/browse/HBASE-22808 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Priority: Major > > For disabled table, the regions were offline and the info:server may be an > unknownserver. The HBCK report should not show these regions in UI. Because > these regions no need to fix. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (HBASE-22808) HBCK Report showed the offline regions which belong to disabled table
Guanghao Zhang created HBASE-22808: -- Summary: HBCK Report showed the offline regions which belong to disabled table Key: HBASE-22808 URL: https://issues.apache.org/jira/browse/HBASE-22808 Project: HBase Issue Type: Sub-task Reporter: Guanghao Zhang For disabled table, the regions were offline and the info:server may be an unknownserver. The HBCK report should not show these regions in UI. Because these regions no need to fix. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (HBASE-22807) HBCK Report showed wrong orphans regions on FileSystem
Guanghao Zhang created HBASE-22807: -- Summary: HBCK Report showed wrong orphans regions on FileSystem Key: HBASE-22807 URL: https://issues.apache.org/jira/browse/HBASE-22807 Project: HBase Issue Type: Sub-task Reporter: Guanghao Zhang Assignee: Guanghao Zhang -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22709) Add a chore thread in master to do hbck checking and display results in 'HBCK Report' page
[ https://issues.apache.org/jira/browse/HBASE-22709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900510#comment-16900510 ] Guanghao Zhang commented on HBASE-22709: bq. If yes, I can file the Jira & work on it. +1 to add a config to trun it off. > Add a chore thread in master to do hbck checking and display results in 'HBCK > Report' page > -- > > Key: HBASE-22709 > URL: https://issues.apache.org/jira/browse/HBASE-22709 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6 > > Attachments: HBASE-22709.master.001.patch > > > See HBASE-21965. There may have two type of failed splited/merged regions. > One is orphan region on filesystem. Another one is unassigned daughter > regions or merged regions. Plan to add a seperate hbck.jsp for them. Will add > more hbck problems to this UI in future. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22741) Show catalogjanitor consistency complaints in new 'HBCK Report' page
[ https://issues.apache.org/jira/browse/HBASE-22741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16899832#comment-16899832 ] Guanghao Zhang commented on HBASE-22741: Pushed to branch-2.2. > Show catalogjanitor consistency complaints in new 'HBCK Report' page > > > Key: HBASE-22741 > URL: https://issues.apache.org/jira/browse/HBASE-22741 > Project: HBase > Issue Type: Sub-task > Components: hbck2, UI >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6 > > Attachments: > 0001-HBASE-22741-Show-catalogjanitor-consistency-complain.patch, > HBASE-22741.master.001.patch, HBASE-22741.master.002.patch, Screen Shot > 2019-07-25 at 11.12.40 PM.png, Screen Shot 2019-07-30 at 11.29.09 AM.png > > > HBASE-22723 makes it so catalogjanitor looks for holes and overlaps when it > scans hbase:meta. HBASE-22709 added a new HBCK Report page to the master in > which it notes findings its figured looking at regionserver reports and > current state of Master. > This issue is about exposing the inconsistencies found scanning hbase:meta in > the HBCK Report page. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22741) Show catalogjanitor consistency complaints in new 'HBCK Report' page
[ https://issues.apache.org/jira/browse/HBASE-22741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16899831#comment-16899831 ] Guanghao Zhang commented on HBASE-22741: [~stack] Seems this forgot to commit to branch-2.2. Let me cherry-pick this. > Show catalogjanitor consistency complaints in new 'HBCK Report' page > > > Key: HBASE-22741 > URL: https://issues.apache.org/jira/browse/HBASE-22741 > Project: HBase > Issue Type: Sub-task > Components: hbck2, UI >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6 > > Attachments: > 0001-HBASE-22741-Show-catalogjanitor-consistency-complain.patch, > HBASE-22741.master.001.patch, HBASE-22741.master.002.patch, Screen Shot > 2019-07-25 at 11.12.40 PM.png, Screen Shot 2019-07-30 at 11.29.09 AM.png > > > HBASE-22723 makes it so catalogjanitor looks for holes and overlaps when it > scans hbase:meta. HBASE-22709 added a new HBCK Report page to the master in > which it notes findings its figured looking at regionserver reports and > current state of Master. > This issue is about exposing the inconsistencies found scanning hbase:meta in > the HBCK Report page. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22767) System table RIT STUCK if their RSGroup has no highest version RSes
[ https://issues.apache.org/jira/browse/HBASE-22767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16898054#comment-16898054 ] Guanghao Zhang commented on HBASE-22767: I thought the better fix should fallback to default group to find a RS... No need to add a BOGUS_SERVER_NAME and no need to fix these special cases. > System table RIT STUCK if their RSGroup has no highest version RSes > --- > > Key: HBASE-22767 > URL: https://issues.apache.org/jira/browse/HBASE-22767 > Project: HBase > Issue Type: Bug > Components: rsgroup >Reporter: Xiaolin Ha >Assignee: Xiaolin Ha >Priority: Major > > AM chooses highest version region servers as participants for system tables, > including META table. If system table group has no highest version region > servers, then the reassignment of their regions will be always the BOGUS > server defined in RSGroup. > In our test environment using branch-2.2, we isolate system tables in a > rsgroup containing only one server. And when upgrading RSs, we have met the > problem that META is always assigned to the BOGUS server while the group > server has already been online for a while. META RIT is stuck and can not be > recovered by hbck2. > I made a UT reproduce this problem, steps are: > 1. add a group, move 1 server to it; > 2. move meta table to the group; > 3. restart the group server and downgrade its version; > 4. meta rit stuck. > > ROOT cause is AM filters highest version RSs for system tables. So if we do > not change the versions of system table group servers, but upgrade the > versions of other group servers, then if there is reassignment for any system > tables, such as balancer moving their regions, RIT STUCK!! > > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22737) Add a new admin method and shell cmd to trigger the hbck chore to run
[
https://issues.apache.org/jira/browse/HBASE-22737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang updated HBASE-22737:
---
Release Note: Add a new method runHbckChore in Hbck interface and a new
shell cmd hbck_chore_run to request HBCK chore to run at master side.
> Add a new admin method and shell cmd to trigger the hbck chore to run
> -
>
> Key: HBASE-22737
> URL: https://issues.apache.org/jira/browse/HBASE-22737
> Project: HBase
> Issue Type: Sub-task
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6
>
>
> A follow-on issue after HBASE-22709.
> {quote}Oh, also as a follow-on, should make it so user can trigger this chore
> to run... or perhaps a new shell command which is called hbck_report that
> runs this chore and the catalogjanitor, etc., to produce all hbck.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (HBASE-22737) Add a new admin method and shell cmd to trigger the hbck chore to run
[
https://issues.apache.org/jira/browse/HBASE-22737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang resolved HBASE-22737.
Resolution: Fixed
Fix Version/s: 2.1.6
2.2.1
2.0.6
2.3.0
3.0.0
Pushed to branch-2.0+. Thanks [~stack] for reviewing.
> Add a new admin method and shell cmd to trigger the hbck chore to run
> -
>
> Key: HBASE-22737
> URL: https://issues.apache.org/jira/browse/HBASE-22737
> Project: HBase
> Issue Type: Sub-task
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6
>
>
> A follow-on issue after HBASE-22709.
> {quote}Oh, also as a follow-on, should make it so user can trigger this chore
> to run... or perhaps a new shell command which is called hbck_report that
> runs this chore and the catalogjanitor, etc., to produce all hbck.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (HBASE-22727) The canary table should be placed on all regionservers
[ https://issues.apache.org/jira/browse/HBASE-22727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22727: --- Issue Type: Improvement (was: Sub-task) Parent: (was: HBASE-22514) > The canary table should be placed on all regionservers > -- > > Key: HBASE-22727 > URL: https://issues.apache.org/jira/browse/HBASE-22727 > Project: HBase > Issue Type: Improvement >Reporter: Duo Zhang >Assignee: chenyang >Priority: Major > > Not within a single rs group. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (HBASE-22727) The canary table should be placed on all regionservers
[ https://issues.apache.org/jira/browse/HBASE-22727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang reassigned HBASE-22727: -- Assignee: chenyang > The canary table should be placed on all regionservers > -- > > Key: HBASE-22727 > URL: https://issues.apache.org/jira/browse/HBASE-22727 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Assignee: chenyang >Priority: Major > > Not within a single rs group. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22737) Add a new admin method and shell cmd to trigger the hbck chore to run
[
https://issues.apache.org/jira/browse/HBASE-22737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16896680#comment-16896680
]
Guanghao Zhang commented on HBASE-22737:
Ping [~stack] for reviewing.
> Add a new admin method and shell cmd to trigger the hbck chore to run
> -
>
> Key: HBASE-22737
> URL: https://issues.apache.org/jira/browse/HBASE-22737
> Project: HBase
> Issue Type: Sub-task
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Major
>
> A follow-on issue after HBASE-22709.
> {quote}Oh, also as a follow-on, should make it so user can trigger this chore
> to run... or perhaps a new shell command which is called hbck_report that
> runs this chore and the catalogjanitor, etc., to produce all hbck.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (HBASE-22709) Add a chore thread in master to do hbck checking and display results in 'HBCK Report' page
[ https://issues.apache.org/jira/browse/HBASE-22709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22709: --- Release Note: 1. Add a new chore thread in master to do hbck checking 2. Add a new web ui "HBCK Report" page to display checking results. This feature is enabled by default. And the hbck chore run per 60 minutes by default. You can config "hbase.master.hbck.checker.interval" to change the period. Notice: the config "hbase.master.hbck.checker.interval" was renamed to "hbase.master.hbck.chore.interval" in HBASE-22737. was: 1. Add a new chore thread in master to do hbck checking 2. Add a new web ui "HBCK Report" page to display checking results. This feature is enabled by default. And the hbck chore run per 60 minutes by default. You can config "hbase.master.hbck.checker.interval" to change the period. > Add a chore thread in master to do hbck checking and display results in 'HBCK > Report' page > -- > > Key: HBASE-22709 > URL: https://issues.apache.org/jira/browse/HBASE-22709 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6 > > Attachments: HBASE-22709.master.001.patch > > > See HBASE-21965. There may have two type of failed splited/merged regions. > One is orphan region on filesystem. Another one is unassigned daughter > regions or merged regions. Plan to add a seperate hbck.jsp for them. Will add > more hbck problems to this UI in future. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (HBASE-22737) Add a new admin method and shell cmd to trigger the hbck chore to run
[
https://issues.apache.org/jira/browse/HBASE-22737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang reassigned HBASE-22737:
--
Assignee: Guanghao Zhang
> Add a new admin method and shell cmd to trigger the hbck chore to run
> -
>
> Key: HBASE-22737
> URL: https://issues.apache.org/jira/browse/HBASE-22737
> Project: HBase
> Issue Type: Sub-task
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Major
>
> A follow-on issue after HBASE-22709.
> {quote}Oh, also as a follow-on, should make it so user can trigger this chore
> to run... or perhaps a new shell command which is called hbck_report that
> runs this chore and the catalogjanitor, etc., to produce all hbck.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (HBASE-22737) Add a new admin method and shell cmd to trigger the hbck chore to run
[
https://issues.apache.org/jira/browse/HBASE-22737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang updated HBASE-22737:
---
Summary: Add a new admin method and shell cmd to trigger the hbck chore to
run (was: Add a new shell cmd to trigger the hbck checker to run)
> Add a new admin method and shell cmd to trigger the hbck chore to run
> -
>
> Key: HBASE-22737
> URL: https://issues.apache.org/jira/browse/HBASE-22737
> Project: HBase
> Issue Type: Sub-task
>Reporter: Guanghao Zhang
>Priority: Major
>
> A follow-on issue after HBASE-22709.
> {quote}Oh, also as a follow-on, should make it so user can trigger this chore
> to run... or perhaps a new shell command which is called hbck_report that
> runs this chore and the catalogjanitor, etc., to produce all hbck.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (HBASE-22709) Add a chore thread in master to do hbck checking and display results in 'HBCK Report' page
[ https://issues.apache.org/jira/browse/HBASE-22709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22709: --- Release Note: 1. Add a new chore thread in master to do hbck checking 2. Add a new web ui "HBCK Report" page to display checking results. This feature is enabled by default. And the hbck chore run per 60 minutes by default. You can config "hbase.master.hbck.checker.interval" to change the period. was: 1. Add a new chore thread in master to do hbck checking 2. Add a new web ui "HBCK Report" page to display checking results. This feature is enabled by default. And the hbck checker run per 60 minutes by default. You can config "hbase.master.hbck.checker.interval" to change the period. > Add a chore thread in master to do hbck checking and display results in 'HBCK > Report' page > -- > > Key: HBASE-22709 > URL: https://issues.apache.org/jira/browse/HBASE-22709 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6 > > Attachments: HBASE-22709.master.001.patch > > > See HBASE-21965. There may have two type of failed splited/merged regions. > One is orphan region on filesystem. Another one is unassigned daughter > regions or merged regions. Plan to add a seperate hbck.jsp for them. Will add > more hbck problems to this UI in future. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22709) Add a chore thread in master to do hbck checking and display results in 'HBCK Report' page
[ https://issues.apache.org/jira/browse/HBASE-22709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16894985#comment-16894985 ] Guanghao Zhang commented on HBASE-22709: bq. Pls explain those also, if there, in the RN. Will be very helpful in future. RN updated. > Add a chore thread in master to do hbck checking and display results in 'HBCK > Report' page > -- > > Key: HBASE-22709 > URL: https://issues.apache.org/jira/browse/HBASE-22709 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6 > > Attachments: HBASE-22709.master.001.patch > > > See HBASE-21965. There may have two type of failed splited/merged regions. > One is orphan region on filesystem. Another one is unassigned daughter > regions or merged regions. Plan to add a seperate hbck.jsp for them. Will add > more hbck problems to this UI in future. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22709) Add a chore thread in master to do hbck checking and display results in 'HBCK Report' page
[ https://issues.apache.org/jira/browse/HBASE-22709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22709: --- Release Note: 1. Add a new chore thread in master to do hbck checking 2. Add a new web ui "HBCK Report" page to display checking results. This feature is enabled by default. And the hbck checker run per 60 minutes by default. You can config "hbase.master.hbck.checker.interval" to change the period. was: 1. Add a new chore thread in master to do hbck checking 2. Add a new web ui "HBCK Report" page to display checking results. > Add a chore thread in master to do hbck checking and display results in 'HBCK > Report' page > -- > > Key: HBASE-22709 > URL: https://issues.apache.org/jira/browse/HBASE-22709 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6 > > Attachments: HBASE-22709.master.001.patch > > > See HBASE-21965. There may have two type of failed splited/merged regions. > One is orphan region on filesystem. Another one is unassigned daughter > regions or merged regions. Plan to add a seperate hbck.jsp for them. Will add > more hbck problems to this UI in future. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22709) Add a chore thread in master to do hbck checking and display results in 'HBCK Report' page
[ https://issues.apache.org/jira/browse/HBASE-22709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22709: --- Release Note: 1. Add a new chore thread in master to do hbck checking 2. Add a new web ui "HBCK Report" page to display checking results. > Add a chore thread in master to do hbck checking and display results in 'HBCK > Report' page > -- > > Key: HBASE-22709 > URL: https://issues.apache.org/jira/browse/HBASE-22709 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6 > > Attachments: HBASE-22709.master.001.patch > > > See HBASE-21965. There may have two type of failed splited/merged regions. > One is orphan region on filesystem. Another one is unassigned daughter > regions or merged regions. Plan to add a seperate hbck.jsp for them. Will add > more hbck problems to this UI in future. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22709) Add a chore thread in master to do hbck checking and display results in 'HBCK Report' page
[ https://issues.apache.org/jira/browse/HBASE-22709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22709: --- Resolution: Fixed Fix Version/s: 2.1.6 2.2.1 2.0.6 2.3.0 3.0.0 Status: Resolved (was: Patch Available) Pushed to branch-2.0+. Thanks [~stack] for reviewing. > Add a chore thread in master to do hbck checking and display results in 'HBCK > Report' page > -- > > Key: HBASE-22709 > URL: https://issues.apache.org/jira/browse/HBASE-22709 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6 > > Attachments: HBASE-22709.master.001.patch > > > See HBASE-21965. There may have two type of failed splited/merged regions. > One is orphan region on filesystem. Another one is unassigned daughter > regions or merged regions. Plan to add a seperate hbck.jsp for them. Will add > more hbck problems to this UI in future. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (HBASE-22742) [HBCK2] Add more log for hbck operations at master side
[ https://issues.apache.org/jira/browse/HBASE-22742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang resolved HBASE-22742. Resolution: Fixed Fix Version/s: 2.1.6 2.2.1 2.0.6 2.3.0 3.0.0 Pushed to branch-2.0+. > [HBCK2] Add more log for hbck operations at master side > --- > > Key: HBASE-22742 > URL: https://issues.apache.org/jira/browse/HBASE-22742 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Minor > Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (HBASE-22742) [HBCK2] Add more log for hbck operations at master side
[ https://issues.apache.org/jira/browse/HBASE-22742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang reassigned HBASE-22742: -- Assignee: Guanghao Zhang > [HBCK2] Add more log for hbck operations at master side > --- > > Key: HBASE-22742 > URL: https://issues.apache.org/jira/browse/HBASE-22742 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (HBASE-22742) [HBCK2] Add more log for hbck operations at master side
Guanghao Zhang created HBASE-22742: -- Summary: [HBCK2] Add more log for hbck operations at master side Key: HBASE-22742 URL: https://issues.apache.org/jira/browse/HBASE-22742 Project: HBase Issue Type: Sub-task Reporter: Guanghao Zhang -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22738) Fallback to default group to choose RS when there are no RS in current group
[ https://issues.apache.org/jira/browse/HBASE-22738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22738: --- Summary: Fallback to default group to choose RS when there are no RS in current group (was: Fallback to other group to choose RS when there are no RS in current group) > Fallback to default group to choose RS when there are no RS in current group > > > Key: HBASE-22738 > URL: https://issues.apache.org/jira/browse/HBASE-22738 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Priority: Major > > We configure one regionserver for hbase system table. But when rolling > upgrade, you need move the region to other regionservers. But because there > are no other regionservers in this group, you cannot move the region... > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (HBASE-22738) Fallback to other group to choose RS when there are no RS in current group
Guanghao Zhang created HBASE-22738: -- Summary: Fallback to other group to choose RS when there are no RS in current group Key: HBASE-22738 URL: https://issues.apache.org/jira/browse/HBASE-22738 Project: HBase Issue Type: Bug Reporter: Guanghao Zhang We configure one regionserver for hbase system table. But when rolling upgrade, you need move the region to other regionservers. But because there are no other regionservers in this group, you cannot move the region... -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (HBASE-22736) Add text to show how to fix the HBCK checking result
Guanghao Zhang created HBASE-22736: -- Summary: Add text to show how to fix the HBCK checking result Key: HBASE-22736 URL: https://issues.apache.org/jira/browse/HBASE-22736 Project: HBase Issue Type: Sub-task Reporter: Guanghao Zhang A follow-on issue after HBASE-22709. Copied the comment here. bq. In follow-on, we can add text on how to fix including commands. Also may want a json version of this page. Lets see. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (HBASE-22737) Add a new shell cmd to trigger the hbck checker to run
Guanghao Zhang created HBASE-22737:
--
Summary: Add a new shell cmd to trigger the hbck checker to run
Key: HBASE-22737
URL: https://issues.apache.org/jira/browse/HBASE-22737
Project: HBase
Issue Type: Sub-task
Reporter: Guanghao Zhang
A follow-on issue after HBASE-22709.
{quote}Oh, also as a follow-on, should make it so user can trigger this chore
to run... or perhaps a new shell command which is called hbck_report that runs
this chore and the catalogjanitor, etc., to produce all hbck.
{quote}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (HBASE-22709) Add a chore thread in master to do hbck checking
[ https://issues.apache.org/jira/browse/HBASE-22709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892871#comment-16892871 ] Guanghao Zhang commented on HBASE-22709: Ping [~stack] for reviewing. > Add a chore thread in master to do hbck checking > > > Key: HBASE-22709 > URL: https://issues.apache.org/jira/browse/HBASE-22709 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22709.master.001.patch > > > See HBASE-21965. There may have two type of failed splited/merged regions. > One is orphan region on filesystem. Another one is unassigned daughter > regions or merged regions. Plan to add a seperate hbck.jsp for them. Will add > more hbck problems to this UI in future. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (HBASE-21747) Release 2.2.0
[ https://issues.apache.org/jira/browse/HBASE-21747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang resolved HBASE-21747. Resolution: Fixed > Release 2.2.0 > - > > Key: HBASE-21747 > URL: https://issues.apache.org/jira/browse/HBASE-21747 > Project: HBase > Issue Type: Umbrella >Reporter: Duo Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 2.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-21747) Release 2.2.0
[ https://issues.apache.org/jira/browse/HBASE-21747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892319#comment-16892319 ] Guanghao Zhang commented on HBASE-21747: Pushed tag rel/2.2.0. > Release 2.2.0 > - > > Key: HBASE-21747 > URL: https://issues.apache.org/jira/browse/HBASE-21747 > Project: HBase > Issue Type: Umbrella >Reporter: Duo Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 2.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22721) Refactor HBaseFsck: move the inner class out
[ https://issues.apache.org/jira/browse/HBASE-22721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22721: --- Resolution: Fixed Fix Version/s: 2.1.6 2.2.1 2.0.6 2.3.0 3.0.0 Status: Resolved (was: Patch Available) > Refactor HBaseFsck: move the inner class out > > > Key: HBASE-22721 > URL: https://issues.apache.org/jira/browse/HBASE-22721 > Project: HBase > Issue Type: Improvement >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6 > > Attachments: HBASE-22721.branch-2.001.patch > > > HBaseFsck.java has too many code. And HBASE-22709 will use some inner of > HBaseFsck. So plan to refactor it. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22721) Refactor HBaseFsck: move the inner class out
[ https://issues.apache.org/jira/browse/HBASE-22721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892315#comment-16892315 ] Guanghao Zhang commented on HBASE-22721: Cherry-picked to branch-2.0+. Thanks [~stack] for reviewing. > Refactor HBaseFsck: move the inner class out > > > Key: HBASE-22721 > URL: https://issues.apache.org/jira/browse/HBASE-22721 > Project: HBase > Issue Type: Improvement >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22721.branch-2.001.patch > > > HBaseFsck.java has too many code. And HBASE-22709 will use some inner of > HBaseFsck. So plan to refactor it. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22721) Refactor HBaseFsck: move the inner class out
[ https://issues.apache.org/jira/browse/HBASE-22721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892295#comment-16892295 ] Guanghao Zhang commented on HBASE-22721: The method length checkstyle is not easy to fix... > Refactor HBaseFsck: move the inner class out > > > Key: HBASE-22721 > URL: https://issues.apache.org/jira/browse/HBASE-22721 > Project: HBase > Issue Type: Improvement >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22721.branch-2.001.patch > > > HBaseFsck.java has too many code. And HBASE-22709 will use some inner of > HBaseFsck. So plan to refactor it. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (HBASE-22729) Start RSGroupInfoManager as default
Guanghao Zhang created HBASE-22729: -- Summary: Start RSGroupInfoManager as default Key: HBASE-22729 URL: https://issues.apache.org/jira/browse/HBASE-22729 Project: HBase Issue Type: Sub-task Reporter: Guanghao Zhang Start RSGroupInfoManager as default. If no rsgroup information, all RegionServers belong to default group. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22709) Add a chore thread in master to do hbck checking
[ https://issues.apache.org/jira/browse/HBASE-22709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891536#comment-16891536 ] Guanghao Zhang commented on HBASE-22709: bq. But I think this maybe a bit dangerous? If the balancer is still running, we may introduce more inconsistencies if we do this automatically... Yes, the check result is not absolutely right. The "fix" thing shoule be better done by user manually. And for the inconsistent regions, current HBCK2 is enough to fix them. Case1. Master thought this region opened, but no regionserver reported it. > Fix: Use assign cmd. Case2. Master thought this region opened on Server1, but regionserver reported Server2. > Fix: need to check the server is still exist. If not, schedule SCP for it. If exist, restart Server2 and Server1. Case3. More than one regionservers reported opened this region > Fix: restart the regionservers. > Add a chore thread in master to do hbck checking > > > Key: HBASE-22709 > URL: https://issues.apache.org/jira/browse/HBASE-22709 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22709.master.001.patch > > > See HBASE-21965. There may have two type of failed splited/merged regions. > One is orphan region on filesystem. Another one is unassigned daughter > regions or merged regions. Plan to add a seperate hbck.jsp for them. Will add > more hbck problems to this UI in future. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22514) Move rsgroup feature into core of HBase
[ https://issues.apache.org/jira/browse/HBASE-22514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891529#comment-16891529 ] Guanghao Zhang commented on HBASE-22514: Another problem need to fix is the canary table's region should be served by all RSGroup. Open a sub-task here? > Move rsgroup feature into core of HBase > --- > > Key: HBASE-22514 > URL: https://issues.apache.org/jira/browse/HBASE-22514 > Project: HBase > Issue Type: Umbrella > Components: Admin, Client, rsgroup >Reporter: Yechao Chen >Assignee: Duo Zhang >Priority: Major > Attachments: HBASE-22514.master.001.patch, > image-2019-05-31-18-25-38-217.png > > > The class RSGroupAdminClient is not public > we need to use java api RSGroupAdminClient to manager RSG > so RSGroupAdminClient should be public > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22709) Add a chore thread in master to do hbck checking
[ https://issues.apache.org/jira/browse/HBASE-22709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891522#comment-16891522 ] Guanghao Zhang commented on HBASE-22709: bq. We maybe should make it so HBCK2 can ask the Master for list of orphans (JSON listing?) This can be done in UI? a link to get the JSON listing. I thought no need to add a API for this... > Add a chore thread in master to do hbck checking > > > Key: HBASE-22709 > URL: https://issues.apache.org/jira/browse/HBASE-22709 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22709.master.001.patch > > > See HBASE-21965. There may have two type of failed splited/merged regions. > One is orphan region on filesystem. Another one is unassigned daughter > regions or merged regions. Plan to add a seperate hbck.jsp for them. Will add > more hbck problems to this UI in future. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22709) Add a chore thread in master to do hbck checking
[ https://issues.apache.org/jira/browse/HBASE-22709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891506#comment-16891506 ] Guanghao Zhang commented on HBASE-22709: bq. Will this overload master? We have already put lots of functions into master... It only need to list the hdfs directory. And no need to scan meta. And the rsReports is in-memory. For the region hole or overlap problem, it will be done in CatalogJanitor. It already scan meta now. I thought it is fine to add more checking thing in CatalogJanitor. > Add a chore thread in master to do hbck checking > > > Key: HBASE-22709 > URL: https://issues.apache.org/jira/browse/HBASE-22709 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22709.master.001.patch > > > See HBASE-21965. There may have two type of failed splited/merged regions. > One is orphan region on filesystem. Another one is unassigned daughter > regions or merged regions. Plan to add a seperate hbck.jsp for them. Will add > more hbck problems to this UI in future. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22721) Refactor HBaseFsck: move the inner class out
[ https://issues.apache.org/jira/browse/HBASE-22721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891497#comment-16891497 ] Guanghao Zhang commented on HBASE-22721: Pushed to master. Thanks [~stack] for reviewing. Cherry-pick to branch-2 and branch-2.2 have conflicts. Attach the patch here. > Refactor HBaseFsck: move the inner class out > > > Key: HBASE-22721 > URL: https://issues.apache.org/jira/browse/HBASE-22721 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22721.branch-2.001.patch > > > HBaseFsck.java has too many code. And HBASE-22709 will use some inner of > HBaseFsck. So plan to refactor it. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22721) Refactor HBaseFsck: move the inner class out
[ https://issues.apache.org/jira/browse/HBASE-22721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22721: --- Issue Type: Improvement (was: Bug) > Refactor HBaseFsck: move the inner class out > > > Key: HBASE-22721 > URL: https://issues.apache.org/jira/browse/HBASE-22721 > Project: HBase > Issue Type: Improvement >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22721.branch-2.001.patch > > > HBaseFsck.java has too many code. And HBASE-22709 will use some inner of > HBaseFsck. So plan to refactor it. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22721) Refactor HBaseFsck: move the inner class out
[ https://issues.apache.org/jira/browse/HBASE-22721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22721: --- Status: Patch Available (was: Open) > Refactor HBaseFsck: move the inner class out > > > Key: HBASE-22721 > URL: https://issues.apache.org/jira/browse/HBASE-22721 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22721.branch-2.001.patch > > > HBaseFsck.java has too many code. And HBASE-22709 will use some inner of > HBaseFsck. So plan to refactor it. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22721) Refactor HBaseFsck: move the inner class out
[ https://issues.apache.org/jira/browse/HBASE-22721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22721: --- Attachment: HBASE-22721.branch-2.001.patch > Refactor HBaseFsck: move the inner class out > > > Key: HBASE-22721 > URL: https://issues.apache.org/jira/browse/HBASE-22721 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22721.branch-2.001.patch > > > HBaseFsck.java has too many code. And HBASE-22709 will use some inner of > HBaseFsck. So plan to refactor it. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22527) [hbck2] Add a master web ui to show the problematic regions
[ https://issues.apache.org/jira/browse/HBASE-22527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891490#comment-16891490 ] Guanghao Zhang commented on HBASE-22527: bq. add a release note please. done, sir. > [hbck2] Add a master web ui to show the problematic regions > --- > > Key: HBASE-22527 > URL: https://issues.apache.org/jira/browse/HBASE-22527 > Project: HBase > Issue Type: Sub-task > Components: hbase-operator-tools, hbck2 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6 > > Attachments: HBASE-22527.branch-2.0.001.patch, > HBASE-22527.branch-2.0.001.patch, HBASE-22527.branch-2.0.002.patch, > HBASE-22527.branch-2.1.001.patch, HBASE-22527.branch-2.1.002.patch, > HBASE-22527.branch-2.1.003.patch, HBASE-22527.master.001.patch, > HBASE-22527.master.002.patch, HBASE-22527.master.003.patch, > HBASE-22527.master.004.patch, HBASE-22527.master.addendum.patch > > > On our cluster which based 2.2.0, we found one problem: there are some opened > regions which had wrong regionserver in meta. The regionserver is not exist. > We used hbck2 to fix them by the following steps. > # disable table > # bypass the stucked close region procedure (as the target regionserver is > not exist) and disable table procedure. > # setRegionState to CLOSED. > # setTableState to DISABLED. > # enable table > We found this problem by scan the hbase:meta. I thought we should add this > feature to hbck2. The we can use hbck2 to find this problem. Thanks. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (HBASE-22527) [hbck2] Add a master web ui to show the problematic regions
[ https://issues.apache.org/jira/browse/HBASE-22527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang resolved HBASE-22527. Resolution: Fixed Fix Version/s: 2.1.6 2.2.1 2.0.6 2.3.0 3.0.0 Release Note: Add a new master web UI to show the potentially problematic opened regions. There are three case: 1. Master thought this region opened, but no regionserver reported it. 2. Master thought this region opened on Server1, but regionserver reported Server2 3. More than one regionservers reported opened this region > [hbck2] Add a master web ui to show the problematic regions > --- > > Key: HBASE-22527 > URL: https://issues.apache.org/jira/browse/HBASE-22527 > Project: HBase > Issue Type: Sub-task > Components: hbase-operator-tools, hbck2 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6 > > Attachments: HBASE-22527.branch-2.0.001.patch, > HBASE-22527.branch-2.0.001.patch, HBASE-22527.branch-2.0.002.patch, > HBASE-22527.branch-2.1.001.patch, HBASE-22527.branch-2.1.002.patch, > HBASE-22527.branch-2.1.003.patch, HBASE-22527.master.001.patch, > HBASE-22527.master.002.patch, HBASE-22527.master.003.patch, > HBASE-22527.master.004.patch, HBASE-22527.master.addendum.patch > > > On our cluster which based 2.2.0, we found one problem: there are some opened > regions which had wrong regionserver in meta. The regionserver is not exist. > We used hbck2 to fix them by the following steps. > # disable table > # bypass the stucked close region procedure (as the target regionserver is > not exist) and disable table procedure. > # setRegionState to CLOSED. > # setTableState to DISABLED. > # enable table > We found this problem by scan the hbase:meta. I thought we should add this > feature to hbck2. The we can use hbck2 to find this problem. Thanks. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22724) Add a emoji on the vote table for pre commit result on github
[ https://issues.apache.org/jira/browse/HBASE-22724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890835#comment-16890835 ] Guanghao Zhang commented on HBASE-22724: See https://github.com/apache/yetus/pull/67. The +1 will use :+1: emoji and -1 use :broken_heart: emoji. > Add a emoji on the vote table for pre commit result on github > - > > Key: HBASE-22724 > URL: https://issues.apache.org/jira/browse/HBASE-22724 > Project: HBase > Issue Type: Improvement >Reporter: Duo Zhang >Priority: Major > > [~zghaobac] said that the current vote table on github is not good enough, as > the colors are almost the same, it is not easy to find out which line is > broken. > Since github can not change the color of the text, he suggested that we add a > column at the left most with some emojis to better notify the developpers. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22709) Add a chore thread in master to do hbck checking
[ https://issues.apache.org/jira/browse/HBASE-22709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890704#comment-16890704 ] Guanghao Zhang commented on HBASE-22709: I found a bug for "Problematic Regions": the rsReports didn't remove the dead server's report. Will fix this in this issue. As I plan to move the "Problematic Regions" UI to a new hbck.jsp. > Add a chore thread in master to do hbck checking > > > Key: HBASE-22709 > URL: https://issues.apache.org/jira/browse/HBASE-22709 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22709.master.001.patch > > > See HBASE-21965. There may have two type of failed splited/merged regions. > One is orphan region on filesystem. Another one is unassigned daughter > regions or merged regions. Plan to add a seperate hbck.jsp for them. Will add > more hbck problems to this UI in future. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22709) Add a chore thread in master to do hbck checking
[ https://issues.apache.org/jira/browse/HBASE-22709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890698#comment-16890698 ] Guanghao Zhang commented on HBASE-22709: bq. Did you see suggestion of an 'adoption service' in HBASE-27145? We'd ask the Master to 'adopt' orphans found in HDFS (by your work here for instance). I thought we only fix it by HBCK2 now... The master UI shows the orphan regions and user use HBCK2 to fix them. > Add a chore thread in master to do hbck checking > > > Key: HBASE-22709 > URL: https://issues.apache.org/jira/browse/HBASE-22709 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22709.master.001.patch > > > See HBASE-21965. There may have two type of failed splited/merged regions. > One is orphan region on filesystem. Another one is unassigned daughter > regions or merged regions. Plan to add a seperate hbck.jsp for them. Will add > more hbck problems to this UI in future. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22527) [hbck2] Add a master web ui to show the problematic regions
[ https://issues.apache.org/jira/browse/HBASE-22527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22527: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-2.0 and branch-2.1. Thanks [~stack] for reviewing. > [hbck2] Add a master web ui to show the problematic regions > --- > > Key: HBASE-22527 > URL: https://issues.apache.org/jira/browse/HBASE-22527 > Project: HBase > Issue Type: Sub-task > Components: hbase-operator-tools, hbck2 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22527.branch-2.0.001.patch, > HBASE-22527.branch-2.0.001.patch, HBASE-22527.branch-2.0.002.patch, > HBASE-22527.branch-2.1.001.patch, HBASE-22527.branch-2.1.002.patch, > HBASE-22527.branch-2.1.003.patch, HBASE-22527.master.001.patch, > HBASE-22527.master.002.patch, HBASE-22527.master.003.patch, > HBASE-22527.master.004.patch, HBASE-22527.master.addendum.patch > > > On our cluster which based 2.2.0, we found one problem: there are some opened > regions which had wrong regionserver in meta. The regionserver is not exist. > We used hbck2 to fix them by the following steps. > # disable table > # bypass the stucked close region procedure (as the target regionserver is > not exist) and disable table procedure. > # setRegionState to CLOSED. > # setTableState to DISABLED. > # enable table > We found this problem by scan the hbase:meta. I thought we should add this > feature to hbck2. The we can use hbck2 to find this problem. Thanks. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22721) Refactor HBaseFsck: move the inner class out
[ https://issues.apache.org/jira/browse/HBASE-22721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890642#comment-16890642 ] Guanghao Zhang commented on HBASE-22721: bq. Should I do same thing over in hbase-operator-tools? hbasefsck has been moved there. Not need, sir. I refactor it because i want to use HbckRegionInfo class for HBASE-22709. > Refactor HBaseFsck: move the inner class out > > > Key: HBASE-22721 > URL: https://issues.apache.org/jira/browse/HBASE-22721 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > > HBaseFsck.java has too many code. And HBASE-22709 will use some inner of > HBaseFsck. So plan to refactor it. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22709) Add a chore thread in master to do hbck checking
[ https://issues.apache.org/jira/browse/HBASE-22709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890638#comment-16890638 ] Guanghao Zhang commented on HBASE-22709: bq. It runs once an hour? Yes. It need to scan all hdfs dir. So I thought no need to run it frequently. bq. Can operator ask to run it? Good idea. bq. I'm working on a patch to beef up CatalogJanitor so when it scans on its five minute interval, it reports on holes, overlaps, and unknown servers. Great. The patch here only handle the orphan regions on RegionServer or on HDFS and the inconsistent regions. > Add a chore thread in master to do hbck checking > > > Key: HBASE-22709 > URL: https://issues.apache.org/jira/browse/HBASE-22709 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22709.master.001.patch > > > See HBASE-21965. There may have two type of failed splited/merged regions. > One is orphan region on filesystem. Another one is unassigned daughter > regions or merged regions. Plan to add a seperate hbck.jsp for them. Will add > more hbck problems to this UI in future. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (HBASE-22721) Refactore HBaseFsck: move the inner class out
Guanghao Zhang created HBASE-22721: -- Summary: Refactore HBaseFsck: move the inner class out Key: HBASE-22721 URL: https://issues.apache.org/jira/browse/HBASE-22721 Project: HBase Issue Type: Bug Reporter: Guanghao Zhang HBaseFsck.java has too many code. And HBASE-22709 will use some inner of HBaseFsck. So plan to refactor it. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (HBASE-22721) Refactor HBaseFsck: move the inner class out
[ https://issues.apache.org/jira/browse/HBASE-22721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang reassigned HBASE-22721: -- Assignee: Guanghao Zhang > Refactor HBaseFsck: move the inner class out > > > Key: HBASE-22721 > URL: https://issues.apache.org/jira/browse/HBASE-22721 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > > HBaseFsck.java has too many code. And HBASE-22709 will use some inner of > HBaseFsck. So plan to refactor it. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22721) Refactor HBaseFsck: move the inner class out
[ https://issues.apache.org/jira/browse/HBASE-22721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22721: --- Summary: Refactor HBaseFsck: move the inner class out (was: Refactore HBaseFsck: move the inner class out) > Refactor HBaseFsck: move the inner class out > > > Key: HBASE-22721 > URL: https://issues.apache.org/jira/browse/HBASE-22721 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Priority: Major > > HBaseFsck.java has too many code. And HBASE-22709 will use some inner of > HBaseFsck. So plan to refactor it. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22709) Add a chore thread in master to do hbck checking
[ https://issues.apache.org/jira/browse/HBASE-22709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22709: --- Status: Patch Available (was: Open) > Add a chore thread in master to do hbck checking > > > Key: HBASE-22709 > URL: https://issues.apache.org/jira/browse/HBASE-22709 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22709.master.001.patch > > > See HBASE-21965. There may have two type of failed splited/merged regions. > One is orphan region on filesystem. Another one is unassigned daughter > regions or merged regions. Plan to add a seperate hbck.jsp for them. Will add > more hbck problems to this UI in future. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22709) Add a chore thread in master to do hbck checking
[ https://issues.apache.org/jira/browse/HBASE-22709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890567#comment-16890567 ] Guanghao Zhang commented on HBASE-22709: Let me move the refactor work to a new issue. > Add a chore thread in master to do hbck checking > > > Key: HBASE-22709 > URL: https://issues.apache.org/jira/browse/HBASE-22709 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22709.master.001.patch > > > See HBASE-21965. There may have two type of failed splited/merged regions. > One is orphan region on filesystem. Another one is unassigned daughter > regions or merged regions. Plan to add a seperate hbck.jsp for them. Will add > more hbck problems to this UI in future. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22709) Add a chore thread in master to do hbck checking
[ https://issues.apache.org/jira/browse/HBASE-22709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890067#comment-16890067 ] Guanghao Zhang commented on HBASE-22709: A basic patch. Refactor HBaseFsck and add a new HbckChecker chore in master. Will add ui later. > Add a chore thread in master to do hbck checking > > > Key: HBASE-22709 > URL: https://issues.apache.org/jira/browse/HBASE-22709 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22709.master.001.patch > > > See HBASE-21965. There may have two type of failed splited/merged regions. > One is orphan region on filesystem. Another one is unassigned daughter > regions or merged regions. Plan to add a seperate hbck.jsp for them. Will add > more hbck problems to this UI in future. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22709) Add a chore thread in master to do hbck checking
[ https://issues.apache.org/jira/browse/HBASE-22709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22709: --- Attachment: HBASE-22709.master.001.patch > Add a chore thread in master to do hbck checking > > > Key: HBASE-22709 > URL: https://issues.apache.org/jira/browse/HBASE-22709 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22709.master.001.patch > > > See HBASE-21965. There may have two type of failed splited/merged regions. > One is orphan region on filesystem. Another one is unassigned daughter > regions or merged regions. Plan to add a seperate hbck.jsp for them. Will add > more hbck problems to this UI in future. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22709) Add a chore thread in master to do hbck checking
[ https://issues.apache.org/jira/browse/HBASE-22709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22709: --- Summary: Add a chore thread in master to do hbck checking (was: Add a web ui to show the failed splited/merged regions) > Add a chore thread in master to do hbck checking > > > Key: HBASE-22709 > URL: https://issues.apache.org/jira/browse/HBASE-22709 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > > See HBASE-21965. There may have two type of failed splited/merged regions. > One is orphan region on filesystem. Another one is unassigned daughter > regions or merged regions. Plan to add a seperate hbck.jsp for them. Will add > more hbck problems to this UI in future. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22527) [hbck2] Add a master web ui to show the problematic regions
[ https://issues.apache.org/jira/browse/HBASE-22527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22527: --- Attachment: HBASE-22527.branch-2.0.002.patch > [hbck2] Add a master web ui to show the problematic regions > --- > > Key: HBASE-22527 > URL: https://issues.apache.org/jira/browse/HBASE-22527 > Project: HBase > Issue Type: Sub-task > Components: hbase-operator-tools, hbck2 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22527.branch-2.0.001.patch, > HBASE-22527.branch-2.0.001.patch, HBASE-22527.branch-2.0.002.patch, > HBASE-22527.branch-2.1.001.patch, HBASE-22527.branch-2.1.002.patch, > HBASE-22527.branch-2.1.003.patch, HBASE-22527.master.001.patch, > HBASE-22527.master.002.patch, HBASE-22527.master.003.patch, > HBASE-22527.master.004.patch, HBASE-22527.master.addendum.patch > > > On our cluster which based 2.2.0, we found one problem: there are some opened > regions which had wrong regionserver in meta. The regionserver is not exist. > We used hbck2 to fix them by the following steps. > # disable table > # bypass the stucked close region procedure (as the target regionserver is > not exist) and disable table procedure. > # setRegionState to CLOSED. > # setTableState to DISABLED. > # enable table > We found this problem by scan the hbase:meta. I thought we should add this > feature to hbck2. The we can use hbck2 to find this problem. Thanks. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22527) [hbck2] Add a master web ui to show the problematic regions
[ https://issues.apache.org/jira/browse/HBASE-22527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22527: --- Attachment: HBASE-22527.branch-2.0.001.patch > [hbck2] Add a master web ui to show the problematic regions > --- > > Key: HBASE-22527 > URL: https://issues.apache.org/jira/browse/HBASE-22527 > Project: HBase > Issue Type: Sub-task > Components: hbase-operator-tools, hbck2 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22527.branch-2.0.001.patch, > HBASE-22527.branch-2.0.001.patch, HBASE-22527.branch-2.1.001.patch, > HBASE-22527.branch-2.1.002.patch, HBASE-22527.branch-2.1.003.patch, > HBASE-22527.master.001.patch, HBASE-22527.master.002.patch, > HBASE-22527.master.003.patch, HBASE-22527.master.004.patch, > HBASE-22527.master.addendum.patch > > > On our cluster which based 2.2.0, we found one problem: there are some opened > regions which had wrong regionserver in meta. The regionserver is not exist. > We used hbck2 to fix them by the following steps. > # disable table > # bypass the stucked close region procedure (as the target regionserver is > not exist) and disable table procedure. > # setRegionState to CLOSED. > # setTableState to DISABLED. > # enable table > We found this problem by scan the hbase:meta. I thought we should add this > feature to hbck2. The we can use hbck2 to find this problem. Thanks. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-21965) Fix failed split and merge transactions that have failed to roll back
[ https://issues.apache.org/jira/browse/HBASE-21965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888518#comment-16888518 ] Guanghao Zhang commented on HBASE-21965: I opened HBASE-22709 to show these in master UI. > Fix failed split and merge transactions that have failed to roll back > - > > Key: HBASE-21965 > URL: https://issues.apache.org/jira/browse/HBASE-21965 > Project: HBase > Issue Type: Sub-task > Components: hbck2 >Reporter: Jingyun Tian >Assignee: Jingyun Tian >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: HBASE-21965.master.001.patch, > HBASE-21965.master.002.patch, HBASE-21965.master.003.patch, > HBASE-21965.master.004.patch, HBASE-21965.master.005.patch, > HBASE-21965.master.006.patch, HBASE-21965.master.007.patch, > HBASE-21965.master.007.patch, HBASE-21965.master.008.patch, > HBASE-21965.master.009.patch, HBASE-21965.master.010.patch, > HBASE-21965.master.011.patch, HBASE-21965.master.012.patch, > HBASE-21965.master.013.patch, HBASE-21965.master.014.patch, > HBASE-21965.master.014.patch > > > Make HBCK2 be able to fix failed split and merge transactions that have > failed to roll back. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (HBASE-21426) TestEncryptionKeyRotation.testCFKeyRotation is flaky
[ https://issues.apache.org/jira/browse/HBASE-21426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang resolved HBASE-21426. Resolution: Fixed Fix Version/s: 2.2.1 2.3.0 3.0.0 Pushed to branch-2.2+. Thanks [~Xiaolin Ha] for contributing. > TestEncryptionKeyRotation.testCFKeyRotation is flaky > > > Key: HBASE-21426 > URL: https://issues.apache.org/jira/browse/HBASE-21426 > Project: HBase > Issue Type: Bug >Reporter: Xiaolin Ha >Assignee: Xiaolin Ha >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.2.1 > > Attachments: testCFKeyRotation [Jenkins test result].pdf > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22527) [hbck2] Add a master web ui to show the problematic regions
[ https://issues.apache.org/jira/browse/HBASE-22527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888427#comment-16888427 ] Guanghao Zhang commented on HBASE-22527: The patch for 2.1 cannot apply to 2.0 directly. I reattached a patch for branch-2.0... > [hbck2] Add a master web ui to show the problematic regions > --- > > Key: HBASE-22527 > URL: https://issues.apache.org/jira/browse/HBASE-22527 > Project: HBase > Issue Type: Sub-task > Components: hbase-operator-tools, hbck2 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22527.branch-2.0.001.patch, > HBASE-22527.branch-2.1.001.patch, HBASE-22527.branch-2.1.002.patch, > HBASE-22527.branch-2.1.003.patch, HBASE-22527.master.001.patch, > HBASE-22527.master.002.patch, HBASE-22527.master.003.patch, > HBASE-22527.master.004.patch, HBASE-22527.master.addendum.patch > > > On our cluster which based 2.2.0, we found one problem: there are some opened > regions which had wrong regionserver in meta. The regionserver is not exist. > We used hbck2 to fix them by the following steps. > # disable table > # bypass the stucked close region procedure (as the target regionserver is > not exist) and disable table procedure. > # setRegionState to CLOSED. > # setTableState to DISABLED. > # enable table > We found this problem by scan the hbase:meta. I thought we should add this > feature to hbck2. The we can use hbck2 to find this problem. Thanks. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22527) [hbck2] Add a master web ui to show the problematic regions
[
https://issues.apache.org/jira/browse/HBASE-22527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888428#comment-16888428
]
Guanghao Zhang commented on HBASE-22527:
{quote}Pushed on branch-2.1
{quote}
Thanks sir. :)
> [hbck2] Add a master web ui to show the problematic regions
> ---
>
> Key: HBASE-22527
> URL: https://issues.apache.org/jira/browse/HBASE-22527
> Project: HBase
> Issue Type: Sub-task
> Components: hbase-operator-tools, hbck2
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Major
> Attachments: HBASE-22527.branch-2.0.001.patch,
> HBASE-22527.branch-2.1.001.patch, HBASE-22527.branch-2.1.002.patch,
> HBASE-22527.branch-2.1.003.patch, HBASE-22527.master.001.patch,
> HBASE-22527.master.002.patch, HBASE-22527.master.003.patch,
> HBASE-22527.master.004.patch, HBASE-22527.master.addendum.patch
>
>
> On our cluster which based 2.2.0, we found one problem: there are some opened
> regions which had wrong regionserver in meta. The regionserver is not exist.
> We used hbck2 to fix them by the following steps.
> # disable table
> # bypass the stucked close region procedure (as the target regionserver is
> not exist) and disable table procedure.
> # setRegionState to CLOSED.
> # setTableState to DISABLED.
> # enable table
> We found this problem by scan the hbase:meta. I thought we should add this
> feature to hbck2. The we can use hbck2 to find this problem. Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (HBASE-22527) [hbck2] Add a master web ui to show the problematic regions
[ https://issues.apache.org/jira/browse/HBASE-22527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22527: --- Attachment: HBASE-22527.branch-2.0.001.patch > [hbck2] Add a master web ui to show the problematic regions > --- > > Key: HBASE-22527 > URL: https://issues.apache.org/jira/browse/HBASE-22527 > Project: HBase > Issue Type: Sub-task > Components: hbase-operator-tools, hbck2 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22527.branch-2.0.001.patch, > HBASE-22527.branch-2.1.001.patch, HBASE-22527.branch-2.1.002.patch, > HBASE-22527.branch-2.1.003.patch, HBASE-22527.master.001.patch, > HBASE-22527.master.002.patch, HBASE-22527.master.003.patch, > HBASE-22527.master.004.patch, HBASE-22527.master.addendum.patch > > > On our cluster which based 2.2.0, we found one problem: there are some opened > regions which had wrong regionserver in meta. The regionserver is not exist. > We used hbck2 to fix them by the following steps. > # disable table > # bypass the stucked close region procedure (as the target regionserver is > not exist) and disable table procedure. > # setRegionState to CLOSED. > # setTableState to DISABLED. > # enable table > We found this problem by scan the hbase:meta. I thought we should add this > feature to hbck2. The we can use hbck2 to find this problem. Thanks. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22673) Avoid to expose protobuf stuff in Hbck interface
[ https://issues.apache.org/jira/browse/HBASE-22673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22673: --- Release Note: Mark the Hbck#scheduleServerCrashProcedure(List serverNames) as deprecated. Use Hbck#scheduleServerCrashProcedures(List serverNames) instead. > Avoid to expose protobuf stuff in Hbck interface > > > Key: HBASE-22673 > URL: https://issues.apache.org/jira/browse/HBASE-22673 > Project: HBase > Issue Type: Sub-task > Components: hbck2 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.2.1 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (HBASE-22673) Avoid to expose protobuf stuff in Hbck interface
[ https://issues.apache.org/jira/browse/HBASE-22673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang resolved HBASE-22673. Resolution: Fixed Fix Version/s: 2.2.1 2.3.0 3.0.0 Pushed to branch-2.2+. Thanks all for reviewing. > Avoid to expose protobuf stuff in Hbck interface > > > Key: HBASE-22673 > URL: https://issues.apache.org/jira/browse/HBASE-22673 > Project: HBase > Issue Type: Sub-task > Components: hbck2 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.2.1 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22527) [hbck2] Add a master web ui to show the problematic regions
[ https://issues.apache.org/jira/browse/HBASE-22527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22527: --- Attachment: HBASE-22527.branch-2.1.003.patch > [hbck2] Add a master web ui to show the problematic regions > --- > > Key: HBASE-22527 > URL: https://issues.apache.org/jira/browse/HBASE-22527 > Project: HBase > Issue Type: Sub-task > Components: hbase-operator-tools, hbck2 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22527.branch-2.1.001.patch, > HBASE-22527.branch-2.1.002.patch, HBASE-22527.branch-2.1.003.patch, > HBASE-22527.master.001.patch, HBASE-22527.master.002.patch, > HBASE-22527.master.003.patch, HBASE-22527.master.004.patch, > HBASE-22527.master.addendum.patch > > > On our cluster which based 2.2.0, we found one problem: there are some opened > regions which had wrong regionserver in meta. The regionserver is not exist. > We used hbck2 to fix them by the following steps. > # disable table > # bypass the stucked close region procedure (as the target regionserver is > not exist) and disable table procedure. > # setRegionState to CLOSED. > # setTableState to DISABLED. > # enable table > We found this problem by scan the hbase:meta. I thought we should add this > feature to hbck2. The we can use hbck2 to find this problem. Thanks. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22527) [hbck2] Add a master web ui to show the problematic regions
[ https://issues.apache.org/jira/browse/HBASE-22527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22527: --- Attachment: HBASE-22527.branch-2.1.002.patch > [hbck2] Add a master web ui to show the problematic regions > --- > > Key: HBASE-22527 > URL: https://issues.apache.org/jira/browse/HBASE-22527 > Project: HBase > Issue Type: Sub-task > Components: hbase-operator-tools, hbck2 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22527.branch-2.1.001.patch, > HBASE-22527.branch-2.1.002.patch, HBASE-22527.master.001.patch, > HBASE-22527.master.002.patch, HBASE-22527.master.003.patch, > HBASE-22527.master.004.patch, HBASE-22527.master.addendum.patch > > > On our cluster which based 2.2.0, we found one problem: there are some opened > regions which had wrong regionserver in meta. The regionserver is not exist. > We used hbck2 to fix them by the following steps. > # disable table > # bypass the stucked close region procedure (as the target regionserver is > not exist) and disable table procedure. > # setRegionState to CLOSED. > # setTableState to DISABLED. > # enable table > We found this problem by scan the hbase:meta. I thought we should add this > feature to hbck2. The we can use hbck2 to find this problem. Thanks. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22527) [hbck2] Add a master web ui to show the problematic regions
[ https://issues.apache.org/jira/browse/HBASE-22527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22527: --- Attachment: HBASE-22527.master.addendum.patch > [hbck2] Add a master web ui to show the problematic regions > --- > > Key: HBASE-22527 > URL: https://issues.apache.org/jira/browse/HBASE-22527 > Project: HBase > Issue Type: Sub-task > Components: hbase-operator-tools, hbck2 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22527.branch-2.1.001.patch, > HBASE-22527.master.001.patch, HBASE-22527.master.002.patch, > HBASE-22527.master.003.patch, HBASE-22527.master.004.patch, > HBASE-22527.master.addendum.patch > > > On our cluster which based 2.2.0, we found one problem: there are some opened > regions which had wrong regionserver in meta. The regionserver is not exist. > We used hbck2 to fix them by the following steps. > # disable table > # bypass the stucked close region procedure (as the target regionserver is > not exist) and disable table procedure. > # setRegionState to CLOSED. > # setTableState to DISABLED. > # enable table > We found this problem by scan the hbase:meta. I thought we should add this > feature to hbck2. The we can use hbck2 to find this problem. Thanks. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22527) [hbck2] Add a master web ui to show the problematic regions
[
https://issues.apache.org/jira/browse/HBASE-22527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887649#comment-16887649
]
Guanghao Zhang commented on HBASE-22527:
{quote}Commit w/o test to branch-2.1 and 2.0.
{quote}
I attatched a new patch for branch-2.1 which split the TestAssignmentManager to
a base class and test class.
> [hbck2] Add a master web ui to show the problematic regions
> ---
>
> Key: HBASE-22527
> URL: https://issues.apache.org/jira/browse/HBASE-22527
> Project: HBase
> Issue Type: Sub-task
> Components: hbase-operator-tools, hbck2
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Major
> Attachments: HBASE-22527.branch-2.1.001.patch,
> HBASE-22527.master.001.patch, HBASE-22527.master.002.patch,
> HBASE-22527.master.003.patch, HBASE-22527.master.004.patch
>
>
> On our cluster which based 2.2.0, we found one problem: there are some opened
> regions which had wrong regionserver in meta. The regionserver is not exist.
> We used hbck2 to fix them by the following steps.
> # disable table
> # bypass the stucked close region procedure (as the target regionserver is
> not exist) and disable table procedure.
> # setRegionState to CLOSED.
> # setTableState to DISABLED.
> # enable table
> We found this problem by scan the hbase:meta. I thought we should add this
> feature to hbck2. The we can use hbck2 to find this problem. Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (HBASE-22673) Avoid to expose protobuf stuff in Hbck interface
[
https://issues.apache.org/jira/browse/HBASE-22673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887609#comment-16887609
]
Guanghao Zhang commented on HBASE-22673:
{quote}Regards server-side, I meant the api w/ pb in it was added only on the
server-side. There was no shipping client that was capable of querying it, not
until HBASE-21322 goes in... So I'm thinking we can just change it.
{quote}
You mean only HBCK2 tool will use this api? And now HBASE-21393 is not
committed to HBCK2 tool? So just change this protobuf method directly?
> Avoid to expose protobuf stuff in Hbck interface
>
>
> Key: HBASE-22673
> URL: https://issues.apache.org/jira/browse/HBASE-22673
> Project: HBase
> Issue Type: Sub-task
> Components: hbck2
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Major
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (HBASE-22673) Avoid to expose protobuf stuff in Hbck interface
[
https://issues.apache.org/jira/browse/HBASE-22673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887600#comment-16887600
]
Guanghao Zhang commented on HBASE-22673:
{quote}Client-side hasn't gone in yet (HBASE-21393). Fix server-side first
[~zghaobac]? Makes sense to me.
{quote}
I mean that we should avoid expose protobuf stuff in Hbck interface.
server-side means?
> Avoid to expose protobuf stuff in Hbck interface
>
>
> Key: HBASE-22673
> URL: https://issues.apache.org/jira/browse/HBASE-22673
> Project: HBase
> Issue Type: Sub-task
> Components: hbck2
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Major
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (HBASE-22673) Avoid to expose protobuf stuff in Hbck interface
[
https://issues.apache.org/jira/browse/HBASE-22673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887594#comment-16887594
]
Guanghao Zhang commented on HBASE-22673:
{quote}It went into 3.0.0, 2.2.0, 2.0.3, 2.1.2 but client was only added
yesterday.
{quote}
It was added to Hbck interface. This is at client side and marked as
LimitPrivate.
> Avoid to expose protobuf stuff in Hbck interface
>
>
> Key: HBASE-22673
> URL: https://issues.apache.org/jira/browse/HBASE-22673
> Project: HBase
> Issue Type: Sub-task
> Components: hbck2
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Major
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (HBASE-22673) Avoid to expose protobuf stuff in Hbck interface
[
https://issues.apache.org/jira/browse/HBASE-22673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887593#comment-16887593
]
Guanghao Zhang commented on HBASE-22673:
{quote}Only in unreleased versions so far... 3.0.0, 2.3.0. No client yet. Safe
to remove!
{quote}
Let me remove it.
> Avoid to expose protobuf stuff in Hbck interface
>
>
> Key: HBASE-22673
> URL: https://issues.apache.org/jira/browse/HBASE-22673
> Project: HBase
> Issue Type: Sub-task
> Components: hbck2
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Major
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Assigned] (HBASE-22709) Add a web ui to show the failed splited/merged regions
[ https://issues.apache.org/jira/browse/HBASE-22709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang reassigned HBASE-22709: -- Assignee: Guanghao Zhang > Add a web ui to show the failed splited/merged regions > -- > > Key: HBASE-22709 > URL: https://issues.apache.org/jira/browse/HBASE-22709 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > > See HBASE-21965. There may have two type of failed splited/merged regions. > One is orphan region on filesystem. Another one is unassigned daughter > regions or merged regions. Plan to add a seperate hbck.jsp for them. Will add > more hbck problems to this UI in future. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (HBASE-22709) Add a web ui to show the failed splited/merged regions
Guanghao Zhang created HBASE-22709: -- Summary: Add a web ui to show the failed splited/merged regions Key: HBASE-22709 URL: https://issues.apache.org/jira/browse/HBASE-22709 Project: HBase Issue Type: Sub-task Reporter: Guanghao Zhang See HBASE-21965. There may have two type of failed splited/merged regions. One is orphan region on filesystem. Another one is unassigned daughter regions or merged regions. Plan to add a seperate hbck.jsp for them. Will add more hbck problems to this UI in future. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22708) Remove the deprecated methods in Hbck interface
[ https://issues.apache.org/jira/browse/HBASE-22708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22708: --- Description: Only for 3.0.0. Remove the methods which mark deprecated in HBASE-22673. > Remove the deprecated methods in Hbck interface > --- > > Key: HBASE-22708 > URL: https://issues.apache.org/jira/browse/HBASE-22708 > Project: HBase > Issue Type: Sub-task >Affects Versions: 3.0.0 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > > Only for 3.0.0. Remove the methods which mark deprecated in HBASE-22673. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (HBASE-22708) Remove the deprecated methods in Hbck interface
Guanghao Zhang created HBASE-22708: -- Summary: Remove the deprecated methods in Hbck interface Key: HBASE-22708 URL: https://issues.apache.org/jira/browse/HBASE-22708 Project: HBase Issue Type: Sub-task Affects Versions: 3.0.0 Reporter: Guanghao Zhang Assignee: Guanghao Zhang -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22673) Avoid to expose protobuf stuff in Hbck interface
[ https://issues.apache.org/jira/browse/HBASE-22673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22673: --- Issue Type: Sub-task (was: Improvement) Parent: HBASE-21745 > Avoid to expose protobuf stuff in Hbck interface > > > Key: HBASE-22673 > URL: https://issues.apache.org/jira/browse/HBASE-22673 > Project: HBase > Issue Type: Sub-task > Components: hbck2 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22527) [hbck2] Add a master web ui to show the problematic regions
[ https://issues.apache.org/jira/browse/HBASE-22527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-22527: --- Attachment: HBASE-22527.branch-2.1.001.patch > [hbck2] Add a master web ui to show the problematic regions > --- > > Key: HBASE-22527 > URL: https://issues.apache.org/jira/browse/HBASE-22527 > Project: HBase > Issue Type: Sub-task > Components: hbase-operator-tools, hbck2 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22527.branch-2.1.001.patch, > HBASE-22527.master.001.patch, HBASE-22527.master.002.patch, > HBASE-22527.master.003.patch, HBASE-22527.master.004.patch > > > On our cluster which based 2.2.0, we found one problem: there are some opened > regions which had wrong regionserver in meta. The regionserver is not exist. > We used hbck2 to fix them by the following steps. > # disable table > # bypass the stucked close region procedure (as the target regionserver is > not exist) and disable table procedure. > # setRegionState to CLOSED. > # setTableState to DISABLED. > # enable table > We found this problem by scan the hbase:meta. I thought we should add this > feature to hbck2. The we can use hbck2 to find this problem. Thanks. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (HBASE-22704) Avoid NPE when access table.jsp and snapshot.jsp but master not finish initialization
[
https://issues.apache.org/jira/browse/HBASE-22704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang resolved HBASE-22704.
Resolution: Fixed
Fix Version/s: 2.1.6
2.2.1
2.0.6
2.3.0
3.0.0
Pushed to branch-2.0+.
> Avoid NPE when access table.jsp and snapshot.jsp but master not finish
> initialization
> -
>
> Key: HBASE-22704
> URL: https://issues.apache.org/jira/browse/HBASE-22704
> Project: HBase
> Issue Type: Improvement
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Minor
> Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6
>
>
> {code:java}
> 2019-07-16,11:11:56,895 WARN [qtp1930319715-581]
> org.eclipse.jetty.servlet.ServletHandler: /table.jsp
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.generated.master.table_jsp._jspService(table_jsp.java:154)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1780)
> at
> org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:112)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)
> at
> org.apache.hadoop.hbase.http.ClickjackingPreventionFilter.doFilter(ClickjackingPreventionFilter.java:48)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)
> at
> org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:1428)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)
> at org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:50)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)
> at org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:50)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:513)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
> at org.eclipse.jetty.server.Server.handle(Server.java:539)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333)
> at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108)
> at
> org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
> at
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
> at
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
> at
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (HBASE-21426) TestEncryptionKeyRotation.testCFKeyRotation is flaky
[ https://issues.apache.org/jira/browse/HBASE-21426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887523#comment-16887523 ] Guanghao Zhang commented on HBASE-21426: Pushed to master to see the result. > TestEncryptionKeyRotation.testCFKeyRotation is flaky > > > Key: HBASE-21426 > URL: https://issues.apache.org/jira/browse/HBASE-21426 > Project: HBase > Issue Type: Bug >Reporter: Xiaolin Ha >Assignee: Xiaolin Ha >Priority: Major > Attachments: testCFKeyRotation [Jenkins test result].pdf > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22527) [hbck2] Add a master web ui to show the problematic regions
[ https://issues.apache.org/jira/browse/HBASE-22527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887520#comment-16887520 ] Guanghao Zhang commented on HBASE-22527: Pushed to branch-2.2+. For branch-2.1 and 2.0, need a new patch as there are no TestAssignmentManagerBase. > [hbck2] Add a master web ui to show the problematic regions > --- > > Key: HBASE-22527 > URL: https://issues.apache.org/jira/browse/HBASE-22527 > Project: HBase > Issue Type: Sub-task > Components: hbase-operator-tools, hbck2 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: HBASE-22527.master.001.patch, > HBASE-22527.master.002.patch, HBASE-22527.master.003.patch, > HBASE-22527.master.004.patch > > > On our cluster which based 2.2.0, we found one problem: there are some opened > regions which had wrong regionserver in meta. The regionserver is not exist. > We used hbck2 to fix them by the following steps. > # disable table > # bypass the stucked close region procedure (as the target regionserver is > not exist) and disable table procedure. > # setRegionState to CLOSED. > # setTableState to DISABLED. > # enable table > We found this problem by scan the hbase:meta. I thought we should add this > feature to hbck2. The we can use hbck2 to find this problem. Thanks. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22527) [hbck2] Add a master web ui to show the problematic regions
[
https://issues.apache.org/jira/browse/HBASE-22527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887127#comment-16887127
]
Guanghao Zhang commented on HBASE-22527:
{quote}can we get this in all branches-2?
{quote}
I thought this can be committed to all branches.
For this feature, I plan to add more web ui for hbck problems in following
issues. Maybe a seperate hbck jsp in future. It not only show the problem, also
suggest user how to fix it.
> [hbck2] Add a master web ui to show the problematic regions
> ---
>
> Key: HBASE-22527
> URL: https://issues.apache.org/jira/browse/HBASE-22527
> Project: HBase
> Issue Type: Sub-task
> Components: hbase-operator-tools, hbck2
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Major
> Attachments: HBASE-22527.master.001.patch,
> HBASE-22527.master.002.patch, HBASE-22527.master.003.patch,
> HBASE-22527.master.004.patch
>
>
> On our cluster which based 2.2.0, we found one problem: there are some opened
> regions which had wrong regionserver in meta. The regionserver is not exist.
> We used hbck2 to fix them by the following steps.
> # disable table
> # bypass the stucked close region procedure (as the target regionserver is
> not exist) and disable table procedure.
> # setRegionState to CLOSED.
> # setTableState to DISABLED.
> # enable table
> We found this problem by scan the hbase:meta. I thought we should add this
> feature to hbck2. The we can use hbck2 to find this problem. Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
