[jira] [Resolved] (HBASE-25766) Introduce RegionSplitRestriction that restricts the pattern of the split point
[ https://issues.apache.org/jira/browse/HBASE-25766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-25766. -- Hadoop Flags: Reviewed Resolution: Fixed > Introduce RegionSplitRestriction that restricts the pattern of the split point > -- > > Key: HBASE-25766 > URL: https://issues.apache.org/jira/browse/HBASE-25766 > Project: HBase > Issue Type: Improvement >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.3 > > > As discussed in HBASE-25706, we can introduce RegionSplitRestriction that > restricts the pattern of the split point. > See the following comment for the details: > https://issues.apache.org/jira/browse/HBASE-25706?focusedCommentId=17310190=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17310190 > CC: [~zhangduo] [~stack] -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [VOTE] Merge branch HBASE-22120 back to master
+1, skimmed through the patch. Thanks for putting this together. On Tue, Apr 20, 2021 at 10:06 PM Tak-Lon (Stephen) Wu wrote: > +1 (non-binding) > > This is a great integration, thanks Duo. > > -Stephen > > On Tue, Apr 20, 2021 at 9:53 PM Pankaj Kumar > wrote: > > > > +1(non-binding) > > > > Regards, > > Pankaj > > > > On Tue, Apr 20, 2021, 8:28 AM 张铎(Duo Zhang) > wrote: > > > > > HBASE-22120 aims to use OpenTelemetry to replace HTrace and bring > tracing > > > back to HBase. > > > > > > The discusson thread: > > > > > > > > > > https://lists.apache.org/thread.html/r31a147c184e379681987b536685db4260af16bbcb0f047ec966b22d5%40%3Cdev.hbase.apache.org%3E > > > > > > The PR > > > > > > https://github.com/apache/hbase/pull/2901 > > > > > > Please vote: > > > [+1] Agree > > > [0] Neutral > > > [-1] Disagree (please include actionable feedback) > > > > > > Thanks. > > > >
[jira] [Resolved] (HBASE-25798) typo in MetricsAssertHelper
[ https://issues.apache.org/jira/browse/HBASE-25798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-25798. --- Hadoop Flags: Reviewed Resolution: Fixed Pushed to branch-2.3+. Thanks [~DeanZ] for contributing. > typo in MetricsAssertHelper > --- > > Key: HBASE-25798 > URL: https://issues.apache.org/jira/browse/HBASE-25798 > Project: HBase > Issue Type: Improvement >Affects Versions: 3.0.0-alpha-1, 2.5.0 >Reporter: Baiqiang Zhao >Assignee: Baiqiang Zhao >Priority: Minor > Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.3, 2.3.6 > > > "boolean true id counter metric exists." -> "boolean true if counter metric > exists." -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: JDK version issue during doing 1.7.0 release
Thanks Andrew! Let me try the 1st first which seems the easiest, 2nd seems much works but worth a try if I fail in the 1st. The 3rd should be the final compromise. -- Best Regards, R.C On Wed, Apr 21, 2021 at 12:34 AM Andrew Purtell wrote: > In my opinion we have a few reasonable options, especially considering this > is the last release from branch-1. > > 1. Make the hbase-thrift module's activation contingent of compilation with > a Java 8+ JDK. Here's an example of how to do that: > https://github.com/apache/hbase/pull/251 ( > > https://github.com/apache/hbase/pull/251/files#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8 > ) > . Dependencies in other modules (like hbase-assembly) would need to be made > optional. Downside here is our official release will not provide > hbase-thrift artifacts to Maven as all others did. Users who want > hbase-thrift would need to recompile with Java 8+ locally. > > 2. Compile the fixed Thrift version ourselves with Java 7 and shade the > result into a org.apache.hbase.thirdparty namespace, release this new > hbase-shaded-thrift, then update branch-1 POMs to depend on this artifact > instead. All of the import statements in the generated files in > hbase-thrift/src/ will need updating too, but we'd only need to do that > once since this is the end of the road and generating them again seems > unlikely. We would continue to release hbase-thrift, and, bonus, it won't > conflict with any other thrift libraries on the user classpath. > > 3. Ignore this issue and keep the version of the Thrift dependency in > branch-1 to a version that is still compatible with Java 7. We would also > continue to release hbase-thrift but we should advise in release notes > about the known CVEs. > > The question really falls to Reid... How much work do you want to do ? What > seems like a reasonable compromise? > > > > > On Tue, Apr 13, 2021 at 12:35 AM Reid Chan wrote: > > > Hi team and community: > > > > This is the error message when I tried to make a release 1.7.0: > > > > [INFO] Restricted to JDK 1.7 yet > > org.apache.thrift:libthrift:jar:0.13.0:compile contains > > org/apache/thrift/TNonblockingMultiFetchClient.class targeted to JDK 1.8 > > HBase has unsupported dependencies. > > HBase requires that all dependencies be compiled with version 1.7 or > > earlier > > of the JDK to properly build from source. You appear to be using a > newer > > dependency. You can use > > either "mvn -version" or "mvn enforcer:display-info" to verify what > > version is active. > > Non-release builds can temporarily build with a newer JDK version by > > setting the > > 'compileSource' property (eg. mvn -DcompileSource=1.8 clean package). > > Found Banned Dependency: org.apache.thrift:libthrift:jar:0.13.0 > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce > > (enforce-maven-version) on project hbase-thrift: Some Enforcer rules have > > failed. Look above for specific messages explaining why the rule failed. > -> > > [Help 1] > > [ERROR] > > [ERROR] To see the full stack trace of the errors, re-run Maven with the > -e > > switch. > > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > > [ERROR] > > [ERROR] For more information about the errors and possible solutions, > > please read the following articles: > > [ERROR] [Help 1] > > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > > [ERROR] > > [ERROR] After correcting the problems, you can resume the build with the > > command > > [ERROR] mvn -rf :hbase-thrift > > > > > > This happened at Thrift module, it seems that thrift-0.13.0 is targeted > to > > JDK 1.8, but I need to use JDK 7 to do the release. > > > > Thus I couldn't run the make_rc.sh successfully, any hints or experiences > > about how to resolve this? > > > > > > -- > > Best Regards, > > R.C > > > > > -- > Best regards, > Andrew > > Words like orphans lost among the crosstalk, meaning torn from truth's > decrepit hands >- A23, Crosstalk >
[jira] [Created] (HBASE-25800) RegionMover tool reassigning the already opened regions
chiranjeevi created HBASE-25800:
---
Summary: RegionMover tool reassigning the already opened regions
Key: HBASE-25800
URL: https://issues.apache.org/jira/browse/HBASE-25800
Project: HBase
Issue Type: Bug
Reporter: chiranjeevi
{color:#00}{color:#00}Steps:
1)Install cluster with 3 RS (RS1,RS2,RS3)
2)Create table with 1000 regions
3)Perform RegionMover to unload from RS1
4)While unloading the regions stop RS1
Observation:
{color}{color}
{color:#00}Regions already asigned to RS2 or RS3(by SCP) getting reassigned
by the tool{color}
{color:#00}2021-03-17 15:08:15,484 INFO [pool-3-thread-1] util.RegionMover:
Moved Region table1,user25612,1615963232549.b19f9a6dac88a1fa21191c9fd0d515aa.
cost:2.485
2021-03-17 15:08:16,663 INFO [pool-3-thread-1] util.RegionMover: Moving
region:b19f9a6dac88a1fa21191c9fd0d515aa from RS1,16040,1615810740162 to
RS2,16040,1615810791637{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-25799) add clusterReadRequests and clusterWriteRequests jmx
xijiawen created HBASE-25799: Summary: add clusterReadRequests and clusterWriteRequests jmx Key: HBASE-25799 URL: https://issues.apache.org/jira/browse/HBASE-25799 Project: HBase Issue Type: Improvement Reporter: xijiawen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-25763) TestRSGroupsWithACL.setupBeforeClass is flaky
[ https://issues.apache.org/jira/browse/HBASE-25763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yulin Niu resolved HBASE-25763. --- Resolution: Fixed > TestRSGroupsWithACL.setupBeforeClass is flaky > - > > Key: HBASE-25763 > URL: https://issues.apache.org/jira/browse/HBASE-25763 > Project: HBase > Issue Type: Improvement >Reporter: Xiaolin Ha >Assignee: Xiaolin Ha >Priority: Major > Attachments: error-logs > > > [ERROR] Failures: [ERROR] > TestRSGroupsWithACL.setupBeforeClass:136->SecureTestUtil.grantGlobal:345->SecureTestUtil.updateACLs:313 > Waiting timed out after [10,000] msec > *[https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3025/8/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt]* > -- This message was sent by Atlassian Jira (v8.3.4#803005)
