[jira] [Commented] (HBASE-23295) hbase-connectors HBaseContext should use most recent delegation token
[ https://issues.apache.org/jira/browse/HBASE-23295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17058998#comment-17058998 ] Sakthi commented on HBASE-23295: Closing out the jira. > hbase-connectors HBaseContext should use most recent delegation token > - > > Key: HBASE-23295 > URL: https://issues.apache.org/jira/browse/HBASE-23295 > Project: HBase > Issue Type: Bug > Components: hbase-connectors >Affects Versions: connector-1.0.0 >Reporter: István Adamcsik >Assignee: István Adamcsik >Priority: Major > Fix For: connector-1.0.1 > > Attachments: HBASE-23295.patch > > > For a long-running HBaseContext, it keeps referring to the persisting > credential instead of the most recent token. This would cause the Spark job > failed due to "token has expired" issue if the HBaseContext's lifetime is > longer than the token's lifetime. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-23295) hbase-connectors HBaseContext should use most recent delegation token
[ https://issues.apache.org/jira/browse/HBASE-23295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi resolved HBASE-23295. Resolution: Fixed > hbase-connectors HBaseContext should use most recent delegation token > - > > Key: HBASE-23295 > URL: https://issues.apache.org/jira/browse/HBASE-23295 > Project: HBase > Issue Type: Bug > Components: hbase-connectors >Affects Versions: connector-1.0.0 >Reporter: István Adamcsik >Assignee: István Adamcsik >Priority: Major > Fix For: connector-1.0.1 > > Attachments: HBASE-23295.patch > > > For a long-running HBaseContext, it keeps referring to the persisting > credential instead of the most recent token. This would cause the Spark job > failed due to "token has expired" issue if the HBaseContext's lifetime is > longer than the token's lifetime. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23295) hbase-connectors HBaseContext should use most recent delegation token
[ https://issues.apache.org/jira/browse/HBASE-23295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-23295: --- Fix Version/s: connector-1.0.1 > hbase-connectors HBaseContext should use most recent delegation token > - > > Key: HBASE-23295 > URL: https://issues.apache.org/jira/browse/HBASE-23295 > Project: HBase > Issue Type: Bug > Components: hbase-connectors >Affects Versions: connector-1.0.0 >Reporter: István Adamcsik >Assignee: István Adamcsik >Priority: Major > Fix For: connector-1.0.1 > > Attachments: HBASE-23295.patch > > > For a long-running HBaseContext, it keeps referring to the persisting > credential instead of the most recent token. This would cause the Spark job > failed due to "token has expired" issue if the HBaseContext's lifetime is > longer than the token's lifetime. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-23743) Release 1.4.13
[ https://issues.apache.org/jira/browse/HBASE-23743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi resolved HBASE-23743. Resolution: Fixed > Release 1.4.13 > -- > > Key: HBASE-23743 > URL: https://issues.apache.org/jira/browse/HBASE-23743 > Project: HBase > Issue Type: Task > Components: build, community >Affects Versions: 1.4.13 >Reporter: Sean Busbey >Assignee: Sakthi >Priority: Major > Fix For: 1.4.13 > > > over due for 1.4.13. I'll try to use the release manager scripts this time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23743) Release 1.4.13
[ https://issues.apache.org/jira/browse/HBASE-23743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052708#comment-17052708 ] Sakthi commented on HBASE-23743: Closing out the Jira as the announcement has been done. > Release 1.4.13 > -- > > Key: HBASE-23743 > URL: https://issues.apache.org/jira/browse/HBASE-23743 > Project: HBase > Issue Type: Task > Components: build, community >Affects Versions: 1.4.13 >Reporter: Sean Busbey >Assignee: Sakthi >Priority: Major > Fix For: 1.4.13 > > > over due for 1.4.13. I'll try to use the release manager scripts this time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-22827) Expose multi-region merge in shell and Admin API
[ https://issues.apache.org/jira/browse/HBASE-22827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-22827: --- Fix Version/s: 2.1.10 > Expose multi-region merge in shell and Admin API > > > Key: HBASE-22827 > URL: https://issues.apache.org/jira/browse/HBASE-22827 > Project: HBase > Issue Type: Improvement > Components: Admin, shell >Reporter: Michael Stack >Assignee: Sakthi >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.2.4, 2.1.10 > > Attachments: hbase-22827.branch-2.001.patch > > > HBASE-22777 adds being able to merge more than two regions at once. It is > only available internally currently for use by hbck2 doing fixup of overlaps > in hbase:meta. This issue is about exposing it via the Admin Interface and in > turn, via the shell. Probably best if old two region merge method is > deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-22827) Expose multi-region merge in shell and Admin API
[ https://issues.apache.org/jira/browse/HBASE-22827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052707#comment-17052707 ] Sakthi commented on HBASE-22827: Sorry for the delay [~zghao]. Have updated the RN. > Expose multi-region merge in shell and Admin API > > > Key: HBASE-22827 > URL: https://issues.apache.org/jira/browse/HBASE-22827 > Project: HBase > Issue Type: Improvement > Components: Admin, shell >Reporter: Michael Stack >Assignee: Sakthi >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.2.4 > > Attachments: hbase-22827.branch-2.001.patch > > > HBASE-22777 adds being able to merge more than two regions at once. It is > only available internally currently for use by hbck2 doing fixup of overlaps > in hbase:meta. This issue is about exposing it via the Admin Interface and in > turn, via the shell. Probably best if old two region merge method is > deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-22827) Expose multi-region merge in shell and Admin API
[ https://issues.apache.org/jira/browse/HBASE-22827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi resolved HBASE-22827. Resolution: Fixed > Expose multi-region merge in shell and Admin API > > > Key: HBASE-22827 > URL: https://issues.apache.org/jira/browse/HBASE-22827 > Project: HBase > Issue Type: Improvement > Components: Admin, shell >Reporter: Michael Stack >Assignee: Sakthi >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.2.4 > > Attachments: hbase-22827.branch-2.001.patch > > > HBASE-22777 adds being able to merge more than two regions at once. It is > only available internally currently for use by hbck2 doing fixup of overlaps > in hbase:meta. This issue is about exposing it via the Admin Interface and in > turn, via the shell. Probably best if old two region merge method is > deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-22827) Expose multi-region merge in shell and Admin API
[ https://issues.apache.org/jira/browse/HBASE-22827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-22827: --- Release Note: merge_region shell command can now be used to merge more than 2 regions as well. It takes a list of regions as comma separated values or as an array of regions, and not just 2 regions. The full regionnames and encoded regionnames are continued to be accepted. > Expose multi-region merge in shell and Admin API > > > Key: HBASE-22827 > URL: https://issues.apache.org/jira/browse/HBASE-22827 > Project: HBase > Issue Type: Improvement > Components: Admin, shell >Reporter: Michael Stack >Assignee: Sakthi >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.2.4 > > Attachments: hbase-22827.branch-2.001.patch > > > HBASE-22777 adds being able to merge more than two regions at once. It is > only available internally currently for use by hbck2 doing fixup of overlaps > in hbase:meta. This issue is about exposing it via the Admin Interface and in > turn, via the shell. Probably best if old two region merge method is > deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23827) [HBCK2] Add mergeRegions method to hbck service
[ https://issues.apache.org/jira/browse/HBASE-23827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17051870#comment-17051870 ] Sakthi commented on HBASE-23827: The PR is up Guanghao. > [HBCK2] Add mergeRegions method to hbck service > --- > > Key: HBASE-23827 > URL: https://issues.apache.org/jira/browse/HBASE-23827 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.2.4, 2.1.10 > > > Let's add the mergeRegions method to the hbck service so that hbck2 can use > it from the client side. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23743) Release 1.4.13
[ https://issues.apache.org/jira/browse/HBASE-23743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048885#comment-17048885 ] Sakthi commented on HBASE-23743: Okay, [https://builds.apache.org/view/H-L/view/HBase/job/hbase_generate_website/1939/console] has done the job right for us. Let me announce the release. > Release 1.4.13 > -- > > Key: HBASE-23743 > URL: https://issues.apache.org/jira/browse/HBASE-23743 > Project: HBase > Issue Type: Task > Components: build, community >Affects Versions: 1.4.13 >Reporter: Sean Busbey >Assignee: Sakthi >Priority: Major > Fix For: 1.4.13 > > > over due for 1.4.13. I'll try to use the release manager scripts this time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23743) Release 1.4.13
[ https://issues.apache.org/jira/browse/HBASE-23743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048865#comment-17048865 ] Sakthi commented on HBASE-23743: The PR went in . Let's wait for the build to pick this up and deploy the changes in our downloads page. I'll announce the release shortly thereafter. > Release 1.4.13 > -- > > Key: HBASE-23743 > URL: https://issues.apache.org/jira/browse/HBASE-23743 > Project: HBase > Issue Type: Task > Components: build, community >Affects Versions: 1.4.13 >Reporter: Sean Busbey >Assignee: Sakthi >Priority: Major > Fix For: 1.4.13 > > > over due for 1.4.13. I'll try to use the release manager scripts this time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23743) Release 1.4.13
[ https://issues.apache.org/jira/browse/HBASE-23743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048259#comment-17048259 ] Sakthi commented on HBASE-23743: Pending: * Update the Downloads page with link and date of the release ([https://github.com/apache/hbase/pull/1226]) * Announcement Email - Once the above pr goes in. Any reviews on the above pr, please? > Release 1.4.13 > -- > > Key: HBASE-23743 > URL: https://issues.apache.org/jira/browse/HBASE-23743 > Project: HBase > Issue Type: Task > Components: build, community >Affects Versions: 1.4.13 >Reporter: Sean Busbey >Assignee: Sakthi >Priority: Major > Fix For: 1.4.13 > > > over due for 1.4.13. I'll try to use the release manager scripts this time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23743) Release 1.4.13
[ https://issues.apache.org/jira/browse/HBASE-23743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048255#comment-17048255 ] Sakthi commented on HBASE-23743: Sure [~zhangduo], stable-1 pointer has been moved to 1.4.13. 1.4.12 has been removed from releases. > Release 1.4.13 > -- > > Key: HBASE-23743 > URL: https://issues.apache.org/jira/browse/HBASE-23743 > Project: HBase > Issue Type: Task > Components: build, community >Affects Versions: 1.4.13 >Reporter: Sean Busbey >Assignee: Sakthi >Priority: Major > Fix For: 1.4.13 > > > over due for 1.4.13. I'll try to use the release manager scripts this time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (HBASE-23120) Fix ref guide - Release process
[
https://issues.apache.org/jira/browse/HBASE-23120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048048#comment-17048048
]
Sakthi edited comment on HBASE-23120 at 2/29/20 12:39 AM:
--
Is missing the steps to do after the voting succeeds:
* Push rel/release-version at the commit where the passing RC is tagged at
* Publish the nexus repo - (click the 'Release' button to release the artifacts
to central. The release process will automatically drop and delete the staging
repository)
* Move the RC from the dev directory to the releases directory (NOTE: the date
this action is performed, is considered to be the date of release.)
* Enter the date of release at reporter.a.o
(https://issues.apache.org/jira/browse/HBASE-23012?focusedCommentId=16958944=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16958944)
* Update the Downloads page with link and date of the release
* Move the version of the branch to next SNAPSHOT version or consider EOL by
starting up a discussion in private/dev
* Enter the release date in CHANGES.txt
* Mark the JIRA version released
* Announce the release
was (Author: jatsakthi):
Is missing the steps to do after the voting succeeds:
* Push rel/release-version at the commit where the passing RC is tagged at
* Publish the nexus repo - (click the 'Release' button to release the artifacts
to central. The release process will automatically drop and delete the staging
repository)
* Move the RC from the dev directory to the releases directory (NOTE: the date
this action is performed, is considered to be the date of release.)
* Enter the date of release at reporter.a.o
(https://issues.apache.org/jira/browse/HBASE-23012?focusedCommentId=16958944=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16958944)
* Update the Downloads page with link and date of the release
* Move the version of the branch to next SNAPSHOT version or consider EOL by
starting up a discussion in private/dev
* Enter the release date in CHANGES.txt
* Mark the JIRA version released
> Fix ref guide - Release process
> ---
>
> Key: HBASE-23120
> URL: https://issues.apache.org/jira/browse/HBASE-23120
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Reporter: Sakthi
>Assignee: Sakthi
>Priority: Minor
> Fix For: 3.0.0
>
>
> The example is of a sample ~/.m2/settings.xml file.
> {code:java}
>
> {code}
> is not a proper comment.
> Also I think here,
> {code:java}
>
> {code}
> the double hyphened --list-keys shouldn't be used. It leads to FATAL error
> like the one below:
> {code:java}
> [FATAL] Non-parseable settings
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (HBASE-23743) Release 1.4.13
[ https://issues.apache.org/jira/browse/HBASE-23743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048087#comment-17048087 ] Sakthi edited comment on HBASE-23743 at 2/29/20 12:38 AM: -- Pending: * Removal of 1.4.12 from releases and updation of the stable-1 pointer * Update the Downloads page with link and date of the release * Move the version of the branch to next SNAPSHOT version * Enter the release date in CHANGES.txt * Mark the JIRA version released * Announcement Email was (Author: jatsakthi): Pending: * Removal of 1.4.12 from releases and updation of the stable-1 pointer * Update the Downloads page with link and date of the release * Move the version of the branch to next SNAPSHOT version * Enter the release date in CHANGES.txt * Mark the JIRA version released > Release 1.4.13 > -- > > Key: HBASE-23743 > URL: https://issues.apache.org/jira/browse/HBASE-23743 > Project: HBase > Issue Type: Task > Components: build, community >Affects Versions: 1.4.13 >Reporter: Sean Busbey >Assignee: Sakthi >Priority: Major > Fix For: 1.4.13 > > > over due for 1.4.13. I'll try to use the release manager scripts this time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23743) Release 1.4.13
[ https://issues.apache.org/jira/browse/HBASE-23743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048087#comment-17048087 ] Sakthi commented on HBASE-23743: Pending: * Removal of 1.4.12 from releases and updation of the stable-1 pointer * Update the Downloads page with link and date of the release * Move the version of the branch to next SNAPSHOT version * Enter the release date in CHANGES.txt * Mark the JIRA version released > Release 1.4.13 > -- > > Key: HBASE-23743 > URL: https://issues.apache.org/jira/browse/HBASE-23743 > Project: HBase > Issue Type: Task > Components: build, community >Affects Versions: 1.4.13 >Reporter: Sean Busbey >Assignee: Sakthi >Priority: Major > Fix For: 1.4.13 > > > over due for 1.4.13. I'll try to use the release manager scripts this time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23743) Release 1.4.13
[ https://issues.apache.org/jira/browse/HBASE-23743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048086#comment-17048086 ] Sakthi commented on HBASE-23743: [~busbey] / [~apurtell] / [~zhangduo] currently I see that there is a stable-1 pointer in https://dist.apache.org/repos/dist/release/hbase/ which points to 1.4.12. Now that 1.4.13 has been added to the releases folder, should the stable-1 pointer be changed to 1.4.13 and 1.4.12 be removed? Just confirming. :) > Release 1.4.13 > -- > > Key: HBASE-23743 > URL: https://issues.apache.org/jira/browse/HBASE-23743 > Project: HBase > Issue Type: Task > Components: build, community >Affects Versions: 1.4.13 >Reporter: Sean Busbey >Assignee: Sakthi >Priority: Major > Fix For: 1.4.13 > > > over due for 1.4.13. I'll try to use the release manager scripts this time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23120) Fix ref guide - Release process
[
https://issues.apache.org/jira/browse/HBASE-23120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048085#comment-17048085
]
Sakthi commented on HBASE-23120:
Change the svn commit... command to svn commit -m "message" version
> Fix ref guide - Release process
> ---
>
> Key: HBASE-23120
> URL: https://issues.apache.org/jira/browse/HBASE-23120
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Reporter: Sakthi
>Assignee: Sakthi
>Priority: Minor
> Fix For: 3.0.0
>
>
> The example is of a sample ~/.m2/settings.xml file.
> {code:java}
>
> {code}
> is not a proper comment.
> Also I think here,
> {code:java}
>
> {code}
> the double hyphened --list-keys shouldn't be used. It leads to FATAL error
> like the one below:
> {code:java}
> [FATAL] Non-parseable settings
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HBASE-23120) Fix ref guide - Release process
[
https://issues.apache.org/jira/browse/HBASE-23120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sakthi updated HBASE-23120:
---
Component/s: documentation
> Fix ref guide - Release process
> ---
>
> Key: HBASE-23120
> URL: https://issues.apache.org/jira/browse/HBASE-23120
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Reporter: Sakthi
>Assignee: Sakthi
>Priority: Minor
> Fix For: 3.0.0
>
>
> The example is of a sample ~/.m2/settings.xml file.
> {code:java}
>
> {code}
> is not a proper comment.
> Also I think here,
> {code:java}
>
> {code}
> the double hyphened --list-keys shouldn't be used. It leads to FATAL error
> like the one below:
> {code:java}
> [FATAL] Non-parseable settings
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (HBASE-23120) Fix ref guide - Release process
[
https://issues.apache.org/jira/browse/HBASE-23120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048048#comment-17048048
]
Sakthi edited comment on HBASE-23120 at 2/28/20 11:33 PM:
--
Is missing the steps to do after the voting succeeds:
* Push rel/release-version at the commit where the passing RC is tagged at
* Publish the nexus repo - (click the 'Release' button to release the artifacts
to central. The release process will automatically drop and delete the staging
repository)
* Move the RC from the dev directory to the releases directory (NOTE: the date
this action is performed, is considered to be the date of release.)
* Enter the date of release at reporter.a.o
(https://issues.apache.org/jira/browse/HBASE-23012?focusedCommentId=16958944=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16958944)
* Update the Downloads page with link and date of the release
* Move the version of the branch to next SNAPSHOT version or consider EOL by
starting up a discussion in private/dev
* Enter the release date in CHANGES.txt
* Mark the JIRA version released
was (Author: jatsakthi):
Is missing the steps to do after the voting succeeds:
* Push rel/release-version at the commit where the passing RC is tagged at
* Publish the nexus repo - (click the 'Release' button to release the artifacts
to central. The release process will automatically drop and delete the staging
repository)
* Move the RC from the dev directory to the releases directory (NOTE: the date
this action is performed, is considered to be the date of release.)
* Enter the date of release at reporter.a.o
* Update the Downloads page with link and date of the release
* Move the version of the branch to next SNAPSHOT version or consider EOL by
starting up a discussion in private/dev
* Enter the release date in CHANGES.txt
* Mark the JIRA version released
> Fix ref guide - Release process
> ---
>
> Key: HBASE-23120
> URL: https://issues.apache.org/jira/browse/HBASE-23120
> Project: HBase
> Issue Type: Bug
>Reporter: Sakthi
>Assignee: Sakthi
>Priority: Minor
> Fix For: 3.0.0
>
>
> The example is of a sample ~/.m2/settings.xml file.
> {code:java}
>
> {code}
> is not a proper comment.
> Also I think here,
> {code:java}
>
> {code}
> the double hyphened --list-keys shouldn't be used. It leads to FATAL error
> like the one below:
> {code:java}
> [FATAL] Non-parseable settings
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23120) Fix ref guide - Release process
[
https://issues.apache.org/jira/browse/HBASE-23120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048048#comment-17048048
]
Sakthi commented on HBASE-23120:
Is missing the steps to do after the voting succeeds:
* Push rel/release-version at the commit where the passing RC is tagged at
* Publish the nexus repo - (click the 'Release' button to release the artifacts
to central. The release process will automatically drop and delete the staging
repository)
* Move the RC from the dev directory to the releases directory (NOTE: the date
this action is performed, is considered to be the date of release.)
* Enter the date of release at reporter.a.o
* Update the Downloads page with link and date of the release
* Move the version of the branch to next SNAPSHOT version or consider EOL by
starting up a discussion in private/dev
* Enter the release date in CHANGES.txt
* Mark the JIRA version released
> Fix ref guide - Release process
> ---
>
> Key: HBASE-23120
> URL: https://issues.apache.org/jira/browse/HBASE-23120
> Project: HBase
> Issue Type: Bug
>Reporter: Sakthi
>Assignee: Sakthi
>Priority: Minor
> Fix For: 3.0.0
>
>
> The example is of a sample ~/.m2/settings.xml file.
> {code:java}
>
> {code}
> is not a proper comment.
> Also I think here,
> {code:java}
>
> {code}
> the double hyphened --list-keys shouldn't be used. It leads to FATAL error
> like the one below:
> {code:java}
> [FATAL] Non-parseable settings
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23743) Release 1.4.13
[ https://issues.apache.org/jira/browse/HBASE-23743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048022#comment-17048022 ] Sakthi commented on HBASE-23743: RC0 passed. > Release 1.4.13 > -- > > Key: HBASE-23743 > URL: https://issues.apache.org/jira/browse/HBASE-23743 > Project: HBase > Issue Type: Task > Components: build, community >Affects Versions: 1.4.13 >Reporter: Sean Busbey >Assignee: Sakthi >Priority: Major > Fix For: 1.4.13 > > > over due for 1.4.13. I'll try to use the release manager scripts this time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-23878) Backport HBASE-22040 to branch-2.1
[ https://issues.apache.org/jira/browse/HBASE-23878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi resolved HBASE-23878. Resolution: Fixed > Backport HBASE-22040 to branch-2.1 > -- > > Key: HBASE-23878 > URL: https://issues.apache.org/jira/browse/HBASE-23878 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Fix For: 2.1.10 > > Attachments: hbase-23878.branch-2.1.001.patch > > > This fix went in to 2.2+. But I feel like it's applicable and could be used > in 2.1 as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23878) Backport HBASE-22040 to branch-2.1
[ https://issues.apache.org/jira/browse/HBASE-23878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-23878: --- Release Note: Add a mergeRegionsAsync(byte[][], boolean) method in the AsyncAdmin interface. Instead of using assert, now we will throw IllegalArgumentException when you want to merge less than 2 regions at client side. And also, at master side, instead of using assert, now we will throw DoNotRetryIOException if you want merge more than 2 regions, since we only support merging two regions at once for now. > Backport HBASE-22040 to branch-2.1 > -- > > Key: HBASE-23878 > URL: https://issues.apache.org/jira/browse/HBASE-23878 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Fix For: 2.1.10 > > Attachments: hbase-23878.branch-2.1.001.patch > > > This fix went in to 2.2+. But I feel like it's applicable and could be used > in 2.1 as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23878) Backport HBASE-22040 to branch-2.1
[ https://issues.apache.org/jira/browse/HBASE-23878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17046957#comment-17046957 ] Sakthi commented on HBASE-23878: This has been merged to 2.1 > Backport HBASE-22040 to branch-2.1 > -- > > Key: HBASE-23878 > URL: https://issues.apache.org/jira/browse/HBASE-23878 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Fix For: 2.1.10 > > Attachments: hbase-23878.branch-2.1.001.patch > > > This fix went in to 2.2+. But I feel like it's applicable and could be used > in 2.1 as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-22827) Expose multi-region merge in shell and Admin API
[ https://issues.apache.org/jira/browse/HBASE-22827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17046506#comment-17046506 ] Sakthi commented on HBASE-22827: Okay, so after HBASE-23878 goes in, I think this feature can be merged in 2.1 as well. As far as the shell command change is concerned, as it supports backwards compatibility by supporting the previous merge syntax as well I think we would be fine here if we expose this feature in 2.1 as well. I'll create a PR and merge in for 2.1, unless any objections. > Expose multi-region merge in shell and Admin API > > > Key: HBASE-22827 > URL: https://issues.apache.org/jira/browse/HBASE-22827 > Project: HBase > Issue Type: Improvement > Components: Admin, shell >Reporter: Michael Stack >Assignee: Sakthi >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.2.4 > > Attachments: hbase-22827.branch-2.001.patch > > > HBASE-22777 adds being able to merge more than two regions at once. It is > only available internally currently for use by hbck2 doing fixup of overlaps > in hbase:meta. This issue is about exposing it via the Admin Interface and in > turn, via the shell. Probably best if old two region merge method is > deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-22827) Expose multi-region merge in shell and Admin API
[ https://issues.apache.org/jira/browse/HBASE-22827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17044638#comment-17044638 ] Sakthi commented on HBASE-22827: Merged in 2.2 > Expose multi-region merge in shell and Admin API > > > Key: HBASE-22827 > URL: https://issues.apache.org/jira/browse/HBASE-22827 > Project: HBase > Issue Type: Improvement > Components: Admin, shell >Reporter: Michael Stack >Assignee: Sakthi >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.2.4 > > Attachments: hbase-22827.branch-2.001.patch > > > HBASE-22777 adds being able to merge more than two regions at once. It is > only available internally currently for use by hbck2 doing fixup of overlaps > in hbase:meta. This issue is about exposing it via the Admin Interface and in > turn, via the shell. Probably best if old two region merge method is > deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-22827) Expose multi-region merge in shell and Admin API
[ https://issues.apache.org/jira/browse/HBASE-22827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-22827: --- Fix Version/s: 2.2.4 > Expose multi-region merge in shell and Admin API > > > Key: HBASE-22827 > URL: https://issues.apache.org/jira/browse/HBASE-22827 > Project: HBase > Issue Type: Improvement > Components: Admin, shell >Reporter: Michael Stack >Assignee: Sakthi >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.2.4 > > Attachments: hbase-22827.branch-2.001.patch > > > HBASE-22777 adds being able to merge more than two regions at once. It is > only available internally currently for use by hbck2 doing fixup of overlaps > in hbase:meta. This issue is about exposing it via the Admin Interface and in > turn, via the shell. Probably best if old two region merge method is > deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23878) Backport HBASE-22040 to branch-2.1
[ https://issues.apache.org/jira/browse/HBASE-23878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17043960#comment-17043960 ] Sakthi commented on HBASE-23878: I have created the PR [~zhangduo]. Please don't mind the patch attached here. Could you please give the PR a quick review? > Backport HBASE-22040 to branch-2.1 > -- > > Key: HBASE-23878 > URL: https://issues.apache.org/jira/browse/HBASE-23878 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Fix For: 2.1.10 > > Attachments: hbase-23878.branch-2.1.001.patch > > > This fix went in to 2.2+. But I feel like it's applicable and could be used > in 2.1 as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23878) Backport HBASE-22040 to branch-2.1
[ https://issues.apache.org/jira/browse/HBASE-23878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17043957#comment-17043957 ] Sakthi commented on HBASE-23878: I got a green signal from [~zhangduo] for this one. Let me create a PR > Backport HBASE-22040 to branch-2.1 > -- > > Key: HBASE-23878 > URL: https://issues.apache.org/jira/browse/HBASE-23878 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Fix For: 2.1.10 > > Attachments: hbase-23878.branch-2.1.001.patch > > > This fix went in to 2.2+. But I feel like it's applicable and could be used > in 2.1 as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (HBASE-22827) Expose multi-region merge in shell and Admin API
[ https://issues.apache.org/jira/browse/HBASE-22827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi reopened HBASE-22827: > Expose multi-region merge in shell and Admin API > > > Key: HBASE-22827 > URL: https://issues.apache.org/jira/browse/HBASE-22827 > Project: HBase > Issue Type: Improvement > Components: Admin, shell >Reporter: Michael Stack >Assignee: Sakthi >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: hbase-22827.branch-2.001.patch > > > HBASE-22777 adds being able to merge more than two regions at once. It is > only available internally currently for use by hbck2 doing fixup of overlaps > in hbase:meta. This issue is about exposing it via the Admin Interface and in > turn, via the shell. Probably best if old two region merge method is > deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23743) Release 1.4.13
[ https://issues.apache.org/jira/browse/HBASE-23743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17043260#comment-17043260 ] Sakthi commented on HBASE-23743: Artifacts have been staged in the mvn repo - https://repository.apache.org/content/repositories/orgapachehbase-1384 > Release 1.4.13 > -- > > Key: HBASE-23743 > URL: https://issues.apache.org/jira/browse/HBASE-23743 > Project: HBase > Issue Type: Task > Components: build, community >Affects Versions: 1.4.13 >Reporter: Sean Busbey >Assignee: Sakthi >Priority: Major > Fix For: 1.4.13 > > > over due for 1.4.13. I'll try to use the release manager scripts this time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23120) Fix ref guide - Release process
[
https://issues.apache.org/jira/browse/HBASE-23120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042794#comment-17042794
]
Sakthi commented on HBASE-23120:
'+$ git tag -s rel/2.0.0-alpha4 -m "Tagging the 2.0.0-alpha4 Release"' has a +
sign at the start. Need to fix it.
> Fix ref guide - Release process
> ---
>
> Key: HBASE-23120
> URL: https://issues.apache.org/jira/browse/HBASE-23120
> Project: HBase
> Issue Type: Bug
>Reporter: Sakthi
>Assignee: Sakthi
>Priority: Minor
> Fix For: 3.0.0
>
>
> The example is of a sample ~/.m2/settings.xml file.
> {code:java}
>
> {code}
> is not a proper comment.
> Also I think here,
> {code:java}
>
> {code}
> the double hyphened --list-keys shouldn't be used. It leads to FATAL error
> like the one below:
> {code:java}
> [FATAL] Non-parseable settings
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (HBASE-23743) Release 1.4.13
[ https://issues.apache.org/jira/browse/HBASE-23743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042773#comment-17042773 ] Sakthi edited comment on HBASE-23743 at 2/23/20 1:59 AM: - Update poms, changes.txt. Pushed the RC tag 1.4.13RC0 was (Author: jatsakthi): Update poms, changes.txt. Pushed the release tag 1.4.13RC0 > Release 1.4.13 > -- > > Key: HBASE-23743 > URL: https://issues.apache.org/jira/browse/HBASE-23743 > Project: HBase > Issue Type: Task > Components: build, community >Affects Versions: 1.4.13 >Reporter: Sean Busbey >Assignee: Sakthi >Priority: Major > Fix For: 1.4.13 > > > over due for 1.4.13. I'll try to use the release manager scripts this time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23743) Release 1.4.13
[ https://issues.apache.org/jira/browse/HBASE-23743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042773#comment-17042773 ] Sakthi commented on HBASE-23743: Update poms, changes.txt. Pushed the release tag 1.4.13RC0 > Release 1.4.13 > -- > > Key: HBASE-23743 > URL: https://issues.apache.org/jira/browse/HBASE-23743 > Project: HBase > Issue Type: Task > Components: build, community >Affects Versions: 1.4.13 >Reporter: Sean Busbey >Assignee: Sakthi >Priority: Major > Fix For: 1.4.13 > > > over due for 1.4.13. I'll try to use the release manager scripts this time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23743) Release 1.4.13
[ https://issues.apache.org/jira/browse/HBASE-23743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042772#comment-17042772 ] Sakthi commented on HBASE-23743: Gira and git status look intact. > Release 1.4.13 > -- > > Key: HBASE-23743 > URL: https://issues.apache.org/jira/browse/HBASE-23743 > Project: HBase > Issue Type: Task > Components: build, community >Affects Versions: 1.4.13 >Reporter: Sean Busbey >Assignee: Sakthi >Priority: Major > Fix For: 1.4.13 > > > over due for 1.4.13. I'll try to use the release manager scripts this time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23862) Fix flaky TestSnapshotFromMaster in 1.x versions
[ https://issues.apache.org/jira/browse/HBASE-23862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-23862: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Fix flaky TestSnapshotFromMaster in 1.x versions > > > Key: HBASE-23862 > URL: https://issues.apache.org/jira/browse/HBASE-23862 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Fix For: 1.3.7, 1.7.0, 1.4.13 > > Attachments: hbase-23862.branch-1.3.001.patch, > hbase-23862.branch-1.4.001.patch > > > HBASE-23658 was about fixing this flakey ut in branch-2+. I think it can be > backported to branch-1s as well. 18/30 times this test has failed in > branch-1, 10/30 in 1.4 and 3/30 in 1.3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23862) Fix flaky TestSnapshotFromMaster in 1.x versions
[ https://issues.apache.org/jira/browse/HBASE-23862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042283#comment-17042283 ] Sakthi commented on HBASE-23862: branch-1 pom currently aims at 1.7.0-snapshot hence putting 1.7.0 as fix version. > Fix flaky TestSnapshotFromMaster in 1.x versions > > > Key: HBASE-23862 > URL: https://issues.apache.org/jira/browse/HBASE-23862 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Fix For: 1.3.7, 1.7.0, 1.4.13 > > Attachments: hbase-23862.branch-1.3.001.patch, > hbase-23862.branch-1.4.001.patch > > > HBASE-23658 was about fixing this flakey ut in branch-2+. I think it can be > backported to branch-1s as well. 18/30 times this test has failed in > branch-1, 10/30 in 1.4 and 3/30 in 1.3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23862) Fix flaky TestSnapshotFromMaster in 1.x versions
[ https://issues.apache.org/jira/browse/HBASE-23862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-23862: --- Fix Version/s: 1.4.13 1.7.0 1.3.7 > Fix flaky TestSnapshotFromMaster in 1.x versions > > > Key: HBASE-23862 > URL: https://issues.apache.org/jira/browse/HBASE-23862 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Fix For: 1.3.7, 1.7.0, 1.4.13 > > Attachments: hbase-23862.branch-1.3.001.patch, > hbase-23862.branch-1.4.001.patch > > > HBASE-23658 was about fixing this flakey ut in branch-2+. I think it can be > backported to branch-1s as well. 18/30 times this test has failed in > branch-1, 10/30 in 1.4 and 3/30 in 1.3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23862) Fix flaky TestSnapshotFromMaster in 1.x versions
[ https://issues.apache.org/jira/browse/HBASE-23862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042281#comment-17042281 ] Sakthi commented on HBASE-23862: pushed to branch-1.4 and branch-1.3. Let me close out this jira. > Fix flaky TestSnapshotFromMaster in 1.x versions > > > Key: HBASE-23862 > URL: https://issues.apache.org/jira/browse/HBASE-23862 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Attachments: hbase-23862.branch-1.3.001.patch, > hbase-23862.branch-1.4.001.patch > > > HBASE-23658 was about fixing this flakey ut in branch-2+. I think it can be > backported to branch-1s as well. 18/30 times this test has failed in > branch-1, 10/30 in 1.4 and 3/30 in 1.3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-22827) Expose multi-region merge in shell and Admin API
[ https://issues.apache.org/jira/browse/HBASE-22827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042279#comment-17042279 ] Sakthi commented on HBASE-22827: Sure [~busbey]. I think we can work on getting this feature in 2.2 as well like i mentioned in the previous comment. As far as branch-2.1 is concerned, the branch is missing HBASE-22040 hence it's okay to skip it there rather than backporting that and including this feature there. I'll go ahead and merge this feature in branch-2.2 in few days, unless any objections. > Expose multi-region merge in shell and Admin API > > > Key: HBASE-22827 > URL: https://issues.apache.org/jira/browse/HBASE-22827 > Project: HBase > Issue Type: Improvement > Components: Admin, shell >Reporter: Michael Stack >Assignee: Sakthi >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: hbase-22827.branch-2.001.patch > > > HBASE-22777 adds being able to merge more than two regions at once. It is > only available internally currently for use by hbck2 doing fixup of overlaps > in hbase:meta. This issue is about exposing it via the Admin Interface and in > turn, via the shell. Probably best if old two region merge method is > deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-22040) Add mergeRegionsAsync with a List of region names method in AsyncAdmin
[ https://issues.apache.org/jira/browse/HBASE-22040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042277#comment-17042277 ] Sakthi commented on HBASE-22040: I think it's fine to not include this in 2.1 now. Never mind Duo. > Add mergeRegionsAsync with a List of region names method in AsyncAdmin > -- > > Key: HBASE-22040 > URL: https://issues.apache.org/jira/browse/HBASE-22040 > Project: HBase > Issue Type: Sub-task > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0, 2.2.0, 2.3.0 > > Attachments: HBASE-22040-branch-2.patch, HBASE-22040-v1.patch, > HBASE-22040-v2.patch, HBASE-22040-v3.patch, HBASE-22040.patch > > > Although we only support merging two regions until now, but the rpc protocol > does support passing more than two regions to master. > So I think we should provide the methods, but need to add comments to say > that for now we only support merging two regions so do not try to pass more > than two regions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-23883) HBase Precommit builds are broken due to some docker/java issue.
Sakthi created HBASE-23883: -- Summary: HBase Precommit builds are broken due to some docker/java issue. Key: HBASE-23883 URL: https://issues.apache.org/jira/browse/HBASE-23883 Project: HBase Issue Type: Task Components: build Reporter: Sakthi For example see: https://builds.apache.org/view/H-L/view/HBase/job/PreCommit-HBASE-Build/1136/console -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23862) Fix flaky TestSnapshotFromMaster in 1.x versions
[ https://issues.apache.org/jira/browse/HBASE-23862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-23862: --- Status: Patch Available (was: In Progress) > Fix flaky TestSnapshotFromMaster in 1.x versions > > > Key: HBASE-23862 > URL: https://issues.apache.org/jira/browse/HBASE-23862 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Attachments: hbase-23862.branch-1.3.001.patch, > hbase-23862.branch-1.4.001.patch > > > HBASE-23658 was about fixing this flakey ut in branch-2+. I think it can be > backported to branch-1s as well. 18/30 times this test has failed in > branch-1, 10/30 in 1.4 and 3/30 in 1.3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23862) Fix flaky TestSnapshotFromMaster in 1.x versions
[ https://issues.apache.org/jira/browse/HBASE-23862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17040611#comment-17040611 ] Sakthi commented on HBASE-23862: Once the QA comes up for both 1.3, 1.4 I'll push them in. > Fix flaky TestSnapshotFromMaster in 1.x versions > > > Key: HBASE-23862 > URL: https://issues.apache.org/jira/browse/HBASE-23862 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Attachments: hbase-23862.branch-1.3.001.patch, > hbase-23862.branch-1.4.001.patch > > > HBASE-23658 was about fixing this flakey ut in branch-2+. I think it can be > backported to branch-1s as well. 18/30 times this test has failed in > branch-1, 10/30 in 1.4 and 3/30 in 1.3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23862) Fix flaky TestSnapshotFromMaster in 1.x versions
[ https://issues.apache.org/jira/browse/HBASE-23862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-23862: --- Attachment: hbase-23862.branch-1.3.001.patch > Fix flaky TestSnapshotFromMaster in 1.x versions > > > Key: HBASE-23862 > URL: https://issues.apache.org/jira/browse/HBASE-23862 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Attachments: hbase-23862.branch-1.3.001.patch, > hbase-23862.branch-1.4.001.patch > > > HBASE-23658 was about fixing this flakey ut in branch-2+. I think it can be > backported to branch-1s as well. 18/30 times this test has failed in > branch-1, 10/30 in 1.4 and 3/30 in 1.3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23862) Fix flaky TestSnapshotFromMaster in 1.x versions
[ https://issues.apache.org/jira/browse/HBASE-23862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-23862: --- Attachment: hbase-23862.branch-1.4.001.patch > Fix flaky TestSnapshotFromMaster in 1.x versions > > > Key: HBASE-23862 > URL: https://issues.apache.org/jira/browse/HBASE-23862 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Attachments: hbase-23862.branch-1.4.001.patch > > > HBASE-23658 was about fixing this flakey ut in branch-2+. I think it can be > backported to branch-1s as well. 18/30 times this test has failed in > branch-1, 10/30 in 1.4 and 3/30 in 1.3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23878) Backport HBASE-22040 to branch-2.1
[ https://issues.apache.org/jira/browse/HBASE-23878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17040577#comment-17040577 ] Sakthi commented on HBASE-23878: the patch 001 is wrong. Just realized that hbase-22941 has already made it into branch-2.1 (which should have after 22040). > Backport HBASE-22040 to branch-2.1 > -- > > Key: HBASE-23878 > URL: https://issues.apache.org/jira/browse/HBASE-23878 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Fix For: 2.1.10 > > Attachments: hbase-23878.branch-2.1.001.patch > > > This fix went in to 2.2+. But I feel like it's applicable and could be used > in 2.1 as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-22040) Add mergeRegionsAsync with a List of region names method in AsyncAdmin
[ https://issues.apache.org/jira/browse/HBASE-22040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17040571#comment-17040571 ] Sakthi commented on HBASE-22040: Ah I see. Yes, the main motto was to try to have multi-region merge feature accessible via shell (HBASE-22827) be present in 2.1 as well. But that needs presence of this fix. Do you think it's possible? What would be the best way forward for users on 2.1 to be able to access this feature. ? [~zhangduo] > Add mergeRegionsAsync with a List of region names method in AsyncAdmin > -- > > Key: HBASE-22040 > URL: https://issues.apache.org/jira/browse/HBASE-22040 > Project: HBase > Issue Type: Sub-task > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0, 2.2.0, 2.3.0 > > Attachments: HBASE-22040-branch-2.patch, HBASE-22040-v1.patch, > HBASE-22040-v2.patch, HBASE-22040-v3.patch, HBASE-22040.patch > > > Although we only support merging two regions until now, but the rpc protocol > does support passing more than two regions to master. > So I think we should provide the methods, but need to add comments to say > that for now we only support merging two regions so do not try to pass more > than two regions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23878) Backport HBASE-22040 to branch-2.1
[ https://issues.apache.org/jira/browse/HBASE-23878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-23878: --- Attachment: hbase-23878.branch-2.1.001.patch > Backport HBASE-22040 to branch-2.1 > -- > > Key: HBASE-23878 > URL: https://issues.apache.org/jira/browse/HBASE-23878 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Fix For: 2.1.10 > > Attachments: hbase-23878.branch-2.1.001.patch > > > This fix went in to 2.2+. But I feel like it's applicable and could be used > in 2.1 as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (HBASE-23878) Backport HBASE-22040 to branch-2.1
[ https://issues.apache.org/jira/browse/HBASE-23878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-23878 started by Sakthi. -- > Backport HBASE-22040 to branch-2.1 > -- > > Key: HBASE-23878 > URL: https://issues.apache.org/jira/browse/HBASE-23878 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Fix For: 2.1.10 > > Attachments: hbase-23878.branch-2.1.001.patch > > > This fix went in to 2.2+. But I feel like it's applicable and could be used > in 2.1 as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23878) Backport HBASE-22040 to branch-2.1
[ https://issues.apache.org/jira/browse/HBASE-23878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-23878: --- Fix Version/s: 2.1.10 > Backport HBASE-22040 to branch-2.1 > -- > > Key: HBASE-23878 > URL: https://issues.apache.org/jira/browse/HBASE-23878 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Fix For: 2.1.10 > > > This fix went in to 2.2+. But I feel like it's applicable and could be used > in 2.1 as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-23878) Backport HBASE-22040 to branch-2.1
Sakthi created HBASE-23878: -- Summary: Backport HBASE-22040 to branch-2.1 Key: HBASE-23878 URL: https://issues.apache.org/jira/browse/HBASE-23878 Project: HBase Issue Type: Task Reporter: Sakthi Assignee: Sakthi This fix went in to 2.2+. But I feel like it's applicable and could be used in 2.1 as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-22040) Add mergeRegionsAsync with a List of region names method in AsyncAdmin
[ https://issues.apache.org/jira/browse/HBASE-22040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17040542#comment-17040542 ] Sakthi commented on HBASE-22040: let me create a sub-task for backporting this to branch-2.1 as well > Add mergeRegionsAsync with a List of region names method in AsyncAdmin > -- > > Key: HBASE-22040 > URL: https://issues.apache.org/jira/browse/HBASE-22040 > Project: HBase > Issue Type: Sub-task > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0, 2.2.0, 2.3.0 > > Attachments: HBASE-22040-branch-2.patch, HBASE-22040-v1.patch, > HBASE-22040-v2.patch, HBASE-22040-v3.patch, HBASE-22040.patch > > > Although we only support merging two regions until now, but the rpc protocol > does support passing more than two regions to master. > So I think we should provide the methods, but need to add comments to say > that for now we only support merging two regions so do not try to pass more > than two regions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-22827) Expose multi-region merge in shell and Admin API
[ https://issues.apache.org/jira/browse/HBASE-22827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039555#comment-17039555 ] Sakthi commented on HBASE-22827: Hey [~stack], I think this would be a nice feature to be added in our 2.1 and 2.2 as well. 2.2 already has everything set in place so we should be fine there. 2.1 needs to have HBASE-22040 for us to be able to land this as well. What do you think? > Expose multi-region merge in shell and Admin API > > > Key: HBASE-22827 > URL: https://issues.apache.org/jira/browse/HBASE-22827 > Project: HBase > Issue Type: Improvement > Components: Admin, shell >Reporter: Michael Stack >Assignee: Sakthi >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: hbase-22827.branch-2.001.patch > > > HBASE-22777 adds being able to merge more than two regions at once. It is > only available internally currently for use by hbck2 doing fixup of overlaps > in hbase:meta. This issue is about exposing it via the Admin Interface and in > turn, via the shell. Probably best if old two region merge method is > deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-22040) Add mergeRegionsAsync with a List of region names method in AsyncAdmin
[ https://issues.apache.org/jira/browse/HBASE-22040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039553#comment-17039553 ] Sakthi commented on HBASE-22040: Hey [~zhangduo] any reason why this one couldn't make it to branch-2.1? > Add mergeRegionsAsync with a List of region names method in AsyncAdmin > -- > > Key: HBASE-22040 > URL: https://issues.apache.org/jira/browse/HBASE-22040 > Project: HBase > Issue Type: Sub-task > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0, 2.2.0, 2.3.0 > > Attachments: HBASE-22040-branch-2.patch, HBASE-22040-v1.patch, > HBASE-22040-v2.patch, HBASE-22040-v3.patch, HBASE-22040.patch > > > Although we only support merging two regions until now, but the rpc protocol > does support passing more than two regions to master. > So I think we should provide the methods, but need to add comments to say > that for now we only support merging two regions so do not try to pass more > than two regions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23862) Fix flaky TestSnapshotFromMaster in 1.x versions
[ https://issues.apache.org/jira/browse/HBASE-23862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038828#comment-17038828 ] Sakthi commented on HBASE-23862: The change seems to help us. Let me create a pr. > Fix flaky TestSnapshotFromMaster in 1.x versions > > > Key: HBASE-23862 > URL: https://issues.apache.org/jira/browse/HBASE-23862 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > > HBASE-23658 was about fixing this flakey ut in branch-2+. I think it can be > backported to branch-1s as well. 18/30 times this test has failed in > branch-1, 10/30 in 1.4 and 3/30 in 1.3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (HBASE-23862) Fix flaky TestSnapshotFromMaster in 1.x versions
[ https://issues.apache.org/jira/browse/HBASE-23862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-23862 started by Sakthi. -- > Fix flaky TestSnapshotFromMaster in 1.x versions > > > Key: HBASE-23862 > URL: https://issues.apache.org/jira/browse/HBASE-23862 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > > HBASE-23658 was about fixing this flakey ut in branch-2+. I think it can be > backported to branch-1s as well. 18/30 times this test has failed in > branch-1, 10/30 in 1.4 and 3/30 in 1.3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-22827) Expose multi-region merge in shell and Admin API
[ https://issues.apache.org/jira/browse/HBASE-22827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-22827: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Expose multi-region merge in shell and Admin API > > > Key: HBASE-22827 > URL: https://issues.apache.org/jira/browse/HBASE-22827 > Project: HBase > Issue Type: Improvement > Components: Admin, shell >Reporter: Michael Stack >Assignee: Sakthi >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: hbase-22827.branch-2.001.patch > > > HBASE-22777 adds being able to merge more than two regions at once. It is > only available internally currently for use by hbck2 doing fixup of overlaps > in hbase:meta. This issue is about exposing it via the Admin Interface and in > turn, via the shell. Probably best if old two region merge method is > deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-22827) Expose multi-region merge in shell and Admin API
[ https://issues.apache.org/jira/browse/HBASE-22827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038814#comment-17038814 ] Sakthi commented on HBASE-22827: Pushed to branch-2. Closing the jira now. > Expose multi-region merge in shell and Admin API > > > Key: HBASE-22827 > URL: https://issues.apache.org/jira/browse/HBASE-22827 > Project: HBase > Issue Type: Improvement > Components: Admin, shell >Reporter: Michael Stack >Assignee: Sakthi >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: hbase-22827.branch-2.001.patch > > > HBASE-22777 adds being able to merge more than two regions at once. It is > only available internally currently for use by hbck2 doing fixup of overlaps > in hbase:meta. This issue is about exposing it via the Admin Interface and in > turn, via the shell. Probably best if old two region merge method is > deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-22827) Expose multi-region merge in shell and Admin API
[ https://issues.apache.org/jira/browse/HBASE-22827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-22827: --- Fix Version/s: 2.3.0 Status: Patch Available (was: In Progress) > Expose multi-region merge in shell and Admin API > > > Key: HBASE-22827 > URL: https://issues.apache.org/jira/browse/HBASE-22827 > Project: HBase > Issue Type: Improvement > Components: Admin, shell >Reporter: Michael Stack >Assignee: Sakthi >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: hbase-22827.branch-2.001.patch > > > HBASE-22777 adds being able to merge more than two regions at once. It is > only available internally currently for use by hbck2 doing fixup of overlaps > in hbase:meta. This issue is about exposing it via the Admin Interface and in > turn, via the shell. Probably best if old two region merge method is > deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-22827) Expose multi-region merge in shell and Admin API
[ https://issues.apache.org/jira/browse/HBASE-22827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-22827: --- Attachment: hbase-22827.branch-2.001.patch > Expose multi-region merge in shell and Admin API > > > Key: HBASE-22827 > URL: https://issues.apache.org/jira/browse/HBASE-22827 > Project: HBase > Issue Type: Improvement > Components: Admin, shell >Reporter: Michael Stack >Assignee: Sakthi >Priority: Major > Fix For: 3.0.0 > > Attachments: hbase-22827.branch-2.001.patch > > > HBASE-22777 adds being able to merge more than two regions at once. It is > only available internally currently for use by hbck2 doing fixup of overlaps > in hbase:meta. This issue is about exposing it via the Admin Interface and in > turn, via the shell. Probably best if old two region merge method is > deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (HBASE-23827) [HBCK2] Add mergeRegions method to hbck service
[ https://issues.apache.org/jira/browse/HBASE-23827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-23827 started by Sakthi. -- > [HBCK2] Add mergeRegions method to hbck service > --- > > Key: HBASE-23827 > URL: https://issues.apache.org/jira/browse/HBASE-23827 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.2.4, 2.1.10 > > > Let's add the mergeRegions method to the hbck service so that hbck2 can use > it from the client side. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23862) Fix flaky TestSnapshotFromMaster in 1.x versions
[ https://issues.apache.org/jira/browse/HBASE-23862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038621#comment-17038621 ] Sakthi commented on HBASE-23862: Have pushed change into the branch https://github.com/apache/hbase/tree/HBASE-23862 for testing using our adhoc UT running job. > Fix flaky TestSnapshotFromMaster in 1.x versions > > > Key: HBASE-23862 > URL: https://issues.apache.org/jira/browse/HBASE-23862 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > > HBASE-23658 was about fixing this flakey ut in branch-2+. I think it can be > backported to branch-1s as well. 18/30 times this test has failed in > branch-1, 10/30 in 1.4 and 3/30 in 1.3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-23862) Fix flaky TestSnapshotFromMaster in 1.x versions
Sakthi created HBASE-23862: -- Summary: Fix flaky TestSnapshotFromMaster in 1.x versions Key: HBASE-23862 URL: https://issues.apache.org/jira/browse/HBASE-23862 Project: HBase Issue Type: Task Reporter: Sakthi Assignee: Sakthi HBASE-23658 was about fixing this flakey ut in branch-2+. I think it can be backported to branch-1s as well. 18/30 times this test has failed in branch-1, 10/30 in 1.4 and 3/30 in 1.3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23658) Fix flaky TestSnapshotFromMaster
[
https://issues.apache.org/jira/browse/HBASE-23658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038612#comment-17038612
]
Sakthi commented on HBASE-23658:
I think this fix can be backported to branch-1+ as well. This UT has been very
flakey in those branches as well.
> Fix flaky TestSnapshotFromMaster
>
>
> Key: HBASE-23658
> URL: https://issues.apache.org/jira/browse/HBASE-23658
> Project: HBase
> Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.3, 2.1.9
>
> Attachments: HBASE-23658.branch-2.2.001.patch
>
>
> testAsyncSnapshotWillNotBlockSnapshotHFileCleaner is flaky. The assert may
> fail.
> {code:java}
> assertTrue(master.getSnapshotManager().isTakingAnySnapshot());
> future.get(); // in branch-2.2, here is Thread.sleep
> assertFalse(master.getSnapshotManager().isTakingAnySnapshot());
> {code}
> See
> [https://builds.apache.org/job/HBase-Flaky-Tests/job/master/5227/testReport/junit/org.apache.hadoop.hbase.master.cleaner/TestSnapshotFromMaster/testAsyncSnapshotWillNotBlockSnapshotHFileCleaner/]
>
> [https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-2.2/lastSuccessfulBuild/artifact/dashboard.html]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23743) Release 1.4.13
[ https://issues.apache.org/jira/browse/HBASE-23743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17037716#comment-17037716 ] Sakthi commented on HBASE-23743: Have moved few jiras to 1.4.14. Rest looks ok. Let me start testing out. > Release 1.4.13 > -- > > Key: HBASE-23743 > URL: https://issues.apache.org/jira/browse/HBASE-23743 > Project: HBase > Issue Type: Task > Components: build, community >Affects Versions: 1.4.13 >Reporter: Sean Busbey >Assignee: Sakthi >Priority: Major > Fix For: 1.4.13 > > > over due for 1.4.13. I'll try to use the release manager scripts this time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23656) [MERGETOOL] HBASE Support Merge region by pattern
[ https://issues.apache.org/jira/browse/HBASE-23656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-23656: --- Fix Version/s: (was: 1.4.13) 1.4.14 > [MERGETOOL] HBASE Support Merge region by pattern > - > > Key: HBASE-23656 > URL: https://issues.apache.org/jira/browse/HBASE-23656 > Project: HBase > Issue Type: New Feature > Components: master >Reporter: zhengsicheng >Assignee: zhengsicheng >Priority: Minor > Fix For: 3.0.0, 1.4.14 > > Attachments: HBASE-23656.branch-1.4.v1.patch, > HBASE-23656.master.v1.patch > > > Design Objective: > # Merge empty region > # Neat region > # merge expired region > Usage: bin/hbase onlinemerge [--tableName=] [--startRegion=] [--stopRegion=] > [--maxRegionSize=] [--maxRegionCreateTime=] [--numMaxMergePlans=] > [--targetRegionCount=] [--printExecutionPlan=] [--configMergePauseTime=] > Options: > --h or --h print help > --tableName table name must be not null > --startRegion start region > --stopRegion stop region > --maxRegionSize max region size Unit GB > --maxRegionCreateTime max Region Create Time /MM/dd HH:mm:ss > --numMaxMergePlans num MaxMerge Plans > --targetRegionCount target Region Count > --configMergePauseTime config Merge Pause Time In milliseconds > --printExecutionPlan Value default is true print execution plans false is > execution merge > Examples: > bin/hbase onlinemerge --tableName=test:test1 > --startRegion=test:test1,,1576835912332.01d0d6c2b41e204104524d9aec6074fb. > --stopRegion=test:test1,,1573044786980.0c9b5bd93f3b19eb9bd1a1011ddff66f. > --maxRegionSize=0 --maxRegionCreateTime=/MM/dd HH:mm:ss > --numMaxMergePlans=2 --targetRegionCount=4 --printExecutionPlan=false -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-21903) Backport major compaction tool HBASE-19528 from to 1.4 and 1.3
[ https://issues.apache.org/jira/browse/HBASE-21903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-21903: --- Fix Version/s: 1.4.14 > Backport major compaction tool HBASE-19528 from to 1.4 and 1.3 > -- > > Key: HBASE-21903 > URL: https://issues.apache.org/jira/browse/HBASE-21903 > Project: HBase > Issue Type: Task > Components: Client, Compaction, tooling >Affects Versions: 1.3.3, 1.4.9 >Reporter: Thiruvel Thirumoolan >Assignee: Thiruvel Thirumoolan >Priority: Major > Fix For: 1.3.7, 1.4.14 > > Attachments: HBASE-21903-branch-1.3-addendum.patch > > > Our internal deployments are based on branch-1.3. We will be using the major > compaction tool HBASE-19528 from [~churromorales] and the enhancements on top > of it HBASE-21883 on our 1.3 clusters. I would like to backport HBASE-19528 > to 1.3 and hence 1.4 as well. Since its a standalone tool without any other > dependency or code changes, I believe that should be ok. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-21903) Backport major compaction tool HBASE-19528 from to 1.4 and 1.3
[ https://issues.apache.org/jira/browse/HBASE-21903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-21903: --- Fix Version/s: (was: 1.4.1) > Backport major compaction tool HBASE-19528 from to 1.4 and 1.3 > -- > > Key: HBASE-21903 > URL: https://issues.apache.org/jira/browse/HBASE-21903 > Project: HBase > Issue Type: Task > Components: Client, Compaction, tooling >Affects Versions: 1.3.3, 1.4.9 >Reporter: Thiruvel Thirumoolan >Assignee: Thiruvel Thirumoolan >Priority: Major > Fix For: 1.3.7 > > Attachments: HBASE-21903-branch-1.3-addendum.patch > > > Our internal deployments are based on branch-1.3. We will be using the major > compaction tool HBASE-19528 from [~churromorales] and the enhancements on top > of it HBASE-21883 on our 1.3 clusters. I would like to backport HBASE-19528 > to 1.3 and hence 1.4 as well. Since its a standalone tool without any other > dependency or code changes, I believe that should be ok. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-21903) Backport major compaction tool HBASE-19528 from to 1.4 and 1.3
[ https://issues.apache.org/jira/browse/HBASE-21903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-21903: --- Fix Version/s: (was: 1.4.13) 1.4.1 > Backport major compaction tool HBASE-19528 from to 1.4 and 1.3 > -- > > Key: HBASE-21903 > URL: https://issues.apache.org/jira/browse/HBASE-21903 > Project: HBase > Issue Type: Task > Components: Client, Compaction, tooling >Affects Versions: 1.3.3, 1.4.9 >Reporter: Thiruvel Thirumoolan >Assignee: Thiruvel Thirumoolan >Priority: Major > Fix For: 1.4.1, 1.3.7 > > Attachments: HBASE-21903-branch-1.3-addendum.patch > > > Our internal deployments are based on branch-1.3. We will be using the major > compaction tool HBASE-19528 from [~churromorales] and the enhancements on top > of it HBASE-21883 on our 1.3 clusters. I would like to backport HBASE-19528 > to 1.3 and hence 1.4 as well. Since its a standalone tool without any other > dependency or code changes, I believe that should be ok. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-22827) Expose multi-region merge in shell and Admin API
[ https://issues.apache.org/jira/browse/HBASE-22827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17037333#comment-17037333 ] Sakthi commented on HBASE-22827: Pushed to master. Working on backport to 2.3.0 > Expose multi-region merge in shell and Admin API > > > Key: HBASE-22827 > URL: https://issues.apache.org/jira/browse/HBASE-22827 > Project: HBase > Issue Type: Improvement > Components: Admin, shell >Reporter: Michael Stack >Assignee: Sakthi >Priority: Major > Fix For: 3.0.0 > > > HBASE-22777 adds being able to merge more than two regions at once. It is > only available internally currently for use by hbck2 doing fixup of overlaps > in hbase:meta. This issue is about exposing it via the Admin Interface and in > turn, via the shell. Probably best if old two region merge method is > deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-22827) Expose multi-region merge in shell and Admin API
[ https://issues.apache.org/jira/browse/HBASE-22827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-22827: --- Fix Version/s: 3.0.0 > Expose multi-region merge in shell and Admin API > > > Key: HBASE-22827 > URL: https://issues.apache.org/jira/browse/HBASE-22827 > Project: HBase > Issue Type: Improvement > Components: Admin, shell >Reporter: Michael Stack >Assignee: Sakthi >Priority: Major > Fix For: 3.0.0 > > > HBASE-22777 adds being able to merge more than two regions at once. It is > only available internally currently for use by hbck2 doing fixup of overlaps > in hbase:meta. This issue is about exposing it via the Admin Interface and in > turn, via the shell. Probably best if old two region merge method is > deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23562) [operator tools] Add a RegionsMerge tool that allows for merging multiple adjacent regions until a desired number of regions is reached.
[ https://issues.apache.org/jira/browse/HBASE-23562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17036525#comment-17036525 ] Sakthi commented on HBASE-23562: FYI: HBASE-23826 [~wchevreuil] . Just wanted to keep you in loop as that jira is related to merging multiple regions as well. > [operator tools] Add a RegionsMerge tool that allows for merging multiple > adjacent regions until a desired number of regions is reached. > > > Key: HBASE-23562 > URL: https://issues.apache.org/jira/browse/HBASE-23562 > Project: HBase > Issue Type: New Feature >Reporter: Wellington Chevreuil >Assignee: Wellington Chevreuil >Priority: Minor > > There's been a few occasions where different customers had faced the need to > reduce the number of regions for specific tables, either due to mistakenly > pre-split or after a purge in table data. This jira is for adding a simple > merge tool that takes the table name and the desired number of regions, then > perform region merges until the total number of regions for the given table > reached the passed valued. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[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 ] Sakthi updated HBASE-23826: --- Description: 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. was: 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 feature: i.e. 2.0.6+,2.1.6+, 2.2.1+ > [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-1.1.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.3.4#803005)
[jira] [Comment Edited] (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:comment-tabpanel=17036503#comment-17036503 ] Sakthi edited comment on HBASE-23826 at 2/13/20 9:11 PM: - Actually I just realized we can't make hbck2 access mergeRegions method from hbck service in any 2.0.x, 2.1.6-2.1.9 (i.e. if this change doesn't make into 2.1.9. else 2.1.8), 2.2.1-2.2.3. As HBASE-23827 would only be present from 3.0.0,2.3.0,2.2.4,2.1.10 was (Author: jatsakthi): Actually I just realized we can't make hbck2 access mergeRegions method from hbck service in any 2.0.x, 2.1.6-2.1.9 (i.e. if this change doesn't make into 2.1.9. else 2.1.8), 2.2.1-2.2.3. As HBASE-23827 would only be present from [3.0.0|https://issues.apache.org/jira/issues/?jql=project+%3D+HBASE+AND+fixVersion+%3D+3.0.0], [2.3.0|https://issues.apache.org/jira/issues/?jql=project+%3D+HBASE+AND+fixVersion+%3D+2.3.0], [2.2.4|https://issues.apache.org/jira/issues/?jql=project+%3D+HBASE+AND+fixVersion+%3D+2.2.4], [2.1.10|https://issues.apache.org/jira/issues/?jql=project+%3D+HBASE+AND+fixVersion+%3D+2.1.10] . > [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-1.1.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 feature: i.e. 2.0.6+,2.1.6+, 2.2.1+ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel=17036503#comment-17036503 ] Sakthi commented on HBASE-23826: Actually I just realized we can't make hbck2 access mergeRegions method from hbck service in any 2.0.x, 2.1.6-2.1.9 (i.e. if this change doesn't make into 2.1.9. else 2.1.8), 2.2.1-2.2.3. As HBASE-23827 would only be present from [3.0.0|https://issues.apache.org/jira/issues/?jql=project+%3D+HBASE+AND+fixVersion+%3D+3.0.0], [2.3.0|https://issues.apache.org/jira/issues/?jql=project+%3D+HBASE+AND+fixVersion+%3D+2.3.0], [2.2.4|https://issues.apache.org/jira/issues/?jql=project+%3D+HBASE+AND+fixVersion+%3D+2.2.4], [2.1.10|https://issues.apache.org/jira/issues/?jql=project+%3D+HBASE+AND+fixVersion+%3D+2.1.10] . > [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-1.1.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 feature: i.e. 2.0.6+,2.1.6+, 2.2.1+ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (HBASE-23743) Release 1.4.13
[ https://issues.apache.org/jira/browse/HBASE-23743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-23743 started by Sakthi. -- > Release 1.4.13 > -- > > Key: HBASE-23743 > URL: https://issues.apache.org/jira/browse/HBASE-23743 > Project: HBase > Issue Type: Task > Components: build, community >Affects Versions: 1.4.13 >Reporter: Sean Busbey >Assignee: Sakthi >Priority: Major > Fix For: 1.4.13 > > > over due for 1.4.13. I'll try to use the release manager scripts this time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HBASE-23743) Release 1.4.13
[ https://issues.apache.org/jira/browse/HBASE-23743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi reassigned HBASE-23743: -- Assignee: Sakthi (was: Sean Busbey) > Release 1.4.13 > -- > > Key: HBASE-23743 > URL: https://issues.apache.org/jira/browse/HBASE-23743 > Project: HBase > Issue Type: Task > Components: build, community >Affects Versions: 1.4.13 >Reporter: Sean Busbey >Assignee: Sakthi >Priority: Major > Fix For: 1.4.13 > > > over due for 1.4.13. I'll try to use the release manager scripts this time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23825) Increment proto conversion is broken
[ https://issues.apache.org/jira/browse/HBASE-23825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034925#comment-17034925 ] Sakthi commented on HBASE-23825: Yup, let me assign that one to myself [~apurtell] > Increment proto conversion is broken > > > Key: HBASE-23825 > URL: https://issues.apache.org/jira/browse/HBASE-23825 > Project: HBase > Issue Type: Bug > Components: Increment >Affects Versions: 1.4.0, 1.2.6, 1.3.2, 1.4.1, 1.5.0, 1.1.11, 1.3.3, 1.4.2, > 1.4.3, 1.4.4, 1.4.5, 1.3.2.1, 1.4.6, 1.4.8, 1.4.7, 1.4.9, 1.4.10, 1.3.4, > 1.3.5, 1.3.6, 1.4.11, 1.4.12 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Blocker > Fix For: 1.6.0, 1.3.7, 1.4.13 > > > While converting the request back to Increment using ProtobufUtil.toIncrement > we incorrectly use the optimization to avoid copying the byte > array(HBaseZeroCopyByteString#zeroCopyGetBytes) on a BoundedByteString. The > optimization was only meant for LiteralByteString where it is safe to use the > backing byte array, however it ends up being used to BoundedByteString which > is a subclass of LiteralByteString. This essentially breaks increments since > we end up creating wrong cells on the server side. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-23827) Add mergeRegions method to hbck service
Sakthi created HBASE-23827: -- Summary: Add mergeRegions method to hbck service Key: HBASE-23827 URL: https://issues.apache.org/jira/browse/HBASE-23827 Project: HBase Issue Type: Task Reporter: Sakthi Assignee: Sakthi Fix For: 3.0.0, 2.3.0, 2.1.9, 2.2.4 Let's add the mergeRegions method to the hbck service so that hbck2 can use it from the client side. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23827) [HBCK2] Add mergeRegions method to hbck service
[ https://issues.apache.org/jira/browse/HBASE-23827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-23827: --- Summary: [HBCK2] Add mergeRegions method to hbck service (was: Add mergeRegions method to hbck service) > [HBCK2] Add mergeRegions method to hbck service > --- > > Key: HBASE-23827 > URL: https://issues.apache.org/jira/browse/HBASE-23827 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.1.9, 2.2.4 > > > Let's add the mergeRegions method to the hbck service so that hbck2 can use > it from the client side. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23825) Increment proto conversion is broken
[ https://issues.apache.org/jira/browse/HBASE-23825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034107#comment-17034107 ] Sakthi commented on HBASE-23825: Let me take care of HBASE-23743 [~busbey]. > Increment proto conversion is broken > > > Key: HBASE-23825 > URL: https://issues.apache.org/jira/browse/HBASE-23825 > Project: HBase > Issue Type: Bug > Components: Increment >Affects Versions: 1.4.0, 1.3.2, 1.4.1, 1.5.0, 1.3.3, 1.4.2, 1.4.3, 1.4.4, > 1.4.5, 1.3.2.1, 1.4.6, 1.4.8, 1.4.7, 1.4.9, 1.4.10, 1.3.4, 1.3.5, 1.3.6, > 1.4.11, 1.4.12 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Blocker > Fix For: 1.6.0, 1.3.7, 1.4.13 > > > While converting the request back to Increment using ProtobufUtil.toIncrement > we incorrectly use the optimization to avoid copying the byte > array(HBaseZeroCopyByteString#zeroCopyGetBytes) on a BoundedByteString. The > optimization was only meant for LiteralByteString where it is safe to use the > backing byte array, however it ends up being used to BoundedByteString which > is a subclass of LiteralByteString. This essentially breaks increments since > we end up creating wrong cells on the server side. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-23826) [HBCK2] Expose Multi-Region merge feature via hbck2
Sakthi created HBASE-23826: -- Summary: [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 Fix For: hbase-operator-tools-1.1.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 feature: i.e. 2.0.6+,2.1.6+, 2.2.1+ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-22827) Expose multi-region merge in shell and Admin API
[ https://issues.apache.org/jira/browse/HBASE-22827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031504#comment-17031504 ] Sakthi commented on HBASE-22827: PR up for review. > Expose multi-region merge in shell and Admin API > > > Key: HBASE-22827 > URL: https://issues.apache.org/jira/browse/HBASE-22827 > Project: HBase > Issue Type: Improvement > Components: Admin, shell >Reporter: Michael Stack >Assignee: Sakthi >Priority: Major > > HBASE-22777 adds being able to merge more than two regions at once. It is > only available internally currently for use by hbck2 doing fixup of overlaps > in hbase:meta. This issue is about exposing it via the Admin Interface and in > turn, via the shell. Probably best if old two region merge method is > deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23748) Include HBASE-21284 to branch-2.2
[ https://issues.apache.org/jira/browse/HBASE-23748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-23748: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Include HBASE-21284 to branch-2.2 > - > > Key: HBASE-23748 > URL: https://issues.apache.org/jira/browse/HBASE-23748 > Project: HBase > Issue Type: Sub-task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Fix For: 2.2.3 > > Attachments: hbase-23748.branch-2.2.001.patch > > > HBASE-21284 was ought to be present in 2.2. But by the time the commit was > done, the branch had been cut already. Hence this Jira to track it's > inclusion. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23748) Include HBASE-21284 to branch-2.2
[ https://issues.apache.org/jira/browse/HBASE-23748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17027205#comment-17027205 ] Sakthi commented on HBASE-23748: I thought I had resolved this one. The commit went in. Let me close this one. Thanks all > Include HBASE-21284 to branch-2.2 > - > > Key: HBASE-23748 > URL: https://issues.apache.org/jira/browse/HBASE-23748 > Project: HBase > Issue Type: Sub-task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Fix For: 2.2.3 > > Attachments: hbase-23748.branch-2.2.001.patch > > > HBASE-21284 was ought to be present in 2.2. But by the time the commit was > done, the branch had been cut already. Hence this Jira to track it's > inclusion. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (HBASE-22827) Expose multi-region merge in shell and Admin API
[ https://issues.apache.org/jira/browse/HBASE-22827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-22827 started by Sakthi. -- > Expose multi-region merge in shell and Admin API > > > Key: HBASE-22827 > URL: https://issues.apache.org/jira/browse/HBASE-22827 > Project: HBase > Issue Type: Improvement > Components: Admin, shell >Reporter: Michael Stack >Assignee: Sakthi >Priority: Major > > HBASE-22777 adds being able to merge more than two regions at once. It is > only available internally currently for use by hbck2 doing fixup of overlaps > in hbase:meta. This issue is about exposing it via the Admin Interface and in > turn, via the shell. Probably best if old two region merge method is > deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-22827) Expose multi-region merge in shell and Admin API
[ https://issues.apache.org/jira/browse/HBASE-22827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026906#comment-17026906 ] Sakthi commented on HBASE-22827: Starting to work on this. > Expose multi-region merge in shell and Admin API > > > Key: HBASE-22827 > URL: https://issues.apache.org/jira/browse/HBASE-22827 > Project: HBase > Issue Type: Improvement > Components: Admin, shell >Reporter: Michael Stack >Assignee: Sakthi >Priority: Major > > HBASE-22777 adds being able to merge more than two regions at once. It is > only available internally currently for use by hbck2 doing fixup of overlaps > in hbase:meta. This issue is about exposing it via the Admin Interface and in > turn, via the shell. Probably best if old two region merge method is > deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-22587) Add a REST server to the nightly test that uses a cluster for simple operations
[ https://issues.apache.org/jira/browse/HBASE-22587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026306#comment-17026306 ] Sakthi commented on HBASE-22587: Yeah you are right [~ndimiduk] . I was thinking from an integration testing point of view. > Add a REST server to the nightly test that uses a cluster for simple > operations > --- > > Key: HBASE-22587 > URL: https://issues.apache.org/jira/browse/HBASE-22587 > Project: HBase > Issue Type: Sub-task > Components: REST, test >Reporter: Sakthi >Priority: Major > Labels: jdk11 > > Let's add rest server to the nightly test that uses a cluster for simple > operations to catch any possible rest server issues related to dependencies, > cnfe, npe etc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-22587) Add a REST server to the nightly test that uses a cluster for simple operations
[ https://issues.apache.org/jira/browse/HBASE-22587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026165#comment-17026165 ] Sakthi commented on HBASE-22587: All the tasks listed here issues that are related to getting our rest server work fine with jdk 11 I guess. But the parent issue hasn't yet been started/completed (No one has taken up the task yet). The motto was for us to continuously test our rest server by doing some simple cluster operations through the rest endpoint. [~stack] > Add a REST server to the nightly test that uses a cluster for simple > operations > --- > > Key: HBASE-22587 > URL: https://issues.apache.org/jira/browse/HBASE-22587 > Project: HBase > Issue Type: Sub-task > Components: REST, test >Reporter: Sakthi >Priority: Major > Labels: jdk11 > > Let's add rest server to the nightly test that uses a cluster for simple > operations to catch any possible rest server issues related to dependencies, > cnfe, npe etc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23748) Include HBASE-21284 to branch-2.2
[ https://issues.apache.org/jira/browse/HBASE-23748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026151#comment-17026151 ] Sakthi commented on HBASE-23748: Thanks [~elserj]. Let me get this in. > Include HBASE-21284 to branch-2.2 > - > > Key: HBASE-23748 > URL: https://issues.apache.org/jira/browse/HBASE-23748 > Project: HBase > Issue Type: Sub-task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Fix For: 2.2.3 > > Attachments: hbase-23748.branch-2.2.001.patch > > > HBASE-21284 was ought to be present in 2.2. But by the time the commit was > done, the branch had been cut already. Hence this Jira to track it's > inclusion. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23748) Include HBASE-21284 to branch-2.2
[ https://issues.apache.org/jira/browse/HBASE-23748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17025457#comment-17025457 ] Sakthi commented on HBASE-23748: [~apurtell] / [~liuml07] / [~elserj] can I get any of your +1s here, please? > Include HBASE-21284 to branch-2.2 > - > > Key: HBASE-23748 > URL: https://issues.apache.org/jira/browse/HBASE-23748 > Project: HBase > Issue Type: Sub-task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Fix For: 2.2.3 > > Attachments: hbase-23748.branch-2.2.001.patch > > > HBASE-21284 was ought to be present in 2.2. But by the time the commit was > done, the branch had been cut already. Hence this Jira to track it's > inclusion. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23180) Add a hbck2 testing tool
[ https://issues.apache.org/jira/browse/HBASE-23180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-23180: --- Release Note: This adds a new tool that spins up hbase on hadoop minicluster and mimicks actions of hbck2 to verify it's functionalities. The tool has been designed for easy addition of more compound actions (i.e. collection of actions) to verify hbck2. deleteRegionInMeta.sh is one such example of a compound action script. Summary: Add a hbck2 testing tool (was: Create a nightly build to verify hbck2) > Add a hbck2 testing tool > > > Key: HBASE-23180 > URL: https://issues.apache.org/jira/browse/HBASE-23180 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Labels: hbck2 > Fix For: hbase-operator-tools-1.1.0 > > > Quoting myself from the discussion thread from the dev mailing list "*How do > we test hbck2?*" - > "Planning to start working on a nightly build that can spin up a > mini-cluster, load some data into it, do some actions to bring the cluster > into an undesirable state that hbck2 can fix and then invoke the hbck2 to see > if things work well. > > Plan is to start small with one of the hbck2 commands and remaining ones can > be added incrementally. As of now I would like to start with making sure the > job uses one of the hbase versions (probably 2.1.x/2.2.x), we can discuss > about the need to run the job against all the present hbase versions/taking > in a bunch of hbase versions as input and running against them/or just a > single version. > > The job script would be located in our operator-tools repo." -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-23180) Add a hbck2 testing tool
[ https://issues.apache.org/jira/browse/HBASE-23180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi resolved HBASE-23180. Resolution: Fixed > Add a hbck2 testing tool > > > Key: HBASE-23180 > URL: https://issues.apache.org/jira/browse/HBASE-23180 > Project: HBase > Issue Type: Task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Labels: hbck2 > Fix For: hbase-operator-tools-1.1.0 > > > Quoting myself from the discussion thread from the dev mailing list "*How do > we test hbck2?*" - > "Planning to start working on a nightly build that can spin up a > mini-cluster, load some data into it, do some actions to bring the cluster > into an undesirable state that hbck2 can fix and then invoke the hbck2 to see > if things work well. > > Plan is to start small with one of the hbck2 commands and remaining ones can > be added incrementally. As of now I would like to start with making sure the > job uses one of the hbase versions (probably 2.1.x/2.2.x), we can discuss > about the need to run the job against all the present hbase versions/taking > in a bunch of hbase versions as input and running against them/or just a > single version. > > The job script would be located in our operator-tools repo." -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23748) Include HBASE-21284 to branch-2.2
[ https://issues.apache.org/jira/browse/HBASE-23748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-23748: --- Fix Version/s: 2.2.3 Status: Patch Available (was: In Progress) > Include HBASE-21284 to branch-2.2 > - > > Key: HBASE-23748 > URL: https://issues.apache.org/jira/browse/HBASE-23748 > Project: HBase > Issue Type: Sub-task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Fix For: 2.2.3 > > Attachments: hbase-23748.branch-2.2.001.patch > > > HBASE-21284 was ought to be present in 2.2. But by the time the commit was > done, the branch had been cut already. Hence this Jira to track it's > inclusion. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23748) Include HBASE-21284 to branch-2.2
[ https://issues.apache.org/jira/browse/HBASE-23748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-23748: --- Attachment: hbase-23748.branch-2.2.001.patch > Include HBASE-21284 to branch-2.2 > - > > Key: HBASE-23748 > URL: https://issues.apache.org/jira/browse/HBASE-23748 > Project: HBase > Issue Type: Sub-task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Attachments: hbase-23748.branch-2.2.001.patch > > > HBASE-21284 was ought to be present in 2.2. But by the time the commit was > done, the branch had been cut already. Hence this Jira to track it's > inclusion. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (HBASE-23748) Include HBASE-21284 to branch-2.2
[ https://issues.apache.org/jira/browse/HBASE-23748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-23748 started by Sakthi. -- > Include HBASE-21284 to branch-2.2 > - > > Key: HBASE-23748 > URL: https://issues.apache.org/jira/browse/HBASE-23748 > Project: HBase > Issue Type: Sub-task >Reporter: Sakthi >Assignee: Sakthi >Priority: Major > Attachments: hbase-23748.branch-2.2.001.patch > > > HBASE-21284 was ought to be present in 2.2. But by the time the commit was > done, the branch had been cut already. Hence this Jira to track it's > inclusion. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-23748) Include HBASE-21284 to branch-2.2
Sakthi created HBASE-23748: -- Summary: Include HBASE-21284 to branch-2.2 Key: HBASE-23748 URL: https://issues.apache.org/jira/browse/HBASE-23748 Project: HBase Issue Type: Sub-task Reporter: Sakthi Assignee: Sakthi HBASE-21284 was ought to be present in 2.2. But by the time the commit was done, the branch had been cut already. Hence this Jira to track it's inclusion. -- This message was sent by Atlassian Jira (v8.3.4#803005)
