[jira] [Resolved] (HBASE-26562) Release hbase-operator-tools 1.2.0
[ https://issues.apache.org/jira/browse/HBASE-26562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng resolved HBASE-26562. --- Resolution: Resolved > Release hbase-operator-tools 1.2.0 > -- > > Key: HBASE-26562 > URL: https://issues.apache.org/jira/browse/HBASE-26562 > Project: HBase > Issue Type: Umbrella >Reporter: Duo Zhang >Assignee: Guangxu Cheng >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work started] (HBASE-26562) Release hbase-operator-tools 1.2.0
[ https://issues.apache.org/jira/browse/HBASE-26562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-26562 started by Guangxu Cheng. - > Release hbase-operator-tools 1.2.0 > -- > > Key: HBASE-26562 > URL: https://issues.apache.org/jira/browse/HBASE-26562 > Project: HBase > Issue Type: Umbrella >Reporter: Duo Zhang >Assignee: Guangxu Cheng >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HBASE-26562) Release hbase-operator-tools 1.2.0
[ https://issues.apache.org/jira/browse/HBASE-26562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-26562: -- Status: Open (was: Patch Available) > Release hbase-operator-tools 1.2.0 > -- > > Key: HBASE-26562 > URL: https://issues.apache.org/jira/browse/HBASE-26562 > Project: HBase > Issue Type: Umbrella >Reporter: Duo Zhang >Assignee: Guangxu Cheng >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HBASE-26562) Release hbase-operator-tools 1.2.0
[ https://issues.apache.org/jira/browse/HBASE-26562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-26562: -- Status: Patch Available (was: In Progress) > Release hbase-operator-tools 1.2.0 > -- > > Key: HBASE-26562 > URL: https://issues.apache.org/jira/browse/HBASE-26562 > Project: HBase > Issue Type: Umbrella >Reporter: Duo Zhang >Assignee: Guangxu Cheng >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (HBASE-26562) Release hbase-operator-tools 1.2.0
[ https://issues.apache.org/jira/browse/HBASE-26562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465517#comment-17465517 ] Guangxu Cheng commented on HBASE-26562: --- Done > Release hbase-operator-tools 1.2.0 > -- > > Key: HBASE-26562 > URL: https://issues.apache.org/jira/browse/HBASE-26562 > Project: HBase > Issue Type: Umbrella >Reporter: Duo Zhang >Assignee: Guangxu Cheng >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work started] (HBASE-26562) Release hbase-operator-tools 1.2.0
[ https://issues.apache.org/jira/browse/HBASE-26562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-26562 started by Guangxu Cheng. - > Release hbase-operator-tools 1.2.0 > -- > > Key: HBASE-26562 > URL: https://issues.apache.org/jira/browse/HBASE-26562 > Project: HBase > Issue Type: Umbrella >Reporter: Duo Zhang >Assignee: Guangxu Cheng >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work stopped] (HBASE-26562) Release hbase-operator-tools 1.2.0
[ https://issues.apache.org/jira/browse/HBASE-26562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-26562 stopped by Guangxu Cheng. - > Release hbase-operator-tools 1.2.0 > -- > > Key: HBASE-26562 > URL: https://issues.apache.org/jira/browse/HBASE-26562 > Project: HBase > Issue Type: Umbrella >Reporter: Duo Zhang >Assignee: Guangxu Cheng >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work started] (HBASE-26562) Release hbase-operator-tools 1.2.0
[ https://issues.apache.org/jira/browse/HBASE-26562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-26562 started by Guangxu Cheng. - > Release hbase-operator-tools 1.2.0 > -- > > Key: HBASE-26562 > URL: https://issues.apache.org/jira/browse/HBASE-26562 > Project: HBase > Issue Type: Umbrella >Reporter: Duo Zhang >Assignee: Guangxu Cheng >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (HBASE-26627) [hbase-operator-tools] Set version as 1.3.0-SNAPSHOT in master
[ https://issues.apache.org/jira/browse/HBASE-26627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng resolved HBASE-26627. --- Resolution: Fixed > [hbase-operator-tools] Set version as 1.3.0-SNAPSHOT in master > -- > > Key: HBASE-26627 > URL: https://issues.apache.org/jira/browse/HBASE-26627 > Project: HBase > Issue Type: Sub-task > Components: hbase-operator-tools >Affects Versions: hbase-operator-tools-1.2.0 >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (HBASE-26626) Update download page for HBase Operator Tools to 1.2.0
[ https://issues.apache.org/jira/browse/HBASE-26626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng resolved HBASE-26626. --- Resolution: Fixed > Update download page for HBase Operator Tools to 1.2.0 > -- > > Key: HBASE-26626 > URL: https://issues.apache.org/jira/browse/HBASE-26626 > Project: HBase > Issue Type: Sub-task >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HBASE-26627) [hbase-operator-tools] Set version as 1.3.0-SNAPSHOT in master
[ https://issues.apache.org/jira/browse/HBASE-26627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-26627: -- Summary: [hbase-operator-tools] Set version as 1.3.0-SNAPSHOT in master (was: Set version as 1.3.0-SNAPSHOT in master) > [hbase-operator-tools] Set version as 1.3.0-SNAPSHOT in master > -- > > Key: HBASE-26627 > URL: https://issues.apache.org/jira/browse/HBASE-26627 > Project: HBase > Issue Type: Sub-task > Components: hbase-operator-tools >Affects Versions: hbase-operator-tools-1.2.0 >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HBASE-26627) Set version as 1.3.0-SNAPSHOT in master
[ https://issues.apache.org/jira/browse/HBASE-26627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-26627: -- Affects Version/s: hbase-operator-tools-1.2.0 > Set version as 1.3.0-SNAPSHOT in master > --- > > Key: HBASE-26627 > URL: https://issues.apache.org/jira/browse/HBASE-26627 > Project: HBase > Issue Type: Sub-task > Components: hbase-operator-tools >Affects Versions: hbase-operator-tools-1.2.0 >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HBASE-26627) Set version as 1.3.0-SNAPSHOT in master
[ https://issues.apache.org/jira/browse/HBASE-26627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-26627: -- Component/s: hbase-operator-tools > Set version as 1.3.0-SNAPSHOT in master > --- > > Key: HBASE-26627 > URL: https://issues.apache.org/jira/browse/HBASE-26627 > Project: HBase > Issue Type: Sub-task > Components: hbase-operator-tools >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (HBASE-26627) Set version as 1.3.0-SNAPSHOT in master
Guangxu Cheng created HBASE-26627: - Summary: Set version as 1.3.0-SNAPSHOT in master Key: HBASE-26627 URL: https://issues.apache.org/jira/browse/HBASE-26627 Project: HBase Issue Type: Sub-task Reporter: Guangxu Cheng Assignee: Guangxu Cheng -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (HBASE-26626) Update download page for HBase Operator Tools to 1.2.0
Guangxu Cheng created HBASE-26626: - Summary: Update download page for HBase Operator Tools to 1.2.0 Key: HBASE-26626 URL: https://issues.apache.org/jira/browse/HBASE-26626 Project: HBase Issue Type: Sub-task Reporter: Guangxu Cheng Assignee: Guangxu Cheng -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (HBASE-26608) [hbase-operator-tools] Upgrade log4j2 to 2.17.0
[ https://issues.apache.org/jira/browse/HBASE-26608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462151#comment-17462151 ] Guangxu Cheng commented on HBASE-26608: --- I will submit a new pr to upgrade log4j2 to 2.17.0 > [hbase-operator-tools] Upgrade log4j2 to 2.17.0 > --- > > Key: HBASE-26608 > URL: https://issues.apache.org/jira/browse/HBASE-26608 > Project: HBase > Issue Type: Task > Components: hbase-operator-tools, logging, security >Reporter: Duo Zhang >Assignee: Guangxu Cheng >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (HBASE-26608) [hbase-operator-tools] Upgrade log4j2 to 2.17.0
[ https://issues.apache.org/jira/browse/HBASE-26608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng reassigned HBASE-26608: - Assignee: Guangxu Cheng > [hbase-operator-tools] Upgrade log4j2 to 2.17.0 > --- > > Key: HBASE-26608 > URL: https://issues.apache.org/jira/browse/HBASE-26608 > Project: HBase > Issue Type: Task > Components: hbase-operator-tools, logging, security >Reporter: Duo Zhang >Assignee: Guangxu Cheng >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (HBASE-26574) [hbase-operator-tools] Set version as 1.2.0 in master
[ https://issues.apache.org/jira/browse/HBASE-26574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng resolved HBASE-26574. --- Fix Version/s: hbase-operator-tools-1.2.0 Resolution: Resolved > [hbase-operator-tools] Set version as 1.2.0 in master > - > > Key: HBASE-26574 > URL: https://issues.apache.org/jira/browse/HBASE-26574 > Project: HBase > Issue Type: Sub-task >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > Fix For: hbase-operator-tools-1.2.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HBASE-26573) [hbase-operator-tools] Generate CHANGES.md and RELEASENOTES.md for 1.2.0
[ https://issues.apache.org/jira/browse/HBASE-26573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-26573: -- Fix Version/s: hbase-operator-tools-1.2.0 > [hbase-operator-tools] Generate CHANGES.md and RELEASENOTES.md for 1.2.0 > > > Key: HBASE-26573 > URL: https://issues.apache.org/jira/browse/HBASE-26573 > Project: HBase > Issue Type: Sub-task >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > Fix For: hbase-operator-tools-1.2.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (HBASE-26573) [hbase-operator-tools] Generate CHANGES.md and RELEASENOTES.md for 1.2.0
[ https://issues.apache.org/jira/browse/HBASE-26573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng resolved HBASE-26573. --- Resolution: Resolved > [hbase-operator-tools] Generate CHANGES.md and RELEASENOTES.md for 1.2.0 > > > Key: HBASE-26573 > URL: https://issues.apache.org/jira/browse/HBASE-26573 > Project: HBase > Issue Type: Sub-task >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (HBASE-26574) [hbase-operator-tools] Set version as 1.2.0 in master
Guangxu Cheng created HBASE-26574: - Summary: [hbase-operator-tools] Set version as 1.2.0 in master Key: HBASE-26574 URL: https://issues.apache.org/jira/browse/HBASE-26574 Project: HBase Issue Type: Sub-task Reporter: Guangxu Cheng Assignee: Guangxu Cheng -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (HBASE-26573) [hbase-operator-tools] Generate CHANGES.md and RELEASENOTES.md for 1.2.0
Guangxu Cheng created HBASE-26573: - Summary: [hbase-operator-tools] Generate CHANGES.md and RELEASENOTES.md for 1.2.0 Key: HBASE-26573 URL: https://issues.apache.org/jira/browse/HBASE-26573 Project: HBase Issue Type: Sub-task Reporter: Guangxu Cheng Assignee: Guangxu Cheng -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HBASE-24204) HBCK2 feature negotiation for commands not on Hbck interface
[ https://issues.apache.org/jira/browse/HBASE-24204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-24204: -- Fix Version/s: hbase-operator-tools-2.0.0 (was: hbase-operator-tools-1.2.0) > HBCK2 feature negotiation for commands not on Hbck interface > > > Key: HBASE-24204 > URL: https://issues.apache.org/jira/browse/HBASE-24204 > Project: HBase > Issue Type: Improvement > Components: hbase-operator-tools >Reporter: Peter Somogyi >Priority: Major > Fix For: hbase-operator-tools-2.0.0 > > > Some HBCK2 commands use version based checking for determining compatibility. > HBASE-24039 changed this to feature-based compatibility check with commands > using org.apache.hadoop.hbase.client.Hbck interface. > A similar approach is needed for the remaining commands that are using > different APIs. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HBASE-21369) [hbase-operator-tools] Create a tool that will write the versions file
[ https://issues.apache.org/jira/browse/HBASE-21369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-21369: -- Fix Version/s: hbase-operator-tools-2.0.0 (was: hbase-operator-tools-1.2.0) > [hbase-operator-tools] Create a tool that will write the versions file > -- > > Key: HBASE-21369 > URL: https://issues.apache.org/jira/browse/HBASE-21369 > Project: HBase > Issue Type: Task > Components: hbase-operator-tools >Reporter: Michael Stack >Priority: Major > Fix For: hbase-operator-tools-2.0.0 > > > hbck1 has the facility for restoring the hbase.version file under /hbase if > it goes missing. This issue is about building a dedicated tool to do this in > hbase-operator-tools or making use of hbck1 as is to do it and document how > in refguide. > For description, see > http://hbase.apache.org/book.html#_special_cases_hbase_version_file_is_missing > As is, we have a regression in our fixup tooling. > Perhaps we create general fs fixup tool? It would do the above and then some. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HBASE-22983) [HBCK2] Record executed command and output to log file
[ https://issues.apache.org/jira/browse/HBASE-22983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-22983: -- Fix Version/s: hbase-operator-tools-2.0.0 (was: hbase-operator-tools-1.2.0) > [HBCK2] Record executed command and output to log file > -- > > Key: HBASE-22983 > URL: https://issues.apache.org/jira/browse/HBASE-22983 > Project: HBase > Issue Type: Sub-task > Components: hbase-operator-tools >Reporter: Peter Somogyi >Priority: Major > Fix For: hbase-operator-tools-2.0.0 > > > HBCK2 operations by default are logged to the console only. For > troubleshooting and tracking it is helpful to write the logs to a file with > the executed command arguments. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HBASE-23826) [HBCK2] Expose Multi-Region merge feature via hbck2
[ https://issues.apache.org/jira/browse/HBASE-23826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-23826: -- Fix Version/s: hbase-operator-tools-2.0.0 (was: hbase-operator-tools-1.2.0) > [HBCK2] Expose Multi-Region merge feature via hbck2 > --- > > Key: HBASE-23826 > URL: https://issues.apache.org/jira/browse/HBASE-23826 > Project: HBase > Issue Type: Task > Components: hbase-operator-tools >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Fix For: hbase-operator-tools-2.0.0 > > > HBase Master can do multi-region merge from: 2.0.6,2.1.6,2.2.1,2.3.0,3.0.0 > HBASE-22827 aims at exposing the feature via shell from: 2.3.0 & 3.0.0 > Let's use this Jira to track, exposing the access to the multi-region merge > feature from hbck2 for the versions where shell feature isn't available but > the master supports the multi merge feature & hbck service supports > mergeRegions api: i.e. 2.1.9+, 2.2.4+ and of course 2.3.0+,3.0.0+ where both > shell/hbck2 would be able to do the task for us. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HBASE-25965) Move delete of WAL directory out of LOG.info and avoid left over directory
[
https://issues.apache.org/jira/browse/HBASE-25965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guangxu Cheng updated HBASE-25965:
--
Fix Version/s: hbase-operator-tools-1.2.0
(was: 1.2.0)
> Move delete of WAL directory out of LOG.info and avoid left over directory
> --
>
> Key: HBASE-25965
> URL: https://issues.apache.org/jira/browse/HBASE-25965
> Project: HBase
> Issue Type: Bug
> Components: hbase-operator-tools
>Affects Versions: 1.1.0
>Reporter: Tak-Lon (Stephen) Wu
>Assignee: Tak-Lon (Stephen) Wu
>Priority: Minor
> Fix For: hbase-operator-tools-1.2.0
>
>
> Followup the comment by [~anoopsamjohn] on HBASE-25921 (in
> [PR#88|https://github.com/apache/hbase-operator-tools/pull/88])
> {quote} Not on this patch. But here is an issue. The actual delete() call
> happening within a Log statement. If INFO level not enabled, the delete wont
> get called. Can we fix that also here pls? {quote}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (HBASE-25921) Fix Wrong FileSystem when running `filesystem` on non-HDFS storage
[
https://issues.apache.org/jira/browse/HBASE-25921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guangxu Cheng updated HBASE-25921:
--
Fix Version/s: hbase-operator-tools-1.2.0
(was: 1.2.0)
> Fix Wrong FileSystem when running `filesystem` on non-HDFS storage
> --
>
> Key: HBASE-25921
> URL: https://issues.apache.org/jira/browse/HBASE-25921
> Project: HBase
> Issue Type: Bug
> Components: hbase-operator-tools
>Affects Versions: 1.0.0, 1.1.0, 1.2.0
>Reporter: Tak-Lon (Stephen) Wu
>Assignee: Tak-Lon (Stephen) Wu
>Priority: Minor
> Fix For: hbase-operator-tools-1.2.0
>
>
> recently we found a bug that when running {{hbck filesystem -f}} on a
> non-HDFS and caused {{Wrong FS}} error and cannot move forward.
> this change fix this problem and use {{FSUtils.getCurrentFileSystem}} to
> respect the root directory of what we set with {{hbase.rootdir}} in stead of
> just using {{fs.defaultFS}}
> e.g. this is one of the captured ERROR message
> {code}
> Exception in thread "main" java.lang.IllegalArgumentException: Wrong FS:
> s3://xyz/data/default/abc, expected: hdfs://xyz/
> at org.apache.hadoop.fs.FileSystem.checkPath(FileSystem.java:737)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.getPathName(DistributedFileSystem.java:233)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.listStatusInternal(DistributedFileSystem.java:1045)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.access$1000(DistributedFileSystem.java:131)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$24.doCall(DistributedFileSystem.java:1112)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$24.doCall(DistributedFileSystem.java:1109)
> at
> org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.listStatus(DistributedFileSystem.java:1119)
> at
> org.apache.hadoop.hbase.util.FSUtils.listStatusWithStatusFilter(FSUtils.java:1530)
> at
> org.apache.hbase.hbck1.HFileCorruptionChecker.checkTableDir(HFileCorruptionChecker.java:320)
> at
> org.apache.hbase.hbck1.HFileCorruptionChecker.checkTables(HFileCorruptionChecker.java:431)
> at org.apache.hbase.FileSystemFsck.fsck(FileSystemFsck.java:87)
> at org.apache.hbase.HBCK2.doCommandLine(HBCK2.java:721)
> at org.apache.hbase.HBCK2.run(HBCK2.java:631)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90)
> at org.apache.hbase.HBCK2.main(HBCK2.java:865)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (HBASE-26562) Release hbase-operator-tools 1.2.0
[ https://issues.apache.org/jira/browse/HBASE-26562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng reassigned HBASE-26562: - Assignee: Guangxu Cheng > Release hbase-operator-tools 1.2.0 > -- > > Key: HBASE-26562 > URL: https://issues.apache.org/jira/browse/HBASE-26562 > Project: HBase > Issue Type: Umbrella >Reporter: Duo Zhang >Assignee: Guangxu Cheng >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (HBASE-26166) table list in master ui has a minor bug
[ https://issues.apache.org/jira/browse/HBASE-26166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17393113#comment-17393113 ] Guangxu Cheng commented on HBASE-26166: --- Pushed to master and branch-2.3+，Thanks [~frostruan] for contributing. > table list in master ui has a minor bug > --- > > Key: HBASE-26166 > URL: https://issues.apache.org/jira/browse/HBASE-26166 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 2.4.5 >Reporter: ruanhui >Assignee: ruanhui >Priority: Minor > Fix For: 2.5.0, 3.0.0-alpha-2, 2.4.6, 2.3.7 > > Attachments: image-2021-08-03-20-20-25-352.png > > > !image-2021-08-03-20-20-25-352.png|width=931,height=162! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-26166) table list in master ui has a minor bug
[ https://issues.apache.org/jira/browse/HBASE-26166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng resolved HBASE-26166. --- Fix Version/s: 2.3.7 2.4.6 3.0.0-alpha-2 2.5.0 Hadoop Flags: Reviewed Resolution: Fixed > table list in master ui has a minor bug > --- > > Key: HBASE-26166 > URL: https://issues.apache.org/jira/browse/HBASE-26166 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 2.4.5 >Reporter: ruanhui >Assignee: ruanhui >Priority: Minor > Fix For: 2.5.0, 3.0.0-alpha-2, 2.4.6, 2.3.7 > > Attachments: image-2021-08-03-20-20-25-352.png > > > !image-2021-08-03-20-20-25-352.png|width=931,height=162! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-26166) table list in master ui has a minor bug
[ https://issues.apache.org/jira/browse/HBASE-26166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-26166: -- Attachment: image-2021-08-03-20-20-25-352.png > table list in master ui has a minor bug > --- > > Key: HBASE-26166 > URL: https://issues.apache.org/jira/browse/HBASE-26166 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 2.4.5 >Reporter: ruanhui >Assignee: ruanhui >Priority: Minor > Attachments: image-2021-08-03-13-09-24-030.png, > image-2021-08-03-20-20-25-352.png > > > !image-2021-08-03-13-09-24-030.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-26166) table list in master ui has a minor bug
[ https://issues.apache.org/jira/browse/HBASE-26166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-26166: -- Description: !image-2021-08-03-20-20-25-352.png|width=931,height=162! (was: !image-2021-08-03-13-09-24-030.png!) > table list in master ui has a minor bug > --- > > Key: HBASE-26166 > URL: https://issues.apache.org/jira/browse/HBASE-26166 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 2.4.5 >Reporter: ruanhui >Assignee: ruanhui >Priority: Minor > Attachments: image-2021-08-03-13-09-24-030.png, > image-2021-08-03-20-20-25-352.png > > > !image-2021-08-03-20-20-25-352.png|width=931,height=162! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24605) Break long region names in the web UI
[ https://issues.apache.org/jira/browse/HBASE-24605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng resolved HBASE-24605. --- Fix Version/s: 2.2.6 2.4.0 2.3.1 3.0.0-alpha-1 Resolution: Fixed Pushed to branch-2.2+, Thanks for your contributing.[~songxincun] > Break long region names in the web UI > - > > Key: HBASE-24605 > URL: https://issues.apache.org/jira/browse/HBASE-24605 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 3.0.0-alpha-1 >Reporter: song XinCun >Assignee: song XinCun >Priority: Minor > Fix For: 3.0.0-alpha-1, 2.3.1, 2.4.0, 2.2.6 > > Attachments: image-2020-06-21-20-18-37-041.png, > image-2020-06-21-20-19-25-183.png, image-2020-06-21-20-20-02-782.png, > image-2020-06-21-20-27-23-474.png, image-2020-06-21-20-28-36-464.png, > image-2020-06-21-20-29-07-819.png > > > Before this patch, when it comes to the long region name, the UI content will > be out of the screen, making it unreadable. Like this: > !image-2020-06-21-20-18-37-041.png|width=542,height=50! > !image-2020-06-21-20-19-25-183.png|width=531,height=23! > !image-2020-06-21-20-20-02-782.png|width=542,height=146! > > After this patch, the long region name wil be break to the new line, like > this: > !image-2020-06-21-20-27-23-474.png|width=529,height=35! > !image-2020-06-21-20-28-36-464.png|width=533,height=33! > !image-2020-06-21-20-29-07-819.png|width=531,height=117! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24478) The regionInfo parameter for MasterProcedureScheduler#waitRegions and MasterProcedureScheduler#wakeRegions should be plural
[ https://issues.apache.org/jira/browse/HBASE-24478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng resolved HBASE-24478. --- Fix Version/s: 2.2.6 2.4.0 2.3.1 3.0.0-alpha-1 Resolution: Fixed > The regionInfo parameter for MasterProcedureScheduler#waitRegions and > MasterProcedureScheduler#wakeRegions should be plural > > > Key: HBASE-24478 > URL: https://issues.apache.org/jira/browse/HBASE-24478 > Project: HBase > Issue Type: Improvement > Components: proc-v2 >Affects Versions: 3.0.0-alpha-1 >Reporter: song XinCun >Assignee: song XinCun >Priority: Minor > Fix For: 3.0.0-alpha-1, 2.3.1, 2.4.0, 2.2.6 > > > MasterProcedureScheduler#waitRegions and MasterProcedureScheduler#wakeRegions > deal with a list of regions, so the variable name of region info should be > plural -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-24478) The regionInfo parameter for MasterProcedureScheduler#waitRegions and MasterProcedureScheduler#wakeRegions should be plural
[ https://issues.apache.org/jira/browse/HBASE-24478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17136485#comment-17136485 ] Guangxu Cheng commented on HBASE-24478: --- Pushed to branch-2.2+. Thanks for your contributing.[~songxincun] > The regionInfo parameter for MasterProcedureScheduler#waitRegions and > MasterProcedureScheduler#wakeRegions should be plural > > > Key: HBASE-24478 > URL: https://issues.apache.org/jira/browse/HBASE-24478 > Project: HBase > Issue Type: Improvement > Components: proc-v2 >Affects Versions: 3.0.0-alpha-1 >Reporter: song XinCun >Assignee: song XinCun >Priority: Minor > > MasterProcedureScheduler#waitRegions and MasterProcedureScheduler#wakeRegions > deal with a list of regions, so the variable name of region info should be > plural -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24417) update copyright notices year to 2020
[ https://issues.apache.org/jira/browse/HBASE-24417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng resolved HBASE-24417. --- Fix Version/s: 2.4.0 2.3.0 3.0.0-alpha-1 Assignee: Guangxu Cheng Resolution: Fixed pushed to branch-2.3+ > update copyright notices year to 2020 > - > > Key: HBASE-24417 > URL: https://issues.apache.org/jira/browse/HBASE-24417 > Project: HBase > Issue Type: Task > Components: documentation >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > Fix For: 3.0.0-alpha-1, 2.3.0, 2.4.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24417) update copyright notices year to 2020
Guangxu Cheng created HBASE-24417: - Summary: update copyright notices year to 2020 Key: HBASE-24417 URL: https://issues.apache.org/jira/browse/HBASE-24417 Project: HBase Issue Type: Task Components: documentation Reporter: Guangxu Cheng -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guangxu Cheng resolved HBASE-23896.
---
Resolution: Fixed
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
> Attachments: HBASE-23896-branch-2.2-addendum.patch
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17090194#comment-17090194
]
Guangxu Cheng commented on HBASE-23896:
---
Pushed to branch-2.2. Thanks [~wchevreuil] [~tamaas] for reivew.
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
> Attachments: HBASE-23896-branch-2.2-addendum.patch
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17089642#comment-17089642
]
Guangxu Cheng commented on HBASE-23896:
---
I just attached an addendum patch. Could you please review it? [~wchevreuil]
[~tamaas] Thanks
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
> Attachments: HBASE-23896-branch-2.2-addendum.patch
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guangxu Cheng updated HBASE-23896:
--
Attachment: (was: HBASE-23896-branch-2.2-addendum.diff)
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
> Attachments: HBASE-23896-branch-2.2-addendum.patch
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guangxu Cheng updated HBASE-23896:
--
Attachment: HBASE-23896-branch-2.2-addendum.patch
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
> Attachments: HBASE-23896-branch-2.2-addendum.patch
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guangxu Cheng updated HBASE-23896:
--
Attachment: HBASE-23896-branch-2.2-addendum.diff
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
> Attachments: HBASE-23896-branch-2.2-addendum.patch
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17089633#comment-17089633
]
Guangxu Cheng commented on HBASE-23896:
---
I'm sorry for that. It’s because that getRandomUUID is not static in branch-2.2
as [~tamaas] said. I will make an addendum patch for this.
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guangxu Cheng resolved HBASE-23896.
---
Fix Version/s: 2.2.5
2.4.0
2.3.0
3.0.0
Resolution: Fixed
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17087310#comment-17087310
]
Guangxu Cheng commented on HBASE-23896:
---
Pushed to branch-2.2+, Thanks [~binlijin] for reivew.
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HBASE-24176) user_permission '.*' command failed to show all table permissions
[
https://issues.apache.org/jira/browse/HBASE-24176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guangxu Cheng updated HBASE-24176:
--
Component/s: shell
Priority: Minor (was: Major)
> user_permission '.*' command failed to show all table permissions
> --
>
> Key: HBASE-24176
> URL: https://issues.apache.org/jira/browse/HBASE-24176
> Project: HBase
> Issue Type: Bug
> Components: shell
>Reporter: song XinCun
>Assignee: song XinCun
>Priority: Minor
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
>
> When we grant somebody global permission, then we use '.*' as the argument of
> user_permission to show all table permissions, the following exception
> occurred:
> {code:java}
> hbase(main):001:0> grant 'user3', 'RW'
> Took 0.4144 seconds
>
>
> hbase(main):002:0> user_permission
> User
> Namespace,Table,Family,Qualifier:Permission
>
> user2 ,,,: [Permission:
> actions=READ,WRITE]
>
> user3 ,,,: [Permission:
> actions=READ,WRITE]
>
> hbaseadmin ,,,: [Permission:
> actions=READ,WRITE,EXEC,CREATE,ADMIN]
>
> 3 row(s)
> Took 0.0445 seconds
>
>
> hbase(main):003:0> user_permission '.*'
> User
> Namespace,Table,Family,Qualifier:Permission
>
> user1 default,t1,,: [Permission:
> actions=READ,WRITE]
>
> hbaseadmin default,t1,,: [Permission:
> actions=READ,WRITE,EXEC,CREATE,ADMIN]
> ERROR: failed to coerce
> org.apache.hadoop.hbase.security.access.GlobalPermission to
> org.apache.hadoop.hbase.security.access.TablePermissionFor usage try 'help
> "user_permission"'Took 0.0940 seconds
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-24176) user_permission '.*' command failed to show all table permissions
[
https://issues.apache.org/jira/browse/HBASE-24176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guangxu Cheng resolved HBASE-24176.
---
Fix Version/s: 2.2.5
2.4.0
2.3.0
3.0.0
Resolution: Fixed
> user_permission '.*' command failed to show all table permissions
> --
>
> Key: HBASE-24176
> URL: https://issues.apache.org/jira/browse/HBASE-24176
> Project: HBase
> Issue Type: Bug
>Reporter: song XinCun
>Assignee: song XinCun
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
>
> When we grant somebody global permission, then we use '.*' as the argument of
> user_permission to show all table permissions, the following exception
> occurred:
> {code:java}
> hbase(main):001:0> grant 'user3', 'RW'
> Took 0.4144 seconds
>
>
> hbase(main):002:0> user_permission
> User
> Namespace,Table,Family,Qualifier:Permission
>
> user2 ,,,: [Permission:
> actions=READ,WRITE]
>
> user3 ,,,: [Permission:
> actions=READ,WRITE]
>
> hbaseadmin ,,,: [Permission:
> actions=READ,WRITE,EXEC,CREATE,ADMIN]
>
> 3 row(s)
> Took 0.0445 seconds
>
>
> hbase(main):003:0> user_permission '.*'
> User
> Namespace,Table,Family,Qualifier:Permission
>
> user1 default,t1,,: [Permission:
> actions=READ,WRITE]
>
> hbaseadmin default,t1,,: [Permission:
> actions=READ,WRITE,EXEC,CREATE,ADMIN]
> ERROR: failed to coerce
> org.apache.hadoop.hbase.security.access.GlobalPermission to
> org.apache.hadoop.hbase.security.access.TablePermissionFor usage try 'help
> "user_permission"'Took 0.0940 seconds
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24176) user_permission '.*' command failed to show all table permissions
[
https://issues.apache.org/jira/browse/HBASE-24176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17082801#comment-17082801
]
Guangxu Cheng commented on HBASE-24176:
---
Pushed to branch-2.2+, Thanks for the contribution [~songxincun]
> user_permission '.*' command failed to show all table permissions
> --
>
> Key: HBASE-24176
> URL: https://issues.apache.org/jira/browse/HBASE-24176
> Project: HBase
> Issue Type: Bug
>Reporter: song XinCun
>Assignee: song XinCun
>Priority: Major
>
> When we grant somebody global permission, then we use '.*' as the argument of
> user_permission to show all table permissions, the following exception
> occurred:
> {code:java}
> hbase(main):001:0> grant 'user3', 'RW'
> Took 0.4144 seconds
>
>
> hbase(main):002:0> user_permission
> User
> Namespace,Table,Family,Qualifier:Permission
>
> user2 ,,,: [Permission:
> actions=READ,WRITE]
>
> user3 ,,,: [Permission:
> actions=READ,WRITE]
>
> hbaseadmin ,,,: [Permission:
> actions=READ,WRITE,EXEC,CREATE,ADMIN]
>
> 3 row(s)
> Took 0.0445 seconds
>
>
> hbase(main):003:0> user_permission '.*'
> User
> Namespace,Table,Family,Qualifier:Permission
>
> user1 default,t1,,: [Permission:
> actions=READ,WRITE]
>
> hbaseadmin default,t1,,: [Permission:
> actions=READ,WRITE,EXEC,CREATE,ADMIN]
> ERROR: failed to coerce
> org.apache.hadoop.hbase.security.access.GlobalPermission to
> org.apache.hadoop.hbase.security.access.TablePermissionFor usage try 'help
> "user_permission"'Took 0.0940 seconds
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
Guangxu Cheng created HBASE-23896:
-
Summary: Snapshot owner cannot delete snapshot when ACL is enabled
and Kerberos is not enabled
Key: HBASE-23896
URL: https://issues.apache.org/jira/browse/HBASE-23896
Project: HBase
Issue Type: Task
Affects Versions: 2.2.3, 3.0.0
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng
When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
delete the snapshot. This is because the owner of the snapshot cannot be taken
during permission verification. By investigation, found that only after HBase
has enabled security authentication, the owner will be set when doing snapshot.
SnapshotManager#takeSnapshotInternal
{code:title=SnapshotManager.java|borderStyle=solid}
RpcServer.getRequestUser().ifPresent(user -> {
if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
builder.setOwner(user.getShortName());
}
});
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HBASE-23312) HBase Thrift SPNEGO configs (HBASE-19852) should be backwards compatible
[ https://issues.apache.org/jira/browse/HBASE-23312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-23312: -- Fix Version/s: (was: 2.1.8) 2.1.9 > HBase Thrift SPNEGO configs (HBASE-19852) should be backwards compatible > > > Key: HBASE-23312 > URL: https://issues.apache.org/jira/browse/HBASE-23312 > Project: HBase > Issue Type: Bug > Components: Thrift >Affects Versions: 3.0.0, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.1.6, 2.1.7, > 2.1.8 >Reporter: Kevin Risden >Assignee: Kevin Risden >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.2.3, 2.1.9 > > Attachments: HBASE-23312.master.001.patch > > > HBASE-19852 is not backwards compatible since it now requires the SPNEGO > thrift configs. I haven't seen anything in Apache HBase about changing this > so that the older configs still work with a merged keytab. (fall back to the > non SPNEGO specific principal/keytab configs) > I wrote the original patch in HBASE-19852 and with hindsight being 20/20, I > think this section of could be extended to fall back to not requiring the > additional configs. > https://github.com/apache/hbase/blame/master/hbase-thrift/src/main/java/org/apache/hadoop/hbase/thrift/ThriftHttpServlet.java#L78 > Supporting the older configs allows upgrade from HBase 1.x to 2.x without > needing to change the configs ahead of time. I'll make sure to log a > deprecation warning if the older configs are used. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-20395) Displaying thrift server type on the thrift page
[ https://issues.apache.org/jira/browse/HBASE-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng resolved HBASE-20395. --- Resolution: Fixed pushed the addendum to branch-2 and master. Thanks @Beata Sudi > Displaying thrift server type on the thrift page > > > Key: HBASE-20395 > URL: https://issues.apache.org/jira/browse/HBASE-20395 > Project: HBase > Issue Type: Improvement > Components: Thrift >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: HBASE-20395.addendum.patch, > HBASE-20395.master.001.patch, HBASE-20395.master.002.patch, > HBASE-20395.master.003.patch, HBASE-20395.master.004.patch, > HBASE-20395.master.005.patch, HBASE-20395.master.005.patch, result.png > > > HBase supports two types of thrift server: thrift and thrift2. > But after start the thrift server successfully, we can not get the thrift > server type conveniently. > So, displaying thrift server type on the thrift page may provide some > convenience for the users. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-20395) Displaying thrift server type on the thrift page
[ https://issues.apache.org/jira/browse/HBASE-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-20395: -- Attachment: HBASE-20395.addendum.patch > Displaying thrift server type on the thrift page > > > Key: HBASE-20395 > URL: https://issues.apache.org/jira/browse/HBASE-20395 > Project: HBase > Issue Type: Improvement > Components: Thrift >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: HBASE-20395.addendum.patch, > HBASE-20395.master.001.patch, HBASE-20395.master.002.patch, > HBASE-20395.master.003.patch, HBASE-20395.master.004.patch, > HBASE-20395.master.005.patch, HBASE-20395.master.005.patch, result.png > > > HBase supports two types of thrift server: thrift and thrift2. > But after start the thrift server successfully, we can not get the thrift > server type conveniently. > So, displaying thrift server type on the thrift page may provide some > convenience for the users. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (HBASE-20395) Displaying thrift server type on the thrift page
[ https://issues.apache.org/jira/browse/HBASE-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng reopened HBASE-20395: --- > Displaying thrift server type on the thrift page > > > Key: HBASE-20395 > URL: https://issues.apache.org/jira/browse/HBASE-20395 > Project: HBase > Issue Type: Improvement > Components: Thrift >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: HBASE-20395.master.001.patch, > HBASE-20395.master.002.patch, HBASE-20395.master.003.patch, > HBASE-20395.master.004.patch, HBASE-20395.master.005.patch, > HBASE-20395.master.005.patch, result.png > > > HBase supports two types of thrift server: thrift and thrift2. > But after start the thrift server successfully, we can not get the thrift > server type conveniently. > So, displaying thrift server type on the thrift page may provide some > convenience for the users. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-20395) Displaying thrift server type on the thrift page
[ https://issues.apache.org/jira/browse/HBASE-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984424#comment-16984424 ] Guangxu Cheng commented on HBASE-20395: --- https://issues.apache.org/jira/browse/HBASE-20395?focusedCommentId=16436711&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16436711 As the above discussion, To avoid introducing new configuration, we set ThriftServerType as an attribute of InfoServer. But we set an instance of ThriftServerType instead of a string, so the above exception was reported. Let me upload a addendum to fix it. > Displaying thrift server type on the thrift page > > > Key: HBASE-20395 > URL: https://issues.apache.org/jira/browse/HBASE-20395 > Project: HBase > Issue Type: Improvement > Components: Thrift >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: HBASE-20395.master.001.patch, > HBASE-20395.master.002.patch, HBASE-20395.master.003.patch, > HBASE-20395.master.004.patch, HBASE-20395.master.005.patch, > HBASE-20395.master.005.patch, result.png > > > HBase supports two types of thrift server: thrift and thrift2. > But after start the thrift server successfully, we can not get the thrift > server type conveniently. > So, displaying thrift server type on the thrift page may provide some > convenience for the users. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-23293) [REPLICATION] make ship edits timeout configurable
[ https://issues.apache.org/jira/browse/HBASE-23293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng resolved HBASE-23293. --- Fix Version/s: 2.2.3 2.3.0 3.0.0 Resolution: Fixed > [REPLICATION] make ship edits timeout configurable > -- > > Key: HBASE-23293 > URL: https://issues.apache.org/jira/browse/HBASE-23293 > Project: HBase > Issue Type: Improvement > Components: Replication >Reporter: chenxu >Assignee: chenxu >Priority: Minor > Fix For: 3.0.0, 2.3.0, 2.2.3 > > > ReplicationSourceShipper#shipEdits may take a while if bulkload replication > enabled, since we should copy HFile from the source cluster, so i think there > is a need to make the timeout value configurable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23293) [REPLICATION] make ship edits timeout configurable
[ https://issues.apache.org/jira/browse/HBASE-23293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984112#comment-16984112 ] Guangxu Cheng commented on HBASE-23293: --- Pushed to branch-2 and branch-2.2. Thank [~javaman_chen] for your contributing. > [REPLICATION] make ship edits timeout configurable > -- > > Key: HBASE-23293 > URL: https://issues.apache.org/jira/browse/HBASE-23293 > Project: HBase > Issue Type: Improvement > Components: Replication >Reporter: chenxu >Assignee: chenxu >Priority: Minor > > ReplicationSourceShipper#shipEdits may take a while if bulkload replication > enabled, since we should copy HFile from the source cluster, so i think there > is a need to make the timeout value configurable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-20395) Displaying thrift server type on the thrift page
[ https://issues.apache.org/jira/browse/HBASE-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-20395: -- Fix Version/s: 2.3.0 3.0.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Displaying thrift server type on the thrift page > > > Key: HBASE-20395 > URL: https://issues.apache.org/jira/browse/HBASE-20395 > Project: HBase > Issue Type: Improvement > Components: Thrift >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: HBASE-20395.master.001.patch, > HBASE-20395.master.002.patch, HBASE-20395.master.003.patch, > HBASE-20395.master.004.patch, HBASE-20395.master.005.patch, > HBASE-20395.master.005.patch, result.png > > > HBase supports two types of thrift server: thrift and thrift2. > But after start the thrift server successfully, we can not get the thrift > server type conveniently. > So, displaying thrift server type on the thrift page may provide some > convenience for the users. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-20395) Displaying thrift server type on the thrift page
[ https://issues.apache.org/jira/browse/HBASE-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16982423#comment-16982423 ] Guangxu Cheng commented on HBASE-20395: --- pushed to master and branch-2. Thanks for all reviewers > Displaying thrift server type on the thrift page > > > Key: HBASE-20395 > URL: https://issues.apache.org/jira/browse/HBASE-20395 > Project: HBase > Issue Type: Improvement > Components: Thrift >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > Attachments: HBASE-20395.master.001.patch, > HBASE-20395.master.002.patch, HBASE-20395.master.003.patch, > HBASE-20395.master.004.patch, HBASE-20395.master.005.patch, > HBASE-20395.master.005.patch, result.png > > > HBase supports two types of thrift server: thrift and thrift2. > But after start the thrift server successfully, we can not get the thrift > server type conveniently. > So, displaying thrift server type on the thrift page may provide some > convenience for the users. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23336) [CLI] Incorrect row(s) count "clear_deadservers"
[
https://issues.apache.org/jira/browse/HBASE-23336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16982393#comment-16982393
]
Guangxu Cheng commented on HBASE-23336:
---
A simple patch. Push to branch-2.1+. Thank [~kpalanisamy] for your contributing.
> [CLI] Incorrect row(s) count "clear_deadservers"
> -
>
> Key: HBASE-23336
> URL: https://issues.apache.org/jira/browse/HBASE-23336
> Project: HBase
> Issue Type: Bug
> Components: shell
>Affects Versions: 3.0.0, 2.1.0, 2.2.0
>Reporter: Karthik Palanisamy
>Assignee: Karthik Palanisamy
>Priority: Minor
>
> [HBASE-15849|https://issues.apache.org/jira/browse/HBASE-15849] simplified
> the format of command total runtime but clear_deadservers caller has not
> modified so it prints current timestamp instead of no of rows.
>
> {code:java}
> hbase(main):015:0> clear_deadservers
> 'kpalanisamy-apache302.openstacklocal,16020'
> SERVERNAME
> kpalanisamy-apache302.openstacklocal,16020,16020
> 1574585488 row(s)
> Took 0.0145 seconds
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-23336) [CLI] Incorrect row(s) count "clear_deadservers"
[
https://issues.apache.org/jira/browse/HBASE-23336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guangxu Cheng resolved HBASE-23336.
---
Fix Version/s: 2.1.9
2.2.3
2.3.0
3.0.0
Resolution: Fixed
> [CLI] Incorrect row(s) count "clear_deadservers"
> -
>
> Key: HBASE-23336
> URL: https://issues.apache.org/jira/browse/HBASE-23336
> Project: HBase
> Issue Type: Bug
> Components: shell
>Affects Versions: 3.0.0, 2.1.0, 2.2.0
>Reporter: Karthik Palanisamy
>Assignee: Karthik Palanisamy
>Priority: Minor
> Fix For: 3.0.0, 2.3.0, 2.2.3, 2.1.9
>
>
> [HBASE-15849|https://issues.apache.org/jira/browse/HBASE-15849] simplified
> the format of command total runtime but clear_deadservers caller has not
> modified so it prints current timestamp instead of no of rows.
>
> {code:java}
> hbase(main):015:0> clear_deadservers
> 'kpalanisamy-apache302.openstacklocal,16020'
> SERVERNAME
> kpalanisamy-apache302.openstacklocal,16020,16020
> 1574585488 row(s)
> Took 0.0145 seconds
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23293) [REPLICATION] make ship edits timeout configurable
[ https://issues.apache.org/jira/browse/HBASE-23293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16982367#comment-16982367 ] Guangxu Cheng commented on HBASE-23293: --- [~javaman_chen] Pushed to master, but it didn't cherry-pick to branch-2. Could you put up a PR for the 2.x branches? > [REPLICATION] make ship edits timeout configurable > -- > > Key: HBASE-23293 > URL: https://issues.apache.org/jira/browse/HBASE-23293 > Project: HBase > Issue Type: Improvement > Components: Replication >Reporter: chenxu >Assignee: chenxu >Priority: Minor > > ReplicationSourceShipper#shipEdits may take a while if bulkload replication > enabled, since we should copy HFile from the source cluster, so i think there > is a need to make the timeout value configurable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23334) The table-lock node of zk is not needed since HBASE-16786
[ https://issues.apache.org/jira/browse/HBASE-23334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16981489#comment-16981489 ] Guangxu Cheng commented on HBASE-23334: --- Pushed to branch-2.2+. Made a little modification when cherry-pick to branch-2.2 Thanks for your contributing [~filtertip] > The table-lock node of zk is not needed since HBASE-16786 > - > > Key: HBASE-23334 > URL: https://issues.apache.org/jira/browse/HBASE-23334 > Project: HBase > Issue Type: Improvement >Reporter: Zheng Wang >Assignee: Zheng Wang >Priority: Minor > > The table-lock znode still be created when init,and it may cause confusion. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-23334) The table-lock node of zk is not needed since HBASE-16786
[ https://issues.apache.org/jira/browse/HBASE-23334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng resolved HBASE-23334. --- Fix Version/s: 2.2.3 2.3.0 3.0.0 Resolution: Fixed > The table-lock node of zk is not needed since HBASE-16786 > - > > Key: HBASE-23334 > URL: https://issues.apache.org/jira/browse/HBASE-23334 > Project: HBase > Issue Type: Improvement >Reporter: Zheng Wang >Assignee: Zheng Wang >Priority: Minor > Fix For: 3.0.0, 2.3.0, 2.2.3 > > > The table-lock znode still be created when init,and it may cause confusion. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-23237) Negative 'Requests per Second' counts in UI
[ https://issues.apache.org/jira/browse/HBASE-23237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng resolved HBASE-23237. --- Fix Version/s: 2.1.9 2.2.3 1.6.0 2.3.0 Resolution: Fixed > Negative 'Requests per Second' counts in UI > --- > > Key: HBASE-23237 > URL: https://issues.apache.org/jira/browse/HBASE-23237 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 2.2.2 >Reporter: Michael Stack >Assignee: Karthik Palanisamy >Priority: Major > Fix For: 3.0.0, 2.3.0, 1.6.0, 2.2.3, 2.1.9 > > Attachments: Screen Shot 2019-10-30 at 9.45.58 PM.png > > > I see request per second showing with negative sign. > !Screen Shot 2019-10-30 at 9.45.58 PM.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23237) Negative 'Requests per Second' counts in UI
[ https://issues.apache.org/jira/browse/HBASE-23237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16980813#comment-16980813 ] Guangxu Cheng commented on HBASE-23237: --- Pushed to branch-1 and branch-2.1+. Made a little modification when cherry-pick to branch-1 and branch-2. Thanks for your contributing [~kpalanisamy] > Negative 'Requests per Second' counts in UI > --- > > Key: HBASE-23237 > URL: https://issues.apache.org/jira/browse/HBASE-23237 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 2.2.2 >Reporter: Michael Stack >Assignee: Karthik Palanisamy >Priority: Major > Fix For: 3.0.0 > > Attachments: Screen Shot 2019-10-30 at 9.45.58 PM.png > > > I see request per second showing with negative sign. > !Screen Shot 2019-10-30 at 9.45.58 PM.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23325) [UI]rsgoup average load keep two decimals
[ https://issues.apache.org/jira/browse/HBASE-23325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-23325: -- Fix Version/s: 2.1.9 2.2.3 2.3.0 3.0.0 Status: Patch Available (was: Open) > [UI]rsgoup average load keep two decimals > - > > Key: HBASE-23325 > URL: https://issues.apache.org/jira/browse/HBASE-23325 > Project: HBase > Issue Type: Improvement >Reporter: xuqinya >Assignee: xuqinya >Priority: Minor > Fix For: 3.0.0, 2.3.0, 2.2.3, 2.1.9 > > Attachments: 20191121165713.png > > > In */master-status*, rsgoup average load keep two decimals. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23325) [UI]rsgoup average load keep two decimals
[ https://issues.apache.org/jira/browse/HBASE-23325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-23325: -- Resolution: Fixed Status: Resolved (was: Patch Available) > [UI]rsgoup average load keep two decimals > - > > Key: HBASE-23325 > URL: https://issues.apache.org/jira/browse/HBASE-23325 > Project: HBase > Issue Type: Improvement >Reporter: xuqinya >Assignee: xuqinya >Priority: Minor > Fix For: 3.0.0, 2.3.0, 2.2.3, 2.1.9 > > Attachments: 20191121165713.png > > > In */master-status*, rsgoup average load keep two decimals. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23325) [UI]rsgoup average load keep two decimals
[ https://issues.apache.org/jira/browse/HBASE-23325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16979905#comment-16979905 ] Guangxu Cheng commented on HBASE-23325: --- Pushed to branch-2.1+. Thanks for the patch [~xu qinya] > [UI]rsgoup average load keep two decimals > - > > Key: HBASE-23325 > URL: https://issues.apache.org/jira/browse/HBASE-23325 > Project: HBase > Issue Type: Improvement >Reporter: xuqinya >Assignee: xuqinya >Priority: Minor > Attachments: 20191121165713.png > > > In */master-status*, rsgoup average load keep two decimals. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-23278) Add a table-level compaction progress display on the UI
[ https://issues.apache.org/jira/browse/HBASE-23278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng resolved HBASE-23278. --- Fix Version/s: 2.2.3 1.6.0 2.3.0 3.0.0 Resolution: Fixed > Add a table-level compaction progress display on the UI > > > Key: HBASE-23278 > URL: https://issues.apache.org/jira/browse/HBASE-23278 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 1.6.0, master >Reporter: Baiqiang Zhao >Assignee: Baiqiang Zhao >Priority: Minor > Fix For: 3.0.0, 2.3.0, 1.6.0, 2.2.3 > > Attachments: HBase-23278-v2.png, HBase-23278.png, > image-2019-11-11-20-35-56-103.png, image-2019-11-11-20-37-53-367.png, > image-2019-11-11-20-44-04-050.png > > > We have regionserver-level compaction progress in UI. However, we often > compact a table, why there is no table-level compaction progress？Use multiple > tabs to show compaction progress. > !HBase-23278-v2.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23278) Add a table-level compaction progress display on the UI
[ https://issues.apache.org/jira/browse/HBASE-23278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16977444#comment-16977444 ] Guangxu Cheng commented on HBASE-23278: --- pushed to branch-1 and branch-2.2+ Thank [~DeanZ] for contributing > Add a table-level compaction progress display on the UI > > > Key: HBASE-23278 > URL: https://issues.apache.org/jira/browse/HBASE-23278 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 1.6.0, master >Reporter: Baiqiang Zhao >Assignee: Baiqiang Zhao >Priority: Minor > Attachments: HBase-23278-v2.png, HBase-23278.png, > image-2019-11-11-20-35-56-103.png, image-2019-11-11-20-37-53-367.png, > image-2019-11-11-20-44-04-050.png > > > We have regionserver-level compaction progress in UI. However, we often > compact a table, why there is no table-level compaction progress？Use multiple > tabs to show compaction progress. > !HBase-23278-v2.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23286) Improve MTTR: Split WAL to HFile
[ https://issues.apache.org/jira/browse/HBASE-23286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16974267#comment-16974267 ] Guangxu Cheng commented on HBASE-23286: --- I think it's better to write HFile to recovered.hfiles. If RegionServer is down during the split WAL, a corrupt HFile may be generated, which will cause the region to fail to open. If these HFiles are written to recovered.hfiles, It might be easier to deal with these files > Improve MTTR: Split WAL to HFile > > > Key: HBASE-23286 > URL: https://issues.apache.org/jira/browse/HBASE-23286 > Project: HBase > Issue Type: Improvement > Components: MTTR >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > > After HBASE-20724, the compaction event marker is not used anymore when > failover. So our new proposal is split WAL to HFile to imporve MTTR. It has 3 > steps: > # Read WAL and write HFile to region’s column family’s recovered.hfiles > directory. > # Open region. > # Bulkload the recovered.hfiles for every column family. > The design doc was attathed by a google doc. Any suggestions are welcomed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23245) All MutableHistogram implementations should remove maxExpected
[ https://issues.apache.org/jira/browse/HBASE-23245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-23245: -- Resolution: Fixed Status: Resolved (was: Patch Available) > All MutableHistogram implementations should remove maxExpected > -- > > Key: HBASE-23245 > URL: https://issues.apache.org/jira/browse/HBASE-23245 > Project: HBase > Issue Type: Improvement > Components: metrics >Affects Versions: 3.0.0, 2.3.0, 1.6.0 >Reporter: Viraj Jasani >Assignee: Viraj Jasani >Priority: Major > Fix For: 3.0.0, 2.3.0, 1.6.0, 1.4.12, 2.1.8, 2.2.3 > > > MutableHistogram is using HistogramImpl() and not using maxExpected. From all > implementation classes, maxExpected should be removed as constructor > argument. Also, HistogramImpl() should pass long casting for > Integer.MAX_VALUE << 2 else it is treated as -4 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23245) All MutableHistogram implementations should remove maxExpected
[ https://issues.apache.org/jira/browse/HBASE-23245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-23245: -- Fix Version/s: 2.2.3 2.1.8 1.4.12 > All MutableHistogram implementations should remove maxExpected > -- > > Key: HBASE-23245 > URL: https://issues.apache.org/jira/browse/HBASE-23245 > Project: HBase > Issue Type: Improvement > Components: metrics >Affects Versions: 3.0.0, 2.3.0, 1.6.0 >Reporter: Viraj Jasani >Assignee: Viraj Jasani >Priority: Major > Fix For: 3.0.0, 2.3.0, 1.6.0, 1.4.12, 2.1.8, 2.2.3 > > > MutableHistogram is using HistogramImpl() and not using maxExpected. From all > implementation classes, maxExpected should be removed as constructor > argument. Also, HistogramImpl() should pass long casting for > Integer.MAX_VALUE << 2 else it is treated as -4 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23245) All MutableHistogram implementations should remove maxExpected
[ https://issues.apache.org/jira/browse/HBASE-23245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16971745#comment-16971745 ] Guangxu Cheng commented on HBASE-23245: --- Pushed to all branch. Thank [~vjasani] for contributing. > All MutableHistogram implementations should remove maxExpected > -- > > Key: HBASE-23245 > URL: https://issues.apache.org/jira/browse/HBASE-23245 > Project: HBase > Issue Type: Improvement > Components: metrics >Affects Versions: 3.0.0, 2.3.0, 1.6.0 >Reporter: Viraj Jasani >Assignee: Viraj Jasani >Priority: Major > Fix For: 3.0.0, 2.3.0, 1.6.0 > > > MutableHistogram is using HistogramImpl() and not using maxExpected. From all > implementation classes, maxExpected should be removed as constructor > argument. Also, HistogramImpl() should pass long casting for > Integer.MAX_VALUE << 2 else it is treated as -4 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-23074) scan#setVersion is invalid.
[
https://issues.apache.org/jira/browse/HBASE-23074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guangxu Cheng resolved HBASE-23074.
---
Resolution: Duplicate
> scan#setVersion is invalid.
> ---
>
> Key: HBASE-23074
> URL: https://issues.apache.org/jira/browse/HBASE-23074
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.1.1, master
>Reporter: Bo Cui
>Priority: Critical
> Attachments: image-2019-09-25-16-45-08-870.png,
> image-2019-09-25-16-45-37-780.png
>
>
> I found a problem, it could be a mistake..
> reproduce steps in hbase shell:
> 1. create 't11', \{NAME => 'f1', VERSIONS => 1}
> 2.put 't11','r1','f1:q1','f1'
> 3.flush 't11'
> 4.put 't11','r1','f1:q1','f2'
> 5.flush 't11'
> 6.scan 't11', \{RAW => true, VERSIONS => 10, FILTER => "(QualifierFilter (>=,
> 'binary:f1'))"}
>
> the result:
> 1. 1.3.1 version
> hbase(main):011:0> scan 't11', \{RAW => true, VERSIONS => 10, FILTER =>
> "(QualifierFilter (>=, 'binary:q1'))"}
> ROW COLUMN+CELL
> r1 column=f1:q1, timestamp=1569400085570, value=f2
> r1 column=f1:q1, timestamp=1569400068958, value=f1
> 2. in 2.1.1 version
> hbase(main):023:0> scan 't11', \{RAW => true, VERSIONS => 10, FILTER =>
> "(QualifierFilter (>=, 'binary:q1'))"}
> ROW COLUMN+CELL
> r1 column=f1:q1, timestamp=1569400122280, value=f2
> 1 row(s)
> Took 0.0800 seconds
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23074) scan#setVersion is invalid.
[
https://issues.apache.org/jira/browse/HBASE-23074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16971581#comment-16971581
]
Guangxu Cheng commented on HBASE-23074:
---
Duplicate of HBASE-22710
> scan#setVersion is invalid.
> ---
>
> Key: HBASE-23074
> URL: https://issues.apache.org/jira/browse/HBASE-23074
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.1.1, master
>Reporter: Bo Cui
>Priority: Critical
> Attachments: image-2019-09-25-16-45-08-870.png,
> image-2019-09-25-16-45-37-780.png
>
>
> I found a problem, it could be a mistake..
> reproduce steps in hbase shell:
> 1. create 't11', \{NAME => 'f1', VERSIONS => 1}
> 2.put 't11','r1','f1:q1','f1'
> 3.flush 't11'
> 4.put 't11','r1','f1:q1','f2'
> 5.flush 't11'
> 6.scan 't11', \{RAW => true, VERSIONS => 10, FILTER => "(QualifierFilter (>=,
> 'binary:f1'))"}
>
> the result:
> 1. 1.3.1 version
> hbase(main):011:0> scan 't11', \{RAW => true, VERSIONS => 10, FILTER =>
> "(QualifierFilter (>=, 'binary:q1'))"}
> ROW COLUMN+CELL
> r1 column=f1:q1, timestamp=1569400085570, value=f2
> r1 column=f1:q1, timestamp=1569400068958, value=f1
> 2. in 2.1.1 version
> hbase(main):023:0> scan 't11', \{RAW => true, VERSIONS => 10, FILTER =>
> "(QualifierFilter (>=, 'binary:q1'))"}
> ROW COLUMN+CELL
> r1 column=f1:q1, timestamp=1569400122280, value=f2
> 1 row(s)
> Took 0.0800 seconds
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (HBASE-23237) Negative 'Requests per Second' counts in UI
[ https://issues.apache.org/jira/browse/HBASE-23237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16971502#comment-16971502 ] Guangxu Cheng edited comment on HBASE-23237 at 11/11/19 1:02 PM: - Agree with what [~zhangduo] said, calculating the delta of each region is a better choice, the result obtained in this way is also more accurate. was (Author: andrewcheng): As [~zhangduo] said, calculating the delta of each region is a better choice, the result obtained in this way is also more accurate. > Negative 'Requests per Second' counts in UI > --- > > Key: HBASE-23237 > URL: https://issues.apache.org/jira/browse/HBASE-23237 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 2.2.2 >Reporter: Michael Stack >Assignee: Karthik Palanisamy >Priority: Major > Attachments: Screen Shot 2019-10-30 at 9.45.58 PM.png > > > I see request per second showing with negative sign. > !Screen Shot 2019-10-30 at 9.45.58 PM.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23237) Negative 'Requests per Second' counts in UI
[ https://issues.apache.org/jira/browse/HBASE-23237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16971502#comment-16971502 ] Guangxu Cheng commented on HBASE-23237: --- As [~zhangduo] said, calculating the delta of each region is a better choice, the result obtained in this way is also more accurate. > Negative 'Requests per Second' counts in UI > --- > > Key: HBASE-23237 > URL: https://issues.apache.org/jira/browse/HBASE-23237 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 2.2.2 >Reporter: Michael Stack >Assignee: Karthik Palanisamy >Priority: Major > Attachments: Screen Shot 2019-10-30 at 9.45.58 PM.png > > > I see request per second showing with negative sign. > !Screen Shot 2019-10-30 at 9.45.58 PM.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23278) Add a table-level compaction progress display on the UI
[ https://issues.apache.org/jira/browse/HBASE-23278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16971493#comment-16971493 ] Guangxu Cheng commented on HBASE-23278: --- !image-2019-11-11-20-44-04-050.png|width=691,height=73! As shown in the above figure, more and more metrics are displayed, the colums of the table is also increasing, which is very difficult to read. so maybe we can use multiple tabs to show metrics, just like the regionserver page shows all metrics of regions. > Add a table-level compaction progress display on the UI > > > Key: HBASE-23278 > URL: https://issues.apache.org/jira/browse/HBASE-23278 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 1.6.0, master >Reporter: Baiqiang Zhao >Assignee: Baiqiang Zhao >Priority: Minor > Attachments: HBase-23278.png, image-2019-11-11-20-35-56-103.png, > image-2019-11-11-20-37-53-367.png, image-2019-11-11-20-44-04-050.png > > > We have regionserver-level compaction progress in UI. However, we often > compact a table, why there is no table-level compaction progress？ > !HBase-23278.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23278) Add a table-level compaction progress display on the UI
[ https://issues.apache.org/jira/browse/HBASE-23278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-23278: -- Attachment: image-2019-11-11-20-44-04-050.png > Add a table-level compaction progress display on the UI > > > Key: HBASE-23278 > URL: https://issues.apache.org/jira/browse/HBASE-23278 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 1.6.0, master >Reporter: Baiqiang Zhao >Assignee: Baiqiang Zhao >Priority: Minor > Attachments: HBase-23278.png, image-2019-11-11-20-35-56-103.png, > image-2019-11-11-20-37-53-367.png, image-2019-11-11-20-44-04-050.png > > > We have regionserver-level compaction progress in UI. However, we often > compact a table, why there is no table-level compaction progress？ > !HBase-23278.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23278) Add a table-level compaction progress display on the UI
[ https://issues.apache.org/jira/browse/HBASE-23278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-23278: -- Attachment: image-2019-11-11-20-37-53-367.png > Add a table-level compaction progress display on the UI > > > Key: HBASE-23278 > URL: https://issues.apache.org/jira/browse/HBASE-23278 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 1.6.0, master >Reporter: Baiqiang Zhao >Assignee: Baiqiang Zhao >Priority: Minor > Attachments: HBase-23278.png, image-2019-11-11-20-35-56-103.png, > image-2019-11-11-20-37-53-367.png > > > We have regionserver-level compaction progress in UI. However, we often > compact a table, why there is no table-level compaction progress？ > !HBase-23278.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23278) Add a table-level compaction progress display on the UI
[ https://issues.apache.org/jira/browse/HBASE-23278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-23278: -- Attachment: image-2019-11-11-20-35-56-103.png > Add a table-level compaction progress display on the UI > > > Key: HBASE-23278 > URL: https://issues.apache.org/jira/browse/HBASE-23278 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 1.6.0, master >Reporter: Baiqiang Zhao >Assignee: Baiqiang Zhao >Priority: Minor > Attachments: HBase-23278.png, image-2019-11-11-20-35-56-103.png > > > We have regionserver-level compaction progress in UI. However, we often > compact a table, why there is no table-level compaction progress？ > !HBase-23278.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23274) Remove auto generated files by thrift from project
[ https://issues.apache.org/jira/browse/HBASE-23274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16971153#comment-16971153 ] Guangxu Cheng commented on HBASE-23274: --- Yes, we should find a suitable maven plugin. I think it's good to remove these auto-generated files. In the header of the auto-generated file contains the generation date of the file. when the thrift definition file is changed, the header of the regenerated file will also change, although the contents of some files have not changed, we still need to update these files to the remote warehouse, which is rather disturbing. > Remove auto generated files by thrift from project > -- > > Key: HBASE-23274 > URL: https://issues.apache.org/jira/browse/HBASE-23274 > Project: HBase > Issue Type: Improvement >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > > Now we have added auto generated files by thrift in the project, and we will > regenerate these files whenever we add interfaces. It might be better to > generate these files automatically at compile time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23273) Table header is not correct on table.jsp when table name is hbase:meta
[ https://issues.apache.org/jira/browse/HBASE-23273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-23273: -- Fix Version/s: 1.4.12 1.6.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Table header is not correct on table.jsp when table name is hbase:meta > -- > > Key: HBASE-23273 > URL: https://issues.apache.org/jira/browse/HBASE-23273 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 1.4.11 >Reporter: Baiqiang Zhao >Assignee: Baiqiang Zhao >Priority: Minor > Fix For: 1.6.0, 1.4.12 > > Attachments: HBASE-23273.branch-1.0001.patch, WX20191107-161810.png > > > When viewing table.jsp?name=hbase:meta, the table header in "Table Regions" > is not correct. As shown in the figure below: > !WX20191107-161810.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (HBASE-23273) Table header is not correct on table.jsp when table name is hbase:meta
[ https://issues.apache.org/jira/browse/HBASE-23273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16971124#comment-16971124 ] Guangxu Cheng edited comment on HBASE-23273 at 11/10/19 1:10 PM: - Manually apply the patch, verification passed. Pushed to branch-1 and branch-1.4 Thank [~DeanZ] for you contributing. was (Author: andrewcheng): Manually apply the patch, verification passed. Pushed to branch-1 and branch-1.4 > Table header is not correct on table.jsp when table name is hbase:meta > -- > > Key: HBASE-23273 > URL: https://issues.apache.org/jira/browse/HBASE-23273 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 1.4.11 >Reporter: Baiqiang Zhao >Assignee: Baiqiang Zhao >Priority: Minor > Attachments: HBASE-23273.branch-1.0001.patch, WX20191107-161810.png > > > When viewing table.jsp?name=hbase:meta, the table header in "Table Regions" > is not correct. As shown in the figure below: > !WX20191107-161810.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23273) Table header is not correct on table.jsp when table name is hbase:meta
[ https://issues.apache.org/jira/browse/HBASE-23273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16971124#comment-16971124 ] Guangxu Cheng commented on HBASE-23273: --- Manually apply the patch, verification passed. Pushed to branch-1 and branch-1.4 > Table header is not correct on table.jsp when table name is hbase:meta > -- > > Key: HBASE-23273 > URL: https://issues.apache.org/jira/browse/HBASE-23273 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 1.4.11 >Reporter: Baiqiang Zhao >Assignee: Baiqiang Zhao >Priority: Minor > Attachments: HBASE-23273.branch-1.0001.patch, WX20191107-161810.png > > > When viewing table.jsp?name=hbase:meta, the table header in "Table Regions" > is not correct. As shown in the figure below: > !WX20191107-161810.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HBASE-23274) Remove auto generated files by thrift from project
[ https://issues.apache.org/jira/browse/HBASE-23274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng reassigned HBASE-23274: - Assignee: Guangxu Cheng > Remove auto generated files by thrift from project > -- > > Key: HBASE-23274 > URL: https://issues.apache.org/jira/browse/HBASE-23274 > Project: HBase > Issue Type: Bug >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > > Now we have added auto generated files by thrift in the project, and we will > regenerate these files whenever we add interfaces. It might be better to > generate these files automatically at compile time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23274) Remove auto generated files by thrift from project
[ https://issues.apache.org/jira/browse/HBASE-23274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-23274: -- Description: Now we have added auto generated files by thrift in the project, and we will regenerate these files whenever we add interfaces. It might be better to generate these files automatically at compile time. > Remove auto generated files by thrift from project > -- > > Key: HBASE-23274 > URL: https://issues.apache.org/jira/browse/HBASE-23274 > Project: HBase > Issue Type: Bug >Reporter: Guangxu Cheng >Priority: Major > > Now we have added auto generated files by thrift in the project, and we will > regenerate these files whenever we add interfaces. It might be better to > generate these files automatically at compile time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-23274) Remove auto generated files by thrift from project
Guangxu Cheng created HBASE-23274: - Summary: Remove auto generated files by thrift from project Key: HBASE-23274 URL: https://issues.apache.org/jira/browse/HBASE-23274 Project: HBase Issue Type: Bug Reporter: Guangxu Cheng -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-20395) Displaying thrift server type on the thrift page
[ https://issues.apache.org/jira/browse/HBASE-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16970160#comment-16970160 ] Guangxu Cheng commented on HBASE-20395: --- Create a new PR: [https://github.com/apache/hbase/pull/808] > Displaying thrift server type on the thrift page > > > Key: HBASE-20395 > URL: https://issues.apache.org/jira/browse/HBASE-20395 > Project: HBase > Issue Type: Improvement > Components: Thrift >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > Attachments: HBASE-20395.master.001.patch, > HBASE-20395.master.002.patch, HBASE-20395.master.003.patch, > HBASE-20395.master.004.patch, HBASE-20395.master.005.patch, > HBASE-20395.master.005.patch, result.png > > > HBase supports two types of thrift server: thrift and thrift2. > But after start the thrift server successfully, we can not get the thrift > server type conveniently. > So, displaying thrift server type on the thrift page may provide some > convenience for the users. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23260) Table metrics no longer update once a new table is created
[ https://issues.apache.org/jira/browse/HBASE-23260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated HBASE-23260: -- Attachment: HBASE-23260-branch-2.2.patch > Table metrics no longer update once a new table is created > --- > > Key: HBASE-23260 > URL: https://issues.apache.org/jira/browse/HBASE-23260 > Project: HBase > Issue Type: Bug > Components: metrics >Affects Versions: 2.2.1 >Reporter: xinxin fan >Assignee: xinxin fan >Priority: Major > Attachments: 111.png, HBASE-23260-branch-2.2.patch, > HBASE-23260-branch-2.2.patch > > > Once a new table is created, the thread > MetricsTableWrapperAggregateImpl$TableMetricsWrapperRunnable will no longer > work as a java.util.NoSuchElementException is throwed. The details as > follows: > !111.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23260) Table metrics no longer update once a new table is created
[ https://issues.apache.org/jira/browse/HBASE-23260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16968923#comment-16968923 ] Guangxu Cheng commented on HBASE-23260: --- Re-submit the patch in order to trigger HBase QA > Table metrics no longer update once a new table is created > --- > > Key: HBASE-23260 > URL: https://issues.apache.org/jira/browse/HBASE-23260 > Project: HBase > Issue Type: Bug > Components: metrics >Affects Versions: 2.2.1 >Reporter: xinxin fan >Assignee: xinxin fan >Priority: Major > Attachments: 111.png, HBASE-23260-branch-2.2.patch, > HBASE-23260-branch-2.2.patch > > > Once a new table is created, the thread > MetricsTableWrapperAggregateImpl$TableMetricsWrapperRunnable will no longer > work as a java.util.NoSuchElementException is throwed. The details as > follows: > !111.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-22980) HRegionPartioner getPartition() method incorrectly partitions the regions of the table.
[
https://issues.apache.org/jira/browse/HBASE-22980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guangxu Cheng resolved HBASE-22980.
---
Fix Version/s: 2.2.3
2.1.8
2.3.0
3.0.0
Resolution: Fixed
> HRegionPartioner getPartition() method incorrectly partitions the regions of
> the table.
> ---
>
> Key: HBASE-22980
> URL: https://issues.apache.org/jira/browse/HBASE-22980
> Project: HBase
> Issue Type: Bug
> Components: mapreduce
>Reporter: Shardul Singh
>Assignee: Shardul Singh
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.1.8, 2.2.3
>
>
> *Problem:*
> Partitioner class HRegionPartitioner in a HBase MapReduce job has a method
> getPartition(). In getPartition(), there is a scenario where we have check
> for less number of reducers than region. This scenario seems incorrect
> because for a rowKey present in last region(let us say nth region) ,
> getPartition() should return value (n-1). But it is not returning n-1 for the
> last region as it is falling in the case where number of reducers < number of
> regions and returning some random value.
> So if a client uses this class as a partitioner class in HBase MapReduce
> jobs, this method incorrectly partitions the regions because rowKeys present
> in the last regions does not fall to the last region.
> [https://github.com/apache/hbase/blob/fbd5b5e32753104f88600b0f4c803ab5659bce64/hbase-mapreduce/src/main/java/org/apache/hadoop/hbase/mapreduce/HRegionPartitioner.java#L92]
> Consider the following scenario:
> if there are 5 regions for the table, partitions = 5 and number of reducers
> is also 5.
> So in this case above check for reducers < regions should not return true.
> But for the last region when i=4(last region, 5th region) , getPartition
> should return 4 but it returns 2 because it falls in the case of when we have
> less reduces than region and returns true for the above condition even though
> we have reducers = regions. So the condition is incorrect.
>
> *Solution:*
> Instead of
> {code} if (i >= numPartitions-1) {code}
> It should be
>{code} if (i >= numPartitions){ {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-22980) HRegionPartioner getPartition() method incorrectly partitions the regions of the table.
[
https://issues.apache.org/jira/browse/HBASE-22980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16968863#comment-16968863
]
Guangxu Cheng commented on HBASE-22980:
---
Pushed to branch-2.1+. Thank [~shardulsingh] for contributing.
> HRegionPartioner getPartition() method incorrectly partitions the regions of
> the table.
> ---
>
> Key: HBASE-22980
> URL: https://issues.apache.org/jira/browse/HBASE-22980
> Project: HBase
> Issue Type: Bug
> Components: mapreduce
>Reporter: Shardul Singh
>Assignee: Shardul Singh
>Priority: Major
>
> *Problem:*
> Partitioner class HRegionPartitioner in a HBase MapReduce job has a method
> getPartition(). In getPartition(), there is a scenario where we have check
> for less number of reducers than region. This scenario seems incorrect
> because for a rowKey present in last region(let us say nth region) ,
> getPartition() should return value (n-1). But it is not returning n-1 for the
> last region as it is falling in the case where number of reducers < number of
> regions and returning some random value.
> So if a client uses this class as a partitioner class in HBase MapReduce
> jobs, this method incorrectly partitions the regions because rowKeys present
> in the last regions does not fall to the last region.
> [https://github.com/apache/hbase/blob/fbd5b5e32753104f88600b0f4c803ab5659bce64/hbase-mapreduce/src/main/java/org/apache/hadoop/hbase/mapreduce/HRegionPartitioner.java#L92]
> Consider the following scenario:
> if there are 5 regions for the table, partitions = 5 and number of reducers
> is also 5.
> So in this case above check for reducers < regions should not return true.
> But for the last region when i=4(last region, 5th region) , getPartition
> should return 4 but it returns 2 because it falls in the case of when we have
> less reduces than region and returns true for the above condition even though
> we have reducers = regions. So the condition is incorrect.
>
> *Solution:*
> Instead of
> {code} if (i >= numPartitions-1) {code}
> It should be
>{code} if (i >= numPartitions){ {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-20395) Displaying thrift server type on the thrift page
[ https://issues.apache.org/jira/browse/HBASE-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16965603#comment-16965603 ] Guangxu Cheng commented on HBASE-20395: --- the patch can't apply to master now. let me rebase and generate another patch for it. > Displaying thrift server type on the thrift page > > > Key: HBASE-20395 > URL: https://issues.apache.org/jira/browse/HBASE-20395 > Project: HBase > Issue Type: Improvement > Components: Thrift >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > Attachments: HBASE-20395.master.001.patch, > HBASE-20395.master.002.patch, HBASE-20395.master.003.patch, > HBASE-20395.master.004.patch, HBASE-20395.master.005.patch, > HBASE-20395.master.005.patch, result.png > > > HBase supports two types of thrift server: thrift and thrift2. > But after start the thrift server successfully, we can not get the thrift > server type conveniently. > So, displaying thrift server type on the thrift page may provide some > convenience for the users. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23237) Negative 'Requests per Second' counts in UI
[ https://issues.apache.org/jira/browse/HBASE-23237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16963705#comment-16963705 ] Guangxu Cheng commented on HBASE-23237: --- I don't have a good idea now. Maybe shown as "0" or "NaN" or "llegal"? > Negative 'Requests per Second' counts in UI > --- > > Key: HBASE-23237 > URL: https://issues.apache.org/jira/browse/HBASE-23237 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 2.2.2 >Reporter: Michael Stack >Priority: Major > Attachments: Screen Shot 2019-10-30 at 9.45.58 PM.png > > > I see request per second showing with negative sign. > !Screen Shot 2019-10-30 at 9.45.58 PM.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23237) Negative 'Requests per Second' counts in UI
[ https://issues.apache.org/jira/browse/HBASE-23237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16963659#comment-16963659 ] Guangxu Cheng commented on HBASE-23237: --- Hi, sir. In HBASE-20626, we use "totalRowActionRequestCount" instead of "totalRequestCount" to calculate RPS. When the region is moved, the QPS may have a negative number. Because the value of "totalRowActionRequestCount" is sum of the request count of all regions on this RegionServer. When the region is moved to other RegionServer, the current value of "totalRowActionRequestCount" may be smaller than the last time. > Negative 'Requests per Second' counts in UI > --- > > Key: HBASE-23237 > URL: https://issues.apache.org/jira/browse/HBASE-23237 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 2.2.2 >Reporter: Michael Stack >Priority: Major > Attachments: Screen Shot 2019-10-30 at 9.45.58 PM.png > > > I see request per second showing with negative sign. > !Screen Shot 2019-10-30 at 9.45.58 PM.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23232) Remove rsgroup profile from pom.xml of hbase-assembly
[ https://issues.apache.org/jira/browse/HBASE-23232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16963570#comment-16963570 ] Guangxu Cheng commented on HBASE-23232: --- Sir, it's ok to push this to branch HBASE-22514 only . The parent issue is for 3.0.0. > Remove rsgroup profile from pom.xml of hbase-assembly > - > > Key: HBASE-23232 > URL: https://issues.apache.org/jira/browse/HBASE-23232 > Project: HBase > Issue Type: Sub-task > Components: build, rsgroup >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > Fix For: HBASE-22514 > > > branch HBASE-22514 built failed -- This message was sent by Atlassian Jira (v8.3.4#803005)
