[jira] [Comment Edited] (HBASE-28844) Align the fixed issues in git and jira
[
https://issues.apache.org/jira/browse/HBASE-28844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885509#comment-17885509
]
Duo Zhang edited comment on HBASE-28844 at 9/30/24 10:28 AM:
-
I've written a simple script to output the differences.
https://github.com/Apache9/hbase-release-audit/blob/main/audit-git-commit-jira-issue.py
This is the result
Commit to previous release but not in current release:
{noformat}
HBASE-12350
HBASE-17553
HBASE-18187
HBASE-18190
HBASE-18282
HBASE-18431
HBASE-18514
HBASE-18594
HBASE-18595
HBASE-18615
HBASE-18653
HBASE-18817
HBASE-18819
HBASE-18828
HBASE-18833
HBASE-18933
HBASE-19197
HBASE-19315
HBASE-19407
HBASE-19648
HBASE-19670
HBASE-19716
HBASE-19860
HBASE-19888
HBASE-20113
HBASE-20142
HBASE-20233
HBASE-20246
HBASE-20247
HBASE-20415
HBASE-20462
HBASE-20464
{noformat}
Issues in jira but not in git commits:
{noformat}
HBASE-13126 Umbrella for release notes
HBASE-13992 In 2.0.0 but reverted(hbase-spark)
HBASE-14123 In 2.0.0 but reverted(backup&restore)
HBASE-14150 In 2.0.0 but reverted(hbase-spark)
HBASE-14158 In 2.0.0 but reverted(hbase-spark)
HBASE-14159 In 2.0.0 but reverted(hbase-spark)
HBASE-14161 No actual code commit, jenkins change, remove fix version
HBASE-14181 In 2.0.0 but reverted(hbase-spark)
HBASE-14184 In 2.0.0 but reverted(hbase-spark)
HBASE-14340 In 2.0.0 but reverted(hbase-spark)
HBASE-14375 In 2.0.0 but reverted(hbase-spark)
HBASE-14377 In 2.0.0 but reverted(hbase-spark)
HBASE-14406 In 2.0.0 but reverted(hbase-spark)
HBASE-14515 In 2.0.0 but reverted(hbase-spark)
HBASE-14789 In 2.0.0 but reverted(hbase-spark)
HBASE-14849 In 2.0.0 but reverted(hbase-spark)
HBASE-15161 Umbrella for release notes
HBASE-15184 In 2.0.0 but reverted(hbase-spark)
HBASE-15282 In 2.0.0 but reverted(hbase-spark)
HBASE-15291 Should be in 2.0.0, fixed
HBASE-15310 In 2.0.0 but reverted(hbase-spark)
HBASE-15333 In 2.0.0 but reverted(hbase-spark)
HBASE-15336 In 2.0.0 but reverted(hbase-spark)
HBASE-15434 In 2.0.0 but reverted(hbase-spark)
HBASE-15466 In 2.0.0 so do not need to set 3.0.0 fix version, fixed
HBASE-15473 In 2.0.0 but reverted(hbase-spark)
HBASE-15572 In 2.0.0 but reverted(hbase-spark)
HBASE-15597 In 2.0.0 but reverted(hbase-spark)
HBASE-15809 Umbrella issue for release note
HBASE-16638 In 2.0.0 but reverted(hbase-spark)
HBASE-16804 In 2.0.0 but reverted(hbase-spark)
HBASE-16823 In 2.0.0 but reverted(hbase-spark)
HBASE-17546 In 2.0.0 but reverted(hbase-spark)
HBASE-17547 In 2.0.0 but reverted(hbase-spark)
HBASE-17549 In 2.0.0 but reverted(hbase-spark)
HBASE-17574 In 2.0.0 but reverted(hbase-spark)
HBASE-17664 Umbrella issue without release note, remove fix version
HBASE-17852 No actual code commit, remove fix version
HBASE-17909 In 2.0.0 but reverted(hbase-spark)
HBASE-17918 In 2.0.0 but reverted(serial replication)
HBASE-17919 Umbrella issue without release note, remove fix version
HBASE-17933 In 2.0.0 but reverted(hbase-spark)
HBASE-18070 Umbrella issue for release note
HBASE-18095 Umbrella issue without release note but the title provide
something, so leave it as is
HBASE-18175 In 2.0.0 but reverted(hbase-spark)
HBASE-18176 In 2.0.0 but reverted(hbase-spark)
HBASE-18326 No actual code commit, remove fix version
HBASE-18391 No actual code commit, remove fix version
HBASE-18506 No actual code commit, remove fix version
HBASE-18622 No actual code commit, remove fix version
HBASE-18646 In 2.0.0 but reverted(backup&restore)
HBASE-18659 Umbrella issue without release note but the title provide
something, so leave it as is
HBASE-19064 Umbrella issue without release note but the title provide
something, so leave it as is
HBASE-19068 In 2.0.0, change fix version
HBASE-19174 In 2.0.0, change fix version
HBASE-19397 Umbrella issue for release note
HBASE-19506 In 2.0.0, change fix version
HBASE-19547 In 2.0.0, change fix version
HBASE-20006 HBASE-20011 is committed to branch-2 with HBASE-20006 in
commit message, so the tool think HBASE-20006 is already in 2.0.0 but actually
it is not
HBASE-20046 Umbrella issue for release note
HBASE-20068 In 2.0.0, change fix version
HBASE-20112 In 2.0.0, change fix version
HBASE-20152 Um
[jira] [Commented] (HBASE-28884) SFT's BrokenStoreFileCleaner may cause data loss
[ https://issues.apache.org/jira/browse/HBASE-28884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885844#comment-17885844 ] Duo Zhang commented on HBASE-28884: --- Then please add these explainations to the code base? Thanks. > SFT's BrokenStoreFileCleaner may cause data loss > > > Key: HBASE-28884 > URL: https://issues.apache.org/jira/browse/HBASE-28884 > Project: HBase > Issue Type: Bug >Affects Versions: 2.6.0, 3.0.0-beta-1, 2.7.0, 2.5.10 >Reporter: Wellington Chevreuil >Assignee: Wellington Chevreuil >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0, 3.0.0-beta-2 > > > When having this BrokenStoreFileCleaner enabled, one of our customers has run > into a data loss situation, probably due to a race condition between regions > getting moved out of the regionserver while the BrokenStoreFileCleaner was > checking this region's files eligibility for deletion. We have seen that the > file got deleted by the given region server, around the same time the region > got closed on this region server. I believe a race condition during region > close is possible here: > 1) In BrokenStoreFileCleaner, for each region online on the given RS, we get > the list of files in the store dirs, then iterate through it [1]; > 2) For each file listed, we perform several checks, including this one [2] > that checks if the file is "active" > The problem is, if the region for the file we are checking got closed between > point #1 and #2, by the time we check if the file is active in [2], the store > may have already been closed as part of the region closure, so this check > would consider the file as deletable. > One simple solution is to check if the store's region is still open before > proceeding with deleting the file. > [1] > https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/BrokenStoreFileCleaner.java#L99 > [2] > https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/BrokenStoreFileCleaner.java#L133 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-24177) MetricsTable#updateFlushTime is wrong
[ https://issues.apache.org/jira/browse/HBASE-24177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-24177. --- Resolution: Fixed I only re applied on master and branch-3. > MetricsTable#updateFlushTime is wrong > - > > Key: HBASE-24177 > URL: https://issues.apache.org/jira/browse/HBASE-24177 > Project: HBase > Issue Type: Bug > Components: metrics >Affects Versions: 2.2.1 >Reporter: ramkrishna.s.vasudevan >Assignee: Gaurav Kanade >Priority: Minor > Fix For: 2.2.5, 2.3.0, 3.0.0-alpha-1 > > Attachments: after.png, before.png > > > MetricsRegionServer does an update on the MetricsRegionServerSource, > MetricsTable etc. > While doing updateFlushTime, the time taken for flush is rightly updated in > the RegionServerSource but at the MetricsTable level we update the > memstoresize instead of the time. > This applies from 1.1 version onwards. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (HBASE-24177) MetricsTable#updateFlushTime is wrong
[ https://issues.apache.org/jira/browse/HBASE-24177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reopened HBASE-24177: --- Missed jira id > MetricsTable#updateFlushTime is wrong > - > > Key: HBASE-24177 > URL: https://issues.apache.org/jira/browse/HBASE-24177 > Project: HBase > Issue Type: Bug > Components: metrics >Affects Versions: 2.2.1 >Reporter: ramkrishna.s.vasudevan >Assignee: Gaurav Kanade >Priority: Minor > Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.5 > > Attachments: after.png, before.png > > > MetricsRegionServer does an update on the MetricsRegionServerSource, > MetricsTable etc. > While doing updateFlushTime, the time taken for flush is rightly updated in > the RegionServerSource but at the MetricsTable level we update the > memstoresize instead of the time. > This applies from 1.1 version onwards. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HBASE-24109) Change fork count from 0.5C to 0.25C
[ https://issues.apache.org/jira/browse/HBASE-24109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885760#comment-17885760 ] Duo Zhang commented on HBASE-24109: --- We still reference the jira id for the parent issue, so remove fix versions here to reduce confusing. > Change fork count from 0.5C to 0.25C > > > Key: HBASE-24109 > URL: https://issues.apache.org/jira/browse/HBASE-24109 > Project: HBase > Issue Type: Sub-task >Reporter: Michael Stack >Assignee: Michael Stack >Priority: Major > Fix For: 3.0.0-alpha-1, 2.3.0 > > > The parent issue, not surprisingly, shows that 0.25C fork count is more > likely to pass than the more aggressive 0.5C. Let me down branch-2.3/master > branches to 0.25C (I've already done it on branch-2). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-24109) Change fork count from 0.5C to 0.25C
[ https://issues.apache.org/jira/browse/HBASE-24109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-24109: -- Fix Version/s: (was: 3.0.0-alpha-1) (was: 2.3.0) > Change fork count from 0.5C to 0.25C > > > Key: HBASE-24109 > URL: https://issues.apache.org/jira/browse/HBASE-24109 > Project: HBase > Issue Type: Sub-task >Reporter: Michael Stack >Assignee: Michael Stack >Priority: Major > > The parent issue, not surprisingly, shows that 0.25C fork count is more > likely to pass than the more aggressive 0.5C. Let me down branch-2.3/master > branches to 0.25C (I've already done it on branch-2). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-24001) The "HBase Nightly" job may exhaust all executors - and create a deadlock
[ https://issues.apache.org/jira/browse/HBASE-24001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-24001: -- Fix Version/s: (was: 3.0.0-alpha-1) (was: 2.3.0) > The "HBase Nightly" job may exhaust all executors - and create a deadlock > - > > Key: HBASE-24001 > URL: https://issues.apache.org/jira/browse/HBASE-24001 > Project: HBase > Issue Type: Bug > Components: jenkins >Reporter: Zoltan Haindrich >Assignee: Michael Stack >Priority: Major > > What seems to happen is: > * the job needs more and more executors to run > * in case there are several of them launched in parallel (different branches) > say 5 > * they take up all available executors labeled "Hadoop" and then they wait > for more indefinetly > I've killed a few builds...see my notes here: > https://the-asf.slack.com/archives/C7M1AFYLS/p1584442366000900 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-24001) The "HBase Nightly" job may exhaust all executors - and create a deadlock
[ https://issues.apache.org/jira/browse/HBASE-24001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-24001: -- Component/s: jenkins > The "HBase Nightly" job may exhaust all executors - and create a deadlock > - > > Key: HBASE-24001 > URL: https://issues.apache.org/jira/browse/HBASE-24001 > Project: HBase > Issue Type: Bug > Components: jenkins >Reporter: Zoltan Haindrich >Assignee: Michael Stack >Priority: Major > Fix For: 3.0.0-alpha-1, 2.3.0 > > > What seems to happen is: > * the job needs more and more executors to run > * in case there are several of them launched in parallel (different branches) > say 5 > * they take up all available executors labeled "Hadoop" and then they wait > for more indefinetly > I've killed a few builds...see my notes here: > https://the-asf.slack.com/archives/C7M1AFYLS/p1584442366000900 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (HBASE-28844) Align the fixed issues in git and jira
[
https://issues.apache.org/jira/browse/HBASE-28844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885509#comment-17885509
]
Duo Zhang edited comment on HBASE-28844 at 9/28/24 2:43 PM:
I've written a simple script to output the differences.
https://github.com/Apache9/hbase-release-audit/blob/main/audit-git-commit-jira-issue.py
This is the result
Commit to previous release but not in current release:
{noformat}
HBASE-12350
HBASE-17553
HBASE-18187
HBASE-18190
HBASE-18282
HBASE-18431
HBASE-18514
HBASE-18594
HBASE-18595
HBASE-18615
HBASE-18653
HBASE-18817
HBASE-18819
HBASE-18828
HBASE-18833
HBASE-18933
HBASE-19197
HBASE-19315
HBASE-19407
HBASE-19648
HBASE-19670
HBASE-19716
HBASE-19860
HBASE-19888
HBASE-20113
HBASE-20142
HBASE-20233
HBASE-20246
HBASE-20247
HBASE-20415
HBASE-20462
HBASE-20464
{noformat}
Issues in jira but not in git commits:
{noformat}
HBASE-13126 Umbrella for release notes
HBASE-13992 In 2.0.0 but reverted(hbase-spark)
HBASE-14123 In 2.0.0 but reverted(backup&restore)
HBASE-14150 In 2.0.0 but reverted(hbase-spark)
HBASE-14158 In 2.0.0 but reverted(hbase-spark)
HBASE-14159 In 2.0.0 but reverted(hbase-spark)
HBASE-14161 No actual code commit, jenkins change, remove fix version
HBASE-14181 In 2.0.0 but reverted(hbase-spark)
HBASE-14184 In 2.0.0 but reverted(hbase-spark)
HBASE-14340 In 2.0.0 but reverted(hbase-spark)
HBASE-14375 In 2.0.0 but reverted(hbase-spark)
HBASE-14377 In 2.0.0 but reverted(hbase-spark)
HBASE-14406 In 2.0.0 but reverted(hbase-spark)
HBASE-14515 In 2.0.0 but reverted(hbase-spark)
HBASE-14789 In 2.0.0 but reverted(hbase-spark)
HBASE-14849 In 2.0.0 but reverted(hbase-spark)
HBASE-15161 Umbrella for release notes
HBASE-15184 In 2.0.0 but reverted(hbase-spark)
HBASE-15282 In 2.0.0 but reverted(hbase-spark)
HBASE-15291 Should be in 2.0.0, fixed
HBASE-15310 In 2.0.0 but reverted(hbase-spark)
HBASE-15333 In 2.0.0 but reverted(hbase-spark)
HBASE-15336 In 2.0.0 but reverted(hbase-spark)
HBASE-15434 In 2.0.0 but reverted(hbase-spark)
HBASE-15466 In 2.0.0 so do not need to set 3.0.0 fix version, fixed
HBASE-15473 In 2.0.0 but reverted(hbase-spark)
HBASE-15572 In 2.0.0 but reverted(hbase-spark)
HBASE-15597 In 2.0.0 but reverted(hbase-spark)
HBASE-15809 Umbrella issue for release note
HBASE-16638 In 2.0.0 but reverted(hbase-spark)
HBASE-16804 In 2.0.0 but reverted(hbase-spark)
HBASE-16823 In 2.0.0 but reverted(hbase-spark)
HBASE-17546 In 2.0.0 but reverted(hbase-spark)
HBASE-17547 In 2.0.0 but reverted(hbase-spark)
HBASE-17549 In 2.0.0 but reverted(hbase-spark)
HBASE-17574 In 2.0.0 but reverted(hbase-spark)
HBASE-17664 Umbrella issue without release note, remove fix version
HBASE-17852 No actual code commit, remove fix version
HBASE-17909 In 2.0.0 but reverted(hbase-spark)
HBASE-17918 In 2.0.0 but reverted(serial replication)
HBASE-17919 Umbrella issue without release note, remove fix version
HBASE-17933 In 2.0.0 but reverted(hbase-spark)
HBASE-18070 Umbrella issue for release note
HBASE-18095 Umbrella issue without release note but the title provide
something, so leave it as is
HBASE-18175 In 2.0.0 but reverted(hbase-spark)
HBASE-18176 In 2.0.0 but reverted(hbase-spark)
HBASE-18326 No actual code commit, remove fix version
HBASE-18391 No actual code commit, remove fix version
HBASE-18506 No actual code commit, remove fix version
HBASE-18622 No actual code commit, remove fix version
HBASE-18646 In 2.0.0 but reverted(backup&restore)
HBASE-18659 Umbrella issue without release note but the title provide
something, so leave it as is
HBASE-19064 Umbrella issue without release note but the title provide
something, so leave it as is
HBASE-19068 In 2.0.0, change fix version
HBASE-19174 In 2.0.0, change fix version
HBASE-19397 Umbrella issue for release note
HBASE-19506 In 2.0.0, change fix version
HBASE-19547 In 2.0.0, change fix version
HBASE-20006 HBASE-20011 is committed to branch-2 with HBASE-20006 in
commit message, so the tool think HBASE-20006 is already in 2.0.0 but actually
it is not
HBASE-20046 Umbrella issue for release note
HBASE-20068 In 2.0.0, change fix version
HBASE-20112 In 2.0.0, change fix version
HBASE-20152 Umbr
[jira] [Resolved] (HBASE-23601) OutputSink.WriterThread exception gets stuck and repeated indefinietly
[
https://issues.apache.org/jira/browse/HBASE-23601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-23601.
---
Fix Version/s: 3.0.0-beta-2
(was: 3.0.0-alpha-1)
Resolution: Fixed
> OutputSink.WriterThread exception gets stuck and repeated indefinietly
> --
>
> Key: HBASE-23601
> URL: https://issues.apache.org/jira/browse/HBASE-23601
> Project: HBase
> Issue Type: Bug
> Components: read replicas
>Affects Versions: 2.2.2
>Reporter: Szabolcs Bukros
>Assignee: Szabolcs Bukros
>Priority: Major
> Fix For: 3.0.0-beta-2, 2.3.0
>
>
> When a WriterThread runs into an exception (ie: NotServingRegionException),
> the exception is stored in the controller. It is never removed and can not be
> overwritten either.
>
> {code:java}
> public void run() {
> try {
> doRun();
> } catch (Throwable t) {
> LOG.error("Exiting thread", t);
> controller.writerThreadError(t);
> }
> }{code}
> Thanks to this every time PipelineController.checkForErrors() is called the
> same old exception is rethrown.
>
> For example in RegionReplicaReplicationEndpoint.replicate there is a while
> loop that does the actual replicating. Every time it loops, it calls
> checkForErrors(), catches the rethrown exception, logs it but does nothing
> about it. This results in ~2GB log files in ~5min in my experience.
>
> My proposal would be to clean up the stored exception when it reaches
> RegionReplicaReplicationEndpoint.replicate and make sure we restart the
> WriterThread that died throwing it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-23150) TestBulkLoadReplication is broken
[ https://issues.apache.org/jira/browse/HBASE-23150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-23150. --- Resolution: Cannot Reproduce > TestBulkLoadReplication is broken > - > > Key: HBASE-23150 > URL: https://issues.apache.org/jira/browse/HBASE-23150 > Project: HBase > Issue Type: Bug >Affects Versions: 3.0.0-alpha-1 >Reporter: Peter Somogyi >Assignee: Wellington Chevreuil >Priority: Major > > Test is failing. See > [https://builds.apache.org/job/HBase-Flaky-Tests/job/master/4506/testReport/org.apache.hadoop.hbase.regionserver/TestBulkLoadReplication/testBulkLoadReplicationActiveActive/] > h3. Stacktrace > java.lang.AssertionError at > org.apache.hadoop.hbase.regionserver.TestBulkLoadReplication.assertTableHasValue(TestBulkLoadReplication.java:295) > at > org.apache.hadoop.hbase.regionserver.TestBulkLoadReplication.assertBulkLoadConditions(TestBulkLoadReplication.java:275) > at > org.apache.hadoop.hbase.regionserver.TestBulkLoadReplication.testBulkLoadReplicationActiveActive(TestBulkLoadReplication.java:236) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (HBASE-23601) OutputSink.WriterThread exception gets stuck and repeated indefinietly
[
https://issues.apache.org/jira/browse/HBASE-23601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang reopened HBASE-23601:
---
Missed on master.
Reopen
> OutputSink.WriterThread exception gets stuck and repeated indefinietly
> --
>
> Key: HBASE-23601
> URL: https://issues.apache.org/jira/browse/HBASE-23601
> Project: HBase
> Issue Type: Bug
> Components: read replicas
>Affects Versions: 2.2.2
>Reporter: Szabolcs Bukros
>Assignee: Szabolcs Bukros
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0
>
>
> When a WriterThread runs into an exception (ie: NotServingRegionException),
> the exception is stored in the controller. It is never removed and can not be
> overwritten either.
>
> {code:java}
> public void run() {
> try {
> doRun();
> } catch (Throwable t) {
> LOG.error("Exiting thread", t);
> controller.writerThreadError(t);
> }
> }{code}
> Thanks to this every time PipelineController.checkForErrors() is called the
> same old exception is rethrown.
>
> For example in RegionReplicaReplicationEndpoint.replicate there is a while
> loop that does the actual replicating. Every time it loops, it calls
> checkForErrors(), catches the rethrown exception, logs it but does nothing
> about it. This results in ~2GB log files in ~5min in my experience.
>
> My proposal would be to clean up the stored exception when it reaches
> RegionReplicaReplicationEndpoint.replicate and make sure we restart the
> WriterThread that died throwing it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (HBASE-23224) Delete the TODO ("get rid of allocations") tag in the WALProcedureStore class
[
https://issues.apache.org/jira/browse/HBASE-23224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang reopened HBASE-23224:
---
Not fixed yet, not sure why it is marked as resolved.
> Delete the TODO ("get rid of allocations") tag in the WALProcedureStore class
> --
>
> Key: HBASE-23224
> URL: https://issues.apache.org/jira/browse/HBASE-23224
> Project: HBase
> Issue Type: Improvement
> Components: proc-v2
>Affects Versions: 1.2.0, 1.3.0, 2.1.0, 2.2.0
>Reporter: lixiaobao
>Assignee: lixiaobao
>Priority: Trivial
> Fix For: 3.0.0-alpha-1
>
>
> {code:java}
> // update webui circular buffers (TODO: get rid of allocations)
> final SyncMetrics syncMetrics = new SyncMetrics();
> syncMetrics.timestamp = currentTs;
> syncMetrics.syncWaitMs = syncWaitMs;
> syncMetrics.syncedEntries = slotIndex;
> syncMetrics.totalSyncedBytes = totalSyncedToStore;
> syncMetrics.syncedPerSec = syncedPerSec;
> syncMetricsQueue.add(syncMetrics);
> {code}
> Delete the TODO tag.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-23224) Delete the TODO ("get rid of allocations") tag in the WALProcedureStore class
[
https://issues.apache.org/jira/browse/HBASE-23224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-23224:
--
Fix Version/s: (was: 3.0.0-alpha-1)
> Delete the TODO ("get rid of allocations") tag in the WALProcedureStore class
> --
>
> Key: HBASE-23224
> URL: https://issues.apache.org/jira/browse/HBASE-23224
> Project: HBase
> Issue Type: Improvement
> Components: proc-v2
>Affects Versions: 1.2.0, 1.3.0, 2.1.0, 2.2.0
>Reporter: lixiaobao
>Assignee: lixiaobao
>Priority: Trivial
>
> {code:java}
> // update webui circular buffers (TODO: get rid of allocations)
> final SyncMetrics syncMetrics = new SyncMetrics();
> syncMetrics.timestamp = currentTs;
> syncMetrics.syncWaitMs = syncWaitMs;
> syncMetrics.syncedEntries = slotIndex;
> syncMetrics.totalSyncedBytes = totalSyncedToStore;
> syncMetrics.syncedPerSec = syncedPerSec;
> syncMetricsQueue.add(syncMetrics);
> {code}
> Delete the TODO tag.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (HBASE-23150) TestBulkLoadReplication is broken
[ https://issues.apache.org/jira/browse/HBASE-23150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reopened HBASE-23150: --- > TestBulkLoadReplication is broken > - > > Key: HBASE-23150 > URL: https://issues.apache.org/jira/browse/HBASE-23150 > Project: HBase > Issue Type: Bug >Affects Versions: 3.0.0-alpha-1 >Reporter: Peter Somogyi >Assignee: Wellington Chevreuil >Priority: Major > > Test is failing. See > [https://builds.apache.org/job/HBase-Flaky-Tests/job/master/4506/testReport/org.apache.hadoop.hbase.regionserver/TestBulkLoadReplication/testBulkLoadReplicationActiveActive/] > h3. Stacktrace > java.lang.AssertionError at > org.apache.hadoop.hbase.regionserver.TestBulkLoadReplication.assertTableHasValue(TestBulkLoadReplication.java:295) > at > org.apache.hadoop.hbase.regionserver.TestBulkLoadReplication.assertBulkLoadConditions(TestBulkLoadReplication.java:275) > at > org.apache.hadoop.hbase.regionserver.TestBulkLoadReplication.testBulkLoadReplicationActiveActive(TestBulkLoadReplication.java:236) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-23100) Make a 3.1.0 hbase-thirdparty release
[ https://issues.apache.org/jira/browse/HBASE-23100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-23100: -- Fix Version/s: (was: 3.0.0-alpha-1) > Make a 3.1.0 hbase-thirdparty release > - > > Key: HBASE-23100 > URL: https://issues.apache.org/jira/browse/HBASE-23100 > Project: HBase > Issue Type: Task > Components: thirdparty >Reporter: Michael Stack >Assignee: Michael Stack >Priority: Major > > Make a hbase-thirdparty release. 3.0.0 broke out a gson module out of the > miscellaneous where it used live. 3.1.0 is about updating the dependencies in > hbase-thirdparty. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-23150) TestBulkLoadReplication is broken
[ https://issues.apache.org/jira/browse/HBASE-23150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-23150: -- Fix Version/s: (was: 3.0.0-alpha-1) > TestBulkLoadReplication is broken > - > > Key: HBASE-23150 > URL: https://issues.apache.org/jira/browse/HBASE-23150 > Project: HBase > Issue Type: Bug >Affects Versions: 3.0.0-alpha-1 >Reporter: Peter Somogyi >Assignee: Wellington Chevreuil >Priority: Major > > Test is failing. See > [https://builds.apache.org/job/HBase-Flaky-Tests/job/master/4506/testReport/org.apache.hadoop.hbase.regionserver/TestBulkLoadReplication/testBulkLoadReplicationActiveActive/] > h3. Stacktrace > java.lang.AssertionError at > org.apache.hadoop.hbase.regionserver.TestBulkLoadReplication.assertTableHasValue(TestBulkLoadReplication.java:295) > at > org.apache.hadoop.hbase.regionserver.TestBulkLoadReplication.assertBulkLoadConditions(TestBulkLoadReplication.java:275) > at > org.apache.hadoop.hbase.regionserver.TestBulkLoadReplication.testBulkLoadReplicationActiveActive(TestBulkLoadReplication.java:236) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-23100) Make a 3.1.0 hbase-thirdparty release
[ https://issues.apache.org/jira/browse/HBASE-23100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-23100: -- Component/s: community > Make a 3.1.0 hbase-thirdparty release > - > > Key: HBASE-23100 > URL: https://issues.apache.org/jira/browse/HBASE-23100 > Project: HBase > Issue Type: Task > Components: community, thirdparty >Reporter: Michael Stack >Assignee: Michael Stack >Priority: Major > > Make a hbase-thirdparty release. 3.0.0 broke out a gson module out of the > miscellaneous where it used live. 3.1.0 is about updating the dependencies in > hbase-thirdparty. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-22992) Blog post for hbtop on hbase.apache.org
[ https://issues.apache.org/jira/browse/HBASE-22992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-22992: -- Fix Version/s: (was: 3.0.0-alpha-1) > Blog post for hbtop on hbase.apache.org > --- > > Key: HBASE-22992 > URL: https://issues.apache.org/jira/browse/HBASE-22992 > Project: HBase > Issue Type: Sub-task > Components: hbtop >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HBASE-22834) Remove deprecated methods from HBaseTestingUtility
[
https://issues.apache.org/jira/browse/HBASE-22834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885586#comment-17885586
]
Duo Zhang commented on HBASE-22834:
---
Since there is no commit with this jira issue and all the sub tasks have their
own release note, remove fix versions from this issue.
> Remove deprecated methods from HBaseTestingUtility
> --
>
> Key: HBASE-22834
> URL: https://issues.apache.org/jira/browse/HBASE-22834
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 3.0.0-alpha-1
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
>
> {{HBaseTestingUtility}} has some deprecated methods, which should be removed
> for 3.0.0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-22834) Remove deprecated methods from HBaseTestingUtility
[
https://issues.apache.org/jira/browse/HBASE-22834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-22834:
--
Fix Version/s: (was: 3.0.0-alpha-1)
> Remove deprecated methods from HBaseTestingUtility
> --
>
> Key: HBASE-22834
> URL: https://issues.apache.org/jira/browse/HBASE-22834
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 3.0.0-alpha-1
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
>
> {{HBaseTestingUtility}} has some deprecated methods, which should be removed
> for 3.0.0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (HBASE-22740) [RSGroup] Forward-port HBASE-22658 to master branch
[ https://issues.apache.org/jira/browse/HBASE-22740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reopened HBASE-22740: --- Missed jira id in commit message, revert and re apply. > [RSGroup] Forward-port HBASE-22658 to master branch > --- > > Key: HBASE-22740 > URL: https://issues.apache.org/jira/browse/HBASE-22740 > Project: HBase > Issue Type: Bug > Components: rsgroup >Affects Versions: 2.0.6, 2.2.3, 2.1.9 >Reporter: Reid Chan >Assignee: Reid Chan >Priority: Major > Fix For: 3.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-22484) Javadoc Warnings: Fix warnings coming due to @result tag in TestCoprocessorWhitelistMasterObserver
[ https://issues.apache.org/jira/browse/HBASE-22484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-22484. --- Resolution: Fixed > Javadoc Warnings: Fix warnings coming due to @result tag in > TestCoprocessorWhitelistMasterObserver > -- > > Key: HBASE-22484 > URL: https://issues.apache.org/jira/browse/HBASE-22484 > Project: HBase > Issue Type: Bug > Components: documentation >Affects Versions: 3.0.0-alpha-1 >Reporter: Murtaza Hassan >Assignee: Murtaza Hassan >Priority: Trivial > Labels: beginner > Fix For: 3.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (HBASE-22484) Javadoc Warnings: Fix warnings coming due to @result tag in TestCoprocessorWhitelistMasterObserver
[ https://issues.apache.org/jira/browse/HBASE-22484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reopened HBASE-22484: --- Wrong jira id in commit message, reopen and reapply. > Javadoc Warnings: Fix warnings coming due to @result tag in > TestCoprocessorWhitelistMasterObserver > -- > > Key: HBASE-22484 > URL: https://issues.apache.org/jira/browse/HBASE-22484 > Project: HBase > Issue Type: Bug > Components: documentation >Affects Versions: 3.0.0-alpha-1 >Reporter: Murtaza Hassan >Assignee: Murtaza Hassan >Priority: Trivial > Labels: beginner > Fix For: 3.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-22218) Shell throws "Unsupported Java version" when tried with Java 11 (run-time)
[
https://issues.apache.org/jira/browse/HBASE-22218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-22218:
--
Fix Version/s: (was: 3.0.0-alpha-1)
(was: 2.3.0)
> Shell throws "Unsupported Java version" when tried with Java 11 (run-time)
> --
>
> Key: HBASE-22218
> URL: https://issues.apache.org/jira/browse/HBASE-22218
> Project: HBase
> Issue Type: Sub-task
>Reporter: Sakthi
>Assignee: Sakthi
>Priority: Major
> Labels: jdk11
>
> Following warning is thrown in the shell.
> {noformat}
> unsupported Java version "11", defaulting to 1.7{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-21078) [amv2] CODE-BUG NPE in RTP doing Unassign
[
https://issues.apache.org/jira/browse/HBASE-21078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-21078:
--
Fix Version/s: (was: 3.0.0-alpha-1)
> [amv2] CODE-BUG NPE in RTP doing Unassign
> -
>
> Key: HBASE-21078
> URL: https://issues.apache.org/jira/browse/HBASE-21078
> Project: HBase
> Issue Type: Bug
> Components: amv2
>Affects Versions: 2.0.1
>Reporter: Michael Stack
>Assignee: Michael Stack
>Priority: Major
> Fix For: 2.2.0, 2.1.1, 2.0.2
>
> Attachments: HBASE-21078.branch-2.0.001.patch,
> HBASE-21078.branch-2.0.002.patch, HBASE-21078.branch-2.0.003.patch,
> HBASE-21078.branch-2.0.004.patch, HBASE-21078.branch-2.0.004.patch,
> HBASE-21078.branch-2.0.004.patch
>
>
> Saw this is a run against tip of branch-2.0. The region had just finished
> being split when the move goes to run.
> {code}
> 2018-08-18 16:55:14,908 INFO [PEWorker-2] procedure2.ProcedureExecutor:
> Finished pid=2028, state=SUCCESS, hasLock=false; SplitTableRegionProcedure
> table=IntegrationTestBigLinkedList, parent=c3f199b5af62ae2ff8f8b6426b21d95d,
> daughterA=31ccbf098ae615ce30f28ec84c956b8f,
> daughterB=1890b4c96736f223f31efef11c817c90 in 9.0090sec
> 2018-08-18 16:55:14,908 INFO [PEWorker-16]
> procedure.MasterProcedureScheduler: pid=2038, ppid=2030,
> state=RUNNABLE:MOVE_REGION_UNASSIGN, hasLock=false; MoveRegionProcedure
> hri=c3f199b5af62ae2ff8f8b6426b21d95d,
> source=ve0540.halxg.cloudera.com,16020,1534632630737,
> destination=ve0540.halxg.cloudera.com,16020,1534632630737 checking lock on
> c3f199b5af62ae2ff8f8b6426b21d95d
> 2018-08-18 16:55:14,958 INFO [PEWorker-16] procedure2.ProcedureExecutor:
> Initialized subprocedures=[{pid=2095, ppid=2038,
> state=RUNNABLE:REGION_TRANSITION_DISPATCH, hasLock=false; UnassignProcedure
> table=IntegrationTestBigLinkedList, region=c3f199b5af62ae2ff8f8b6426b21d95d,
> server=ve0540.halxg.cloudera.com,16020,1534632630737}]
> 2018-08-18 16:55:15,008 INFO [PEWorker-3]
> procedure.MasterProcedureScheduler: pid=2095, ppid=2038,
> state=RUNNABLE:REGION_TRANSITION_DISPATCH, hasLock=false; UnassignProcedure
> table=IntegrationTestBigLinkedList, region=c3f199b5af62ae2ff8f8b6426b21d95d,
> server=ve0540.halxg.cloudera.com,16020,1534632630737 checking lock on
> c3f199b5af62ae2ff8f8b6426b21d95d
> 2018-08-18 16:55:15,085 ERROR [PEWorker-3] procedure2.ProcedureExecutor:
> CODE-BUG: Uncaught runtime exception: pid=2095, ppid=2038,
> state=RUNNABLE:REGION_TRANSITION_DISPATCH, hasLock=true; UnassignProcedure
> table=IntegrationTestBigLinkedList, region=c3f199b5af62ae2ff8f8b6426b21d95d,
> server=ve0540.halxg.cloudera.com,16020,1534632630737
> java.lang.NullPointerException
> at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936)
> at
> org.apache.hadoop.hbase.master.assignment.RegionStates.getOrCreateServer(RegionStates.java:1097)
> at
> org.apache.hadoop.hbase.master.assignment.RegionStates.addRegionToServer(RegionStates.java:1125)
> at
> org.apache.hadoop.hbase.master.assignment.AssignmentManager.markRegionAsClosing(AssignmentManager.java:1477)
> at
> org.apache.hadoop.hbase.master.assignment.UnassignProcedure.updateTransition(UnassignProcedure.java:204)
> at
> org.apache.hadoop.hbase.master.assignment.RegionTransitionProcedure.execute(RegionTransitionProcedure.java:345)
> at
> org.apache.hadoop.hbase.master.assignment.RegionTransitionProcedure.execute(RegionTransitionProcedure.java:97)
> at
> org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:873)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1556)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1344)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$900(ProcedureExecutor.java:76)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:1854)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-21540) when set property "hbase.systemtables.compacting.memstore.type" to "basic" or "eager" will cause an exception
[
https://issues.apache.org/jira/browse/HBASE-21540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-21540.
---
Fix Version/s: 3.0.0-beta-2
(was: 3.0.0-alpha-1)
Resolution: Fixed
> when set property "hbase.systemtables.compacting.memstore.type" to "basic"
> or "eager" will cause an exception
> ---
>
> Key: HBASE-21540
> URL: https://issues.apache.org/jira/browse/HBASE-21540
> Project: HBase
> Issue Type: Bug
> Components: conf
>Affects Versions: 2.0.0
>Reporter: lixiaobao
>Assignee: lixiaobao
>Priority: Major
> Fix For: 3.0.0-beta-2, 2.1.8, 2.2.2, 2.3.0
>
> Attachments: HBASE-21540-and-ut.patch, HBASE-21540-v2.patch,
> HBASE-21540.master.001.patch
>
>
> when set property
> "hbase.systemtables.compacting.memstore.type" value to lowercase (not
> uppercase ) "basic" or "eager" will
> cause an exception "java.lang.IllegalArgumentException: No enum constant
> org.apache.hadoop.hbase.MemoryCompactionPolicy.basic | eager"
> {code:java}
> if (this.getTableName().isSystemTable()) {
>inMemoryCompaction =
> MemoryCompactionPolicy.valueOf(conf.get("hbase.systemtables.compacting.memstore.type",
> "NONE").toUpperCase());
> } else {
> inMemoryCompaction = family.getInMemoryCompaction();
> }{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (HBASE-28844) Align the fixed issues in git and jira
[
https://issues.apache.org/jira/browse/HBASE-28844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885509#comment-17885509
]
Duo Zhang edited comment on HBASE-28844 at 9/28/24 7:25 AM:
I've written a simple script to output the differences.
https://github.com/Apache9/hbase-release-audit/blob/main/audit-git-commit-jira-issue.py
This is the result
Commit to previous release but not in current release:
{noformat}
HBASE-12350
HBASE-17553
HBASE-18187
HBASE-18190
HBASE-18282
HBASE-18431
HBASE-18514
HBASE-18594
HBASE-18595
HBASE-18615
HBASE-18653
HBASE-18817
HBASE-18819
HBASE-18828
HBASE-18833
HBASE-18933
HBASE-19197
HBASE-19315
HBASE-19407
HBASE-19648
HBASE-19670
HBASE-19716
HBASE-19860
HBASE-19888
HBASE-20113
HBASE-20142
HBASE-20233
HBASE-20246
HBASE-20247
HBASE-20415
HBASE-20462
HBASE-20464
{noformat}
Issues in jira but not in git commits:
{noformat}
HBASE-13126 Umbrella for release notes
HBASE-13992 In 2.0.0 but reverted(hbase-spark)
HBASE-14123 In 2.0.0 but reverted(backup&restore)
HBASE-14150 In 2.0.0 but reverted(hbase-spark)
HBASE-14158 In 2.0.0 but reverted(hbase-spark)
HBASE-14159 In 2.0.0 but reverted(hbase-spark)
HBASE-14161 No actual code commit, jenkins change, remove fix version
HBASE-14181 In 2.0.0 but reverted(hbase-spark)
HBASE-14184 In 2.0.0 but reverted(hbase-spark)
HBASE-14340 In 2.0.0 but reverted(hbase-spark)
HBASE-14375 In 2.0.0 but reverted(hbase-spark)
HBASE-14377 In 2.0.0 but reverted(hbase-spark)
HBASE-14406 In 2.0.0 but reverted(hbase-spark)
HBASE-14515 In 2.0.0 but reverted(hbase-spark)
HBASE-14789 In 2.0.0 but reverted(hbase-spark)
HBASE-14849 In 2.0.0 but reverted(hbase-spark)
HBASE-15161 Umbrella for release notes
HBASE-15184 In 2.0.0 but reverted(hbase-spark)
HBASE-15282 In 2.0.0 but reverted(hbase-spark)
HBASE-15291 Should be in 2.0.0, fixed
HBASE-15310 In 2.0.0 but reverted(hbase-spark)
HBASE-15333 In 2.0.0 but reverted(hbase-spark)
HBASE-15336 In 2.0.0 but reverted(hbase-spark)
HBASE-15434 In 2.0.0 but reverted(hbase-spark)
HBASE-15466 In 2.0.0 so do not need to set 3.0.0 fix version, fixed
HBASE-15473 In 2.0.0 but reverted(hbase-spark)
HBASE-15572 In 2.0.0 but reverted(hbase-spark)
HBASE-15597 In 2.0.0 but reverted(hbase-spark)
HBASE-15809 Umbrella issue for release note
HBASE-16638 In 2.0.0 but reverted(hbase-spark)
HBASE-16804 In 2.0.0 but reverted(hbase-spark)
HBASE-16823 In 2.0.0 but reverted(hbase-spark)
HBASE-17546 In 2.0.0 but reverted(hbase-spark)
HBASE-17547 In 2.0.0 but reverted(hbase-spark)
HBASE-17549 In 2.0.0 but reverted(hbase-spark)
HBASE-17574 In 2.0.0 but reverted(hbase-spark)
HBASE-17664 Umbrella issue without release note, remove fix version
HBASE-17852 No actual code commit, remove fix version
HBASE-17909 In 2.0.0 but reverted(hbase-spark)
HBASE-17918 In 2.0.0 but reverted(serial replication)
HBASE-17919 Umbrella issue without release note, remove fix version
HBASE-17933 In 2.0.0 but reverted(hbase-spark)
HBASE-18070 Umbrella issue for release note
HBASE-18095 Umbrella issue without release note but the title provide
something, so leave it as is
HBASE-18175 In 2.0.0 but reverted(hbase-spark)
HBASE-18176 In 2.0.0 but reverted(hbase-spark)
HBASE-18326 No actual code commit, remove fix version
HBASE-18391 No actual code commit, remove fix version
HBASE-18506 No actual code commit, remove fix version
HBASE-18622 No actual code commit, remove fix version
HBASE-18646 In 2.0.0 but reverted(backup&restore)
HBASE-18659 Umbrella issue without release note but the title provide
something, so leave it as is
HBASE-19064 Umbrella issue without release note but the title provide
something, so leave it as is
HBASE-19068 In 2.0.0, change fix version
HBASE-19174 In 2.0.0, change fix version
HBASE-19397 Umbrella issue for release note
HBASE-19506 In 2.0.0, change fix version
HBASE-19547 In 2.0.0, change fix version
HBASE-20006 HBASE-20011 is committed to branch-2 with HBASE-20006 in
commit message, so the tool think HBASE-20006 is already in 2.0.0 but actually
it is not
HBASE-20046 Umbrella issue for release note
HBASE-20068 In 2.0.0, change fix version
HBASE-20112 In 2.0.0, change fix version
HBASE-20152 Umbr
[jira] [Comment Edited] (HBASE-28844) Align the fixed issues in git and jira
[
https://issues.apache.org/jira/browse/HBASE-28844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885509#comment-17885509
]
Duo Zhang edited comment on HBASE-28844 at 9/28/24 7:24 AM:
I've written a simple script to output the differences.
https://github.com/Apache9/hbase-release-audit/blob/main/audit-git-commit-jira-issue.py
This is the result
{noformat}
Commit to previous release but not in current release:
HBASE-12350
HBASE-17553
HBASE-18187
HBASE-18190
HBASE-18282
HBASE-18431
HBASE-18514
HBASE-18594
HBASE-18595
HBASE-18615
HBASE-18653
HBASE-18817
HBASE-18819
HBASE-18828
HBASE-18833
HBASE-18933
HBASE-19197
HBASE-19315
HBASE-19407
HBASE-19648
HBASE-19670
HBASE-19716
HBASE-19860
HBASE-19888
HBASE-20113
HBASE-20142
HBASE-20233
HBASE-20246
HBASE-20247
HBASE-20415
HBASE-20462
HBASE-20464
Issues in jira but not in git commits:
HBASE-13126 Umbrella for release notes
HBASE-13992 In 2.0.0 but reverted(hbase-spark)
HBASE-14123 In 2.0.0 but reverted(backup&restore)
HBASE-14150 In 2.0.0 but reverted(hbase-spark)
HBASE-14158 In 2.0.0 but reverted(hbase-spark)
HBASE-14159 In 2.0.0 but reverted(hbase-spark)
HBASE-14161 No actual code commit, jenkins change, remove fix version
HBASE-14181 In 2.0.0 but reverted(hbase-spark)
HBASE-14184 In 2.0.0 but reverted(hbase-spark)
HBASE-14340 In 2.0.0 but reverted(hbase-spark)
HBASE-14375 In 2.0.0 but reverted(hbase-spark)
HBASE-14377 In 2.0.0 but reverted(hbase-spark)
HBASE-14406 In 2.0.0 but reverted(hbase-spark)
HBASE-14515 In 2.0.0 but reverted(hbase-spark)
HBASE-14789 In 2.0.0 but reverted(hbase-spark)
HBASE-14849 In 2.0.0 but reverted(hbase-spark)
HBASE-15161 Umbrella for release notes
HBASE-15184 In 2.0.0 but reverted(hbase-spark)
HBASE-15282 In 2.0.0 but reverted(hbase-spark)
HBASE-15291 Should be in 2.0.0, fixed
HBASE-15310 In 2.0.0 but reverted(hbase-spark)
HBASE-15333 In 2.0.0 but reverted(hbase-spark)
HBASE-15336 In 2.0.0 but reverted(hbase-spark)
HBASE-15434 In 2.0.0 but reverted(hbase-spark)
HBASE-15466 In 2.0.0 so do not need to set 3.0.0 fix version, fixed
HBASE-15473 In 2.0.0 but reverted(hbase-spark)
HBASE-15572 In 2.0.0 but reverted(hbase-spark)
HBASE-15597 In 2.0.0 but reverted(hbase-spark)
HBASE-15809 Umbrella issue for release note
HBASE-16638 In 2.0.0 but reverted(hbase-spark)
HBASE-16804 In 2.0.0 but reverted(hbase-spark)
HBASE-16823 In 2.0.0 but reverted(hbase-spark)
HBASE-17546 In 2.0.0 but reverted(hbase-spark)
HBASE-17547 In 2.0.0 but reverted(hbase-spark)
HBASE-17549 In 2.0.0 but reverted(hbase-spark)
HBASE-17574 In 2.0.0 but reverted(hbase-spark)
HBASE-17664 Umbrella issue without release note, remove fix version
HBASE-17852 No actual code commit, remove fix version
HBASE-17909 In 2.0.0 but reverted(hbase-spark)
HBASE-17918 In 2.0.0 but reverted(serial replication)
HBASE-17919 Umbrella issue without release note, remove fix version
HBASE-17933 In 2.0.0 but reverted(hbase-spark)
HBASE-18070 Umbrella issue for release note
HBASE-18095 Umbrella issue without release note but the title provide
something, so leave it as is
HBASE-18175 In 2.0.0 but reverted(hbase-spark)
HBASE-18176 In 2.0.0 but reverted(hbase-spark)
HBASE-18326 No actual code commit, remove fix version
HBASE-18391 No actual code commit, remove fix version
HBASE-18506 No actual code commit, remove fix version
HBASE-18622 No actual code commit, remove fix version
HBASE-18646 In 2.0.0 but reverted(backup&restore)
HBASE-18659 Umbrella issue without release note but the title provide
something, so leave it as is
HBASE-19064 Umbrella issue without release note but the title provide
something, so leave it as is
HBASE-19068 In 2.0.0, change fix version
HBASE-19174 In 2.0.0, change fix version
HBASE-19397 Umbrella issue for release note
HBASE-19506 In 2.0.0, change fix version
HBASE-19547 In 2.0.0, change fix version
HBASE-20006 HBASE-20011 is committed to branch-2 with HBASE-20006 in
commit message, so the tool think HBASE-20006 is already in 2.0.0 but actually
it is not
HBASE-20046 Umbrella issue for release note
HBASE-20068 In 2.0.0, change fix version
HBASE-20112 In 2.0.0, change fix version
HBASE-20152 Umbrella issue without rel
[jira] [Updated] (HBASE-21335) Change the default wait time of HBCK2 tool
[ https://issues.apache.org/jira/browse/HBASE-21335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-21335: -- Fix Version/s: (was: 3.0.0-alpha-1) (was: 2.2.0) (was: 2.1.1) (was: 2.0.3) > Change the default wait time of HBCK2 tool > -- > > Key: HBASE-21335 > URL: https://issues.apache.org/jira/browse/HBASE-21335 > Project: HBase > Issue Type: Bug >Reporter: Jingyun Tian >Assignee: Jingyun Tian >Priority: Critical > Fix For: hbase-operator-tools-1.0.0 > > Attachments: > 0001-HBASE-21335-Change-the-default-wait-time-of-HBCK2-to.patch, > 0002-HBASE-21335-Change-the-default-wait-time-of-HBCK2-to.patch > > > Currently default wait time is 0 and I add a condition check before that wait > time should more than 0. Thus the default wait time should be set to a number > that more than 0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (HBASE-21540) when set property "hbase.systemtables.compacting.memstore.type" to "basic" or "eager" will cause an exception
[
https://issues.apache.org/jira/browse/HBASE-21540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang reopened HBASE-21540:
---
Missed in master and branch-3.
> when set property "hbase.systemtables.compacting.memstore.type" to "basic"
> or "eager" will cause an exception
> ---
>
> Key: HBASE-21540
> URL: https://issues.apache.org/jira/browse/HBASE-21540
> Project: HBase
> Issue Type: Bug
> Components: conf
>Affects Versions: 2.0.0
>Reporter: lixiaobao
>Assignee: lixiaobao
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.2, 2.1.8
>
> Attachments: HBASE-21540-and-ut.patch, HBASE-21540-v2.patch,
> HBASE-21540.master.001.patch
>
>
> when set property
> "hbase.systemtables.compacting.memstore.type" value to lowercase (not
> uppercase ) "basic" or "eager" will
> cause an exception "java.lang.IllegalArgumentException: No enum constant
> org.apache.hadoop.hbase.MemoryCompactionPolicy.basic | eager"
> {code:java}
> if (this.getTableName().isSystemTable()) {
>inMemoryCompaction =
> MemoryCompactionPolicy.valueOf(conf.get("hbase.systemtables.compacting.memstore.type",
> "NONE").toUpperCase());
> } else {
> inMemoryCompaction = family.getInMemoryCompaction();
> }{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-20439) Clean up incorrect use of commons-logging in hbase-server
[
https://issues.apache.org/jira/browse/HBASE-20439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-20439:
--
Fix Version/s: (was: 3.0.0-alpha-1)
> Clean up incorrect use of commons-logging in hbase-server
> -
>
> Key: HBASE-20439
> URL: https://issues.apache.org/jira/browse/HBASE-20439
> Project: HBase
> Issue Type: Bug
> Components: dependencies, logging
>Affects Versions: 2.0.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-20439.0.patch, HBASE-20439.1.patch
>
>
> We moved to slf4j in HBASE-10092, but looking at our source tree we've had
> some regression back to commons-logging:
> {code}
> $ git grep -E "org.apache.commons.logging.Log(Factory|;)"
> hbase-server/src/main/java/org/apache/hadoop/hbase/master/zksyncer/ClientZKSyncer.java:import
> org.apache.commons.logging.Log;
> hbase-server/src/main/java/org/apache/hadoop/hbase/master/zksyncer/ClientZKSyncer.java:import
> org.apache.commons.logging.LogFactory;
> hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/FileArchiverNotifierImpl.java:import
> org.apache.commons.logging.Log;
> hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/FileArchiverNotifierImpl.java:import
> org.apache.commons.logging.LogFactory;
> hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/RegionSizeReportingChore.java:import
> org.apache.commons.logging.Log;
> hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/RegionSizeReportingChore.java:import
> org.apache.commons.logging.LogFactory;
> hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/RegionSizeStoreImpl.java:import
> org.apache.commons.logging.Log;
> hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/RegionSizeStoreImpl.java:import
> org.apache.commons.logging.LogFactory;
> hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/throttle/StoreHotnessProtector.java:import
> org.apache.commons.logging.Log;
> hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/throttle/StoreHotnessProtector.java:import
> org.apache.commons.logging.LogFactory;
> hbase-server/src/test/java/org/apache/hadoop/hbase/TestClusterPortAssignment.java:import
> org.apache.commons.logging.Log;
> hbase-server/src/test/java/org/apache/hadoop/hbase/TestClusterPortAssignment.java:import
> org.apache.commons.logging.LogFactory;
> hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFlushFromClient.java:import
> org.apache.commons.logging.Log;
> hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFlushFromClient.java:import
> org.apache.commons.logging.LogFactory;
> hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestSeparateClientZKCluster.java:import
> org.apache.commons.logging.Log;
> hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestSeparateClientZKCluster.java:import
> org.apache.commons.logging.LogFactory;
> hbase-server/src/test/java/org/apache/hadoop/hbase/procedure/TestFailedProcCleanup.java:import
> org.apache.commons.logging.Log;
> hbase-server/src/test/java/org/apache/hadoop/hbase/procedure/TestFailedProcCleanup.java:import
> org.apache.commons.logging.LogFactory;
> hbase-server/src/test/java/org/apache/hadoop/hbase/wal/TestDisabledWAL.java:import
> org.apache.commons.logging.Log;
> hbase-server/src/test/java/org/apache/hadoop/hbase/wal/TestDisabledWAL.java:import
> org.apache.commons.logging.LogFactory;
> {code}
> replace with slf4j
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-20389) Move website building flags into a profile
[
https://issues.apache.org/jira/browse/HBASE-20389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-20389:
--
Fix Version/s: 2.0.0
(was: 3.0.0-alpha-1)
(was: 2.1.0)
(was: 2.0.1)
> Move website building flags into a profile
> --
>
> Key: HBASE-20389
> URL: https://issues.apache.org/jira/browse/HBASE-20389
> Project: HBase
> Issue Type: Improvement
> Components: build, website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-20389.0.patch, HBASE-20389.1.patch
>
>
> we have some "magic" in our website building right now. The script that's
> used bout our automated website build + publish mechanism manually sets a
> bunch of stuff on the maven command line.
> It'd be better to reflect those settings in a maven profile, so that folks
> are less likely to be surprised e.g. when trying to debug a failure in the
> {{site}} goal happens.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-21430) [hbase-connectors] Move hbase-spark* modules to hbase-connectors repo
[ https://issues.apache.org/jira/browse/HBASE-21430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-21430: -- Fix Version/s: hbase-operator-tools-1.0.0 > [hbase-connectors] Move hbase-spark* modules to hbase-connectors repo > - > > Key: HBASE-21430 > URL: https://issues.apache.org/jira/browse/HBASE-21430 > Project: HBase > Issue Type: Bug > Components: hbase-connectors, spark >Reporter: Michael Stack >Assignee: Michael Stack >Priority: Major > Fix For: 3.0.0-alpha-1, 2.2.0, hbase-operator-tools-1.0.0 > > > Exploring moving the spark modules out of core hbase and into > hbase-connectors. Perhaps spark is deserving of its own repo (I think > [~busbey] was on about this) but meantime, experimenting w/ having it out in > hbase-connectors. > Here is thread on spark integration > https://lists.apache.org/thread.html/fd74ef9b9da77abf794664f06ea19c839fb3d543647fb29115081683@%3Cdev.hbase.apache.org%3E -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-21192) Add HOW-TO repair damaged AMv2.
[ https://issues.apache.org/jira/browse/HBASE-21192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-21192: -- Fix Version/s: hbase-operator-tools-1.0.0 (was: 3.0.0-alpha-1) (was: 2.2.0) (was: 2.1.1) (was: 2.0.3) > Add HOW-TO repair damaged AMv2. > --- > > Key: HBASE-21192 > URL: https://issues.apache.org/jira/browse/HBASE-21192 > Project: HBase > Issue Type: Sub-task > Components: amv2 >Reporter: Michael Stack >Assignee: Michael Stack >Priority: Major > Fix For: hbase-operator-tools-1.0.0 > > > Need a page or two on how to do various fixups. Will include doc on how to > identify particular circumstance, how to run a repair, as well as caveats > (e.g. if no log recovery, then region may be missing edits). > Add pointer to log messages, especially those that explicitly ask for > operator intervention; e.g. Master#inMeta. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-20934) Create an hbase-connectors repository; commit new kafka connect here
[ https://issues.apache.org/jira/browse/HBASE-20934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-20934: -- Fix Version/s: hbase-operator-tools-1.0.0 > Create an hbase-connectors repository; commit new kafka connect here > > > Key: HBASE-20934 > URL: https://issues.apache.org/jira/browse/HBASE-20934 > Project: HBase > Issue Type: Bug > Components: kafka, mapreduce, REST, spark, Thrift >Affects Versions: 2.1.0 >Reporter: Michael Stack >Assignee: Michael Stack >Priority: Critical > Fix For: hbase-operator-tools-1.0.0 > > > Create a new repository at hbase.apache.org and commit the new kafka proxy > here (HBASE-15320). Make sure it plays nicely with hbase core making use of > public-apis only (It does as best as I can see... but saying this anyways). > Once the kafka proxy is working, as subissue, move REST and thrift over... > SPARK too. > This might be better done for an hbase3 target. I filed it against hbase2.2 > for now. > See discussion up on dev list, "[DISCUSS] Kafka Connection, HBASE-15320", > https://s.apache.org/RQcC. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-20338) WALProcedureStore#recoverLease() should have fixed sleeps for retrying rollWriter()
[
https://issues.apache.org/jira/browse/HBASE-20338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-20338:
--
Fix Version/s: 2.0.0
(was: 3.0.0-alpha-1)
(was: 2.1.0)
(was: 2.0.1)
> WALProcedureStore#recoverLease() should have fixed sleeps for retrying
> rollWriter()
> ---
>
> Key: HBASE-20338
> URL: https://issues.apache.org/jira/browse/HBASE-20338
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.0.0-beta-2
>Reporter: Umesh Agashe
>Assignee: Wei-Chiu Chuang
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-20338.master.001.patch,
> HBASE-20338.master.002.patch, HBASE-20338.master.003.patch,
> HBASE-20338.master.004.patch, HBASE-20338.master.005.patch
>
>
> In our internal testing we observed that logs are getting flooded due to
> continuous loop in WALProcedureStore#recoverLease():
> {code}
> while (isRunning()) {
> // Get Log-MaxID and recover lease on old logs
> try {
> flushLogId = initOldLogs(oldLogs);
> } catch (FileNotFoundException e) {
> LOG.warn("Someone else is active and deleted logs. retrying.", e);
> oldLogs = getLogFiles();
> continue;
> }
> // Create new state-log
> if (!rollWriter(flushLogId + 1)) {
> // someone else has already created this log
> LOG.debug("Someone else has already created log " + flushLogId);
> continue;
> }
> {code}
> rollWriter() fails to create a new file. Error messages in HDFS namenode logs
> around same time:
> {code}
> INFO org.apache.hadoop.ipc.Server: IPC Server handler 3 on 8020, call
> org.apache.hadoop.hdfs.protocol.ClientProtocol.create from
> 172.31.121.196:38508 Call#3141 Retry#0
> java.io.IOException: Exeption while contacting value generator
> at
> org.apache.hadoop.crypto.key.kms.ValueQueue.getAtMost(ValueQueue.java:389)
> at
> org.apache.hadoop.crypto.key.kms.ValueQueue.getNext(ValueQueue.java:291)
> at
> org.apache.hadoop.crypto.key.kms.KMSClientProvider.generateEncryptedKey(KMSClientProvider.java:724)
> at
> org.apache.hadoop.crypto.key.KeyProviderCryptoExtension.generateEncryptedKey(KeyProviderCryptoExtension.java:511)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem$2.run(FSNamesystem.java:2680)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem$2.run(FSNamesystem.java:2676)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1920)
> at
> org.apache.hadoop.security.SecurityUtil.doAsUser(SecurityUtil.java:477)
> at
> org.apache.hadoop.security.SecurityUtil.doAsLoginUser(SecurityUtil.java:458)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.generateEncryptedDataEncryptionKey(FSNamesystem.java:2675)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInt(FSNamesystem.java:2815)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFile(FSNamesystem.java:2712)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.create(NameNodeRpcServer.java:604)
> at
> org.apache.hadoop.hdfs.server.namenode.AuthorizationProviderProxyClientProtocol.create(AuthorizationProviderProxyClientProtocol.java:115)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.create(ClientNamenodeProtocolServerSideTranslatorPB.java:412)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:617)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1073)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2226)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1920)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2220)
> Caused by: java.net.ConnectException: Connection refused (Connection refused)
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> at
> java.net.AbstractPlainSocketI
[jira] [Updated] (HBASE-20440) Clean up incorrect use of commons-lang 2.y
[
https://issues.apache.org/jira/browse/HBASE-20440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-20440:
--
Fix Version/s: (was: 3.0.0-alpha-1)
> Clean up incorrect use of commons-lang 2.y
> --
>
> Key: HBASE-20440
> URL: https://issues.apache.org/jira/browse/HBASE-20440
> Project: HBase
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 2.0.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-20440.0.patch
>
>
> We updated to commons-lang 3 in HBASE-18674 but we've regressed:
> {code}
> $ git grep org.apache.commons.lang\\.
> hbase-common/src/main/java/org/apache/hadoop/hbase/net/Address.java:import
> org.apache.commons.lang.StringUtils;
> hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/FileArchiverNotifierFactoryImpl.java:import
> org.apache.commons.lang.builder.HashCodeBuilder;
> hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/FileArchiverNotifierImpl.java:import
> org.apache.commons.lang.builder.HashCodeBuilder;
> hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHdfsSnapshotHRegion.java:import
> org.apache.commons.lang.StringUtils;
> hbase-server/src/test/java/org/apache/hadoop/hbase/util/compaction/TestMajorCompactionRequest.java:import
> org.apache.commons.lang.RandomStringUtils;
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-21169) Initiate hbck2 tool in hbase-operator-tools repo
[ https://issues.apache.org/jira/browse/HBASE-21169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-21169: -- Fix Version/s: hbase-operator-tools-1.0.0 (was: 3.0.0-alpha-1) (was: 2.2.0) (was: 2.1.1) > Initiate hbck2 tool in hbase-operator-tools repo > > > Key: HBASE-21169 > URL: https://issues.apache.org/jira/browse/HBASE-21169 > Project: HBase > Issue Type: Sub-task > Components: hbck2 >Affects Versions: 2.1.0 >Reporter: Umesh Agashe >Assignee: Michael Stack >Priority: Major > Fix For: hbase-operator-tools-1.0.0 > > Attachments: hbase-21169.master.001.patch > > > Create hbck2 tool in hbase-operator-tools > (https://github.com/apache/hbase-operator-tools.git) repo. This is not > intended to be complete tool but initial changes with usage, ability to > connect to server, logging, and using newly added HbckService etc. Code > changes to address specific use cases can be added later and tool will evolve. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-20376) RowCounter and CellCounter documentations are incorrect
[ https://issues.apache.org/jira/browse/HBASE-20376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-20376: -- Fix Version/s: (was: 3.0.0-alpha-1) > RowCounter and CellCounter documentations are incorrect > --- > > Key: HBASE-20376 > URL: https://issues.apache.org/jira/browse/HBASE-20376 > Project: HBase > Issue Type: Bug > Components: documentation, mapreduce >Affects Versions: 2.0.0 >Reporter: Peter Somogyi >Assignee: Peter Somogyi >Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-20376.master.001.patch, > HBASE-20376.master.002.patch, HBASE-20376.master.003.patch > > > The documentation of RowCounter and CellCounter in refguide needs some > improvement. Help messages also need some tuning. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-21113) Apply the branch-2 version of HBASE-21095, The timeout retry logic for several procedures are broken after master restarts
[ https://issues.apache.org/jira/browse/HBASE-21113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-21113: -- Fix Version/s: (was: 3.0.0-alpha-1) > Apply the branch-2 version of HBASE-21095, The timeout retry logic for > several procedures are broken after master restarts > -- > > Key: HBASE-21113 > URL: https://issues.apache.org/jira/browse/HBASE-21113 > Project: HBase > Issue Type: Bug > Components: amv2 >Reporter: Michael Stack >Assignee: Allan Yang >Priority: Major > Fix For: 2.2.0, 2.1.1, 2.0.2 > > > This issue is for applying branch-2 version of the HBASE-21095 patch. The > patch applied here is the HBASE-21095.branch-2.0.001.patch patch from > HBASE-21095 written by [~allan163]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-20441) Use checkstyle to ban imports from commons-lang 2
[
https://issues.apache.org/jira/browse/HBASE-20441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-20441:
--
Fix Version/s: (was: 3.0.0-alpha-1)
> Use checkstyle to ban imports from commons-lang 2
> -
>
> Key: HBASE-20441
> URL: https://issues.apache.org/jira/browse/HBASE-20441
> Project: HBase
> Issue Type: Task
> Components: dependencies, test
>Affects Versions: 2.0.0
>Reporter: Sean Busbey
>Assignee: Balazs Meszaros
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-20441.master.001.patch
>
>
> We updated to commons-lang 3 in HBASE-18674 but we've regressed:
> {code}
> $ git grep org.apache.commons.lang\\.
> hbase-common/src/main/java/org/apache/hadoop/hbase/net/Address.java:import
> org.apache.commons.lang.StringUtils;
> hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/FileArchiverNotifierFactoryImpl.java:import
> org.apache.commons.lang.builder.HashCodeBuilder;
> hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/FileArchiverNotifierImpl.java:import
> org.apache.commons.lang.builder.HashCodeBuilder;
> hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHdfsSnapshotHRegion.java:import
> org.apache.commons.lang.StringUtils;
> hbase-server/src/test/java/org/apache/hadoop/hbase/util/compaction/TestMajorCompactionRequest.java:import
> org.apache.commons.lang.RandomStringUtils;
> {code}
> we should add the same kind of check as we do for e.g. hadoop annotations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-20934) Create an hbase-connectors repository; commit new kafka connect here
[ https://issues.apache.org/jira/browse/HBASE-20934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-20934: -- Fix Version/s: (was: 3.0.0-alpha-1) > Create an hbase-connectors repository; commit new kafka connect here > > > Key: HBASE-20934 > URL: https://issues.apache.org/jira/browse/HBASE-20934 > Project: HBase > Issue Type: Bug > Components: kafka, mapreduce, REST, spark, Thrift >Affects Versions: 2.1.0 >Reporter: Michael Stack >Assignee: Michael Stack >Priority: Critical > > Create a new repository at hbase.apache.org and commit the new kafka proxy > here (HBASE-15320). Make sure it plays nicely with hbase core making use of > public-apis only (It does as best as I can see... but saying this anyways). > Once the kafka proxy is working, as subissue, move REST and thrift over... > SPARK too. > This might be better done for an hbase3 target. I filed it against hbase2.2 > for now. > See discussion up on dev list, "[DISCUSS] Kafka Connection, HBASE-15320", > https://s.apache.org/RQcC. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-20442) clean up incorrect use of commons-collections 3
[
https://issues.apache.org/jira/browse/HBASE-20442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-20442:
--
Fix Version/s: (was: 3.0.0-alpha-1)
> clean up incorrect use of commons-collections 3
> ---
>
> Key: HBASE-20442
> URL: https://issues.apache.org/jira/browse/HBASE-20442
> Project: HBase
> Issue Type: Bug
> Components: dependencies, thirdparty
>Affects Versions: 2.0.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-20442.0.patch
>
>
> we upgraded to commons-collections 4 in HBASE-18704 and then to an
> internal-only hbase-thirdparty version in HBASE-20223, but we've regressed:
> {code}
> $ git grep "import org.apache.commons.collections"
> hbase-backup/src/main/java/org/apache/hadoop/hbase/backup/master/BackupLogCleaner.java:import
> org.apache.commons.collections.MapUtils;
> hbase-client/src/main/java/org/apache/hadoop/hbase/client/RowMutations.java:import
> org.apache.commons.collections.CollectionUtils;
> hbase-common/src/main/java/org/apache/hadoop/hbase/util/Bytes.java:import
> org.apache.commons.collections.CollectionUtils;
> hbase-replication/src/main/java/org/apache/hadoop/hbase/replication/ZKReplicationQueueStorage.java:import
> org.apache.commons.collections.CollectionUtils;
> hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java:import
> org.apache.commons.collections.CollectionUtils;
> hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java:import
> org.apache.commons.collections.CollectionUtils;
> hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreScanner.java:import
> org.apache.commons.collections.CollectionUtils;
> hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/FSWALEntry.java:import
> org.apache.commons.collections.CollectionUtils;
> hbase-server/src/main/java/org/apache/hadoop/hbase/wal/WALSplitter.java:import
> org.apache.commons.collections.CollectionUtils;
> hbase-server/src/main/java/org/apache/hadoop/hbase/wal/WALSplitter.java:import
> org.apache.commons.collections.MapUtils;
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-20443) Use checkstyle to ban imports from commons-collections 3
[
https://issues.apache.org/jira/browse/HBASE-20443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-20443:
--
Fix Version/s: (was: 3.0.0-alpha-1)
> Use checkstyle to ban imports from commons-collections 3
>
>
> Key: HBASE-20443
> URL: https://issues.apache.org/jira/browse/HBASE-20443
> Project: HBase
> Issue Type: Task
> Components: dependencies, test
>Reporter: Sean Busbey
>Assignee: Balazs Meszaros
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-20443.master.001.patch,
> HBASE-20443.master.002.patch
>
>
> we upgraded to commons-collections 4 in HBASE-18704 and then to an
> internal-only hbase-thirdparty version in HBASE-20223, but we've regressed:
> {code}
> $ git grep "import org.apache.commons.collections"
> hbase-backup/src/main/java/org/apache/hadoop/hbase/backup/master/BackupLogCleaner.java:import
> org.apache.commons.collections.MapUtils;
> hbase-client/src/main/java/org/apache/hadoop/hbase/client/RowMutations.java:import
> org.apache.commons.collections.CollectionUtils;
> hbase-common/src/main/java/org/apache/hadoop/hbase/util/Bytes.java:import
> org.apache.commons.collections.CollectionUtils;
> hbase-replication/src/main/java/org/apache/hadoop/hbase/replication/ZKReplicationQueueStorage.java:import
> org.apache.commons.collections.CollectionUtils;
> hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java:import
> org.apache.commons.collections.CollectionUtils;
> hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java:import
> org.apache.commons.collections.CollectionUtils;
> hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreScanner.java:import
> org.apache.commons.collections.CollectionUtils;
> hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/FSWALEntry.java:import
> org.apache.commons.collections.CollectionUtils;
> hbase-server/src/main/java/org/apache/hadoop/hbase/wal/WALSplitter.java:import
> org.apache.commons.collections.CollectionUtils;
> hbase-server/src/main/java/org/apache/hadoop/hbase/wal/WALSplitter.java:import
> org.apache.commons.collections.MapUtils;
> {code}
> we should add the same kind of check as we do for e.g. hadoop annotations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-20410) upgrade protoc compiler to 3.5.1-1
[ https://issues.apache.org/jira/browse/HBASE-20410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-20410: -- Fix Version/s: (was: 3.0.0-alpha-1) > upgrade protoc compiler to 3.5.1-1 > -- > > Key: HBASE-20410 > URL: https://issues.apache.org/jira/browse/HBASE-20410 > Project: HBase > Issue Type: Bug > Components: build, dependencies, Protobufs >Reporter: Mike Drob >Assignee: Mike Drob >Priority: Critical > Fix For: 2.0.0 > > Attachments: HBASE-20410.patch > > > See HBASE-20356 > After doing the cleanup there, I was informed that there's a 3.5.1-1 version > of the compiler binaries that work on rhel6, so let's just go to that. Wish I > knew about it beforehand. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-20404) Ugly cleanerchore complaint that dir is not empty
[
https://issues.apache.org/jira/browse/HBASE-20404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-20404:
--
Fix Version/s: 2.0.0
(was: 3.0.0-alpha-1)
(was: 2.1.0)
(was: 2.0.1)
> Ugly cleanerchore complaint that dir is not empty
> -
>
> Key: HBASE-20404
> URL: https://issues.apache.org/jira/browse/HBASE-20404
> Project: HBase
> Issue Type: Bug
> Components: master
>Affects Versions: 1.4.4, 2.0.0
>Reporter: Michael Stack
>Assignee: Sean Busbey
>Priority: Major
> Fix For: 1.3.3, 1.4.4, 2.0.0
>
> Attachments: HBASE-20404.0.patch, HBASE-20404.1.patch,
> HBASE-20404.2.patch
>
>
> I see these big dirty exceptions in my master log during a long-run Lets
> clean them up (Are they exceptions I as an operator can actually do something
> about? Are they 'problems'? Should they be LOG.warn?)
> {code}
> 2018-04-12 16:02:09,911 WARN [ForkJoinPool-1-worker-15]
> cleaner.CleanerChore: Could not delete dir under
> hdfs://ve0524.halxg.cloudera.com:8020/hbase/archive/data/default/IntegrationTestBigLinkedList/1e24549061df3adc4858fbcaf1929553/meta;
> {}
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.fs.PathIsNotEmptyDirectoryException):
>
> `/hbase/archive/data/default/IntegrationTestBigLinkedList/1e24549061df3adc4858fbcaf1929553/meta
> is non empty': Directory is not empty
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirDeleteOp.delete(FSDirDeleteOp.java:115)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.delete(FSNamesystem.java:2848)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.delete(NameNodeRpcServer.java:1048)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.delete(ClientNamenodeProtocolServerSideTranslatorPB.java:641)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:447)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:989)
> at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:847)
> at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:790)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1836)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2486)
> at org.apache.hadoop.ipc.Client.getRpcResponse(Client.java:1489)
> at org.apache.hadoop.ipc.Client.call(Client.java:1435)
> at org.apache.hadoop.ipc.Client.call(Client.java:1345)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:227)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:116)
> at com.sun.proxy.$Proxy26.delete(Unknown Source)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.delete(ClientNamenodeProtocolTranslatorPB.java:568)
> at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:409)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeMethod(RetryInvocationHandler.java:163)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invoke(RetryInvocationHandler.java:155)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeOnce(RetryInvocationHandler.java:95)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:346)
> at com.sun.proxy.$Proxy27.delete(Unknown Source)
> at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown Source)
> ...
> {code}
> Looks like log format is off too...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-20438) Add an HBase antipattern check for reintroducing commons-logging
[
https://issues.apache.org/jira/browse/HBASE-20438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-20438:
--
Fix Version/s: (was: 3.0.0-alpha-1)
> Add an HBase antipattern check for reintroducing commons-logging
>
>
> Key: HBASE-20438
> URL: https://issues.apache.org/jira/browse/HBASE-20438
> Project: HBase
> Issue Type: Improvement
> Components: dependencies, test
>Affects Versions: 3.0.0-alpha-1, 2.1.0, 2.0.0
>Reporter: Sean Busbey
>Assignee: Nihal Jain
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: HBASE-20438.master.001.patch
>
>
> We moved to slf4j in HBASE-10092, but looking at our source tree we've had
> some regression back to commons-logging:
> {code}
> $ git grep -E "org.apache.commons.logging.Log(Factory|;)"
> hbase-server/src/main/java/org/apache/hadoop/hbase/master/zksyncer/ClientZKSyncer.java:import
> org.apache.commons.logging.Log;
> hbase-server/src/main/java/org/apache/hadoop/hbase/master/zksyncer/ClientZKSyncer.java:import
> org.apache.commons.logging.LogFactory;
> hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/FileArchiverNotifierImpl.java:import
> org.apache.commons.logging.Log;
> hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/FileArchiverNotifierImpl.java:import
> org.apache.commons.logging.LogFactory;
> hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/RegionSizeReportingChore.java:import
> org.apache.commons.logging.Log;
> hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/RegionSizeReportingChore.java:import
> org.apache.commons.logging.LogFactory;
> hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/RegionSizeStoreImpl.java:import
> org.apache.commons.logging.Log;
> hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/RegionSizeStoreImpl.java:import
> org.apache.commons.logging.LogFactory;
> hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/throttle/StoreHotnessProtector.java:import
> org.apache.commons.logging.Log;
> hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/throttle/StoreHotnessProtector.java:import
> org.apache.commons.logging.LogFactory;
> hbase-server/src/test/java/org/apache/hadoop/hbase/TestClusterPortAssignment.java:import
> org.apache.commons.logging.Log;
> hbase-server/src/test/java/org/apache/hadoop/hbase/TestClusterPortAssignment.java:import
> org.apache.commons.logging.LogFactory;
> hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFlushFromClient.java:import
> org.apache.commons.logging.Log;
> hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFlushFromClient.java:import
> org.apache.commons.logging.LogFactory;
> hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestSeparateClientZKCluster.java:import
> org.apache.commons.logging.Log;
> hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestSeparateClientZKCluster.java:import
> org.apache.commons.logging.LogFactory;
> hbase-server/src/test/java/org/apache/hadoop/hbase/procedure/TestFailedProcCleanup.java:import
> org.apache.commons.logging.Log;
> hbase-server/src/test/java/org/apache/hadoop/hbase/procedure/TestFailedProcCleanup.java:import
> org.apache.commons.logging.LogFactory;
> hbase-server/src/test/java/org/apache/hadoop/hbase/wal/TestDisabledWAL.java:import
> org.apache.commons.logging.Log;
> hbase-server/src/test/java/org/apache/hadoop/hbase/wal/TestDisabledWAL.java:import
> org.apache.commons.logging.LogFactory;
> {code}
> We should do the same kind of check that we do to avoid e.g. the Hadoop
> annotations
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-20409) Set hbase.client.meta.operation.timeout in TestClientOperationTimeout
[ https://issues.apache.org/jira/browse/HBASE-20409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-20409: -- Fix Version/s: (was: 3.0.0-alpha-1) > Set hbase.client.meta.operation.timeout in TestClientOperationTimeout > - > > Key: HBASE-20409 > URL: https://issues.apache.org/jira/browse/HBASE-20409 > Project: HBase > Issue Type: Improvement > Components: test >Affects Versions: 3.0.0-alpha-1, 2.1.0, 2.0.0 >Reporter: Peter Somogyi >Assignee: Peter Somogyi >Priority: Trivial > Fix For: 2.0.0 > > Attachments: HBASE-20409.master.001.patch > > > In TestClientOperationTimeout the hbase.client.meta.operation.timeout > property is not, so default value is used which is 120ms. The test > finishes earlier if we set the timeout to match with > hbase.client.meta.operation.timeout. > Since the first call will go to META table where the default timeout is used. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-20360) Further optimization for serial replication
[ https://issues.apache.org/jira/browse/HBASE-20360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-20360: -- Fix Version/s: (was: 3.0.0-alpha-1) (was: 2.1.0) > Further optimization for serial replication > --- > > Key: HBASE-20360 > URL: https://issues.apache.org/jira/browse/HBASE-20360 > Project: HBase > Issue Type: Umbrella > Components: Replication >Reporter: Duo Zhang >Priority: Major > > Open a issue to track the remaining works for serial replication. The main > thing is about the cleanup for replication barrier and last pushed sequence > ids. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-20364) nightly job gives old results or no results for stages that timeout on SCM
[
https://issues.apache.org/jira/browse/HBASE-20364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-20364:
--
Fix Version/s: 2.0.0
(was: 3.0.0-alpha-1)
(was: 2.1.0)
(was: 2.0.1)
> nightly job gives old results or no results for stages that timeout on SCM
> --
>
> Key: HBASE-20364
> URL: https://issues.apache.org/jira/browse/HBASE-20364
> Project: HBase
> Issue Type: Bug
> Components: test
>Affects Versions: 3.0.0-alpha-1
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Critical
> Fix For: 1.3.3, 1.4.4, 2.0.0, 1.2.7
>
> Attachments: HBASE-20364.0.patch
>
>
> seen in the branch-2.0 nightly report for HBASE-18828:
>
> {quote}
> Results for branch branch-2.0
> [build #143 on
> builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/143/]:
> (x) *\{color:red}-1 overall\{color}*
>
> details (if available):
> (/) \{color:green}+1 general checks\{color}
> -- For more information [see general
> report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/140//General_Nightly_Build_Report/]
>
> (/) \{color:green}+1 jdk8 hadoop2 checks\{color}
> -- For more information [see jdk8 (hadoop2)
> report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/143//JDK8_Nightly_Build_Report_(Hadoop2)/]
> (/) \{color:green}+1 jdk8 hadoop3 checks\{color}
> -- For more information [see jdk8 (hadoop3)
> report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/143//JDK8_Nightly_Build_Report_(Hadoop3)/]
>
> {quote}
>
> -1 for the overall build was correct. build #143 failed both the general
> check and the source tarball check.
>
> but in the posted comment, we get a false "passing" that links to the general
> result from build #140. and we get no result for the source tarball at all.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-20379) shadedjars yetus plugin should add a footer link
[ https://issues.apache.org/jira/browse/HBASE-20379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-20379: -- Fix Version/s: 2.0.0 (was: 3.0.0-alpha-1) (was: 2.1.0) (was: 2.0.1) > shadedjars yetus plugin should add a footer link > > > Key: HBASE-20379 > URL: https://issues.apache.org/jira/browse/HBASE-20379 > Project: HBase > Issue Type: Improvement > Components: test >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Major > Fix For: 1.3.3, 1.4.4, 2.0.0, 1.2.7 > > Attachments: HBASE-20379.0.patch > > > investigating the failure on HBASE-20219, it would be nice if we posted a > footer link to what failed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-20335) nightly jobs no longer contain machine information
[ https://issues.apache.org/jira/browse/HBASE-20335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-20335: -- Fix Version/s: 2.0.0 (was: 3.0.0-alpha-1) (was: 2.1.0) (was: 2.0.1) > nightly jobs no longer contain machine information > -- > > Key: HBASE-20335 > URL: https://issues.apache.org/jira/browse/HBASE-20335 > Project: HBase > Issue Type: Bug > Components: test >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Critical > Fix For: 1.3.3, 1.4.4, 2.0.0, 1.2.7 > > Attachments: HBASE-20335.0.patch, HBASE-20335.1.patch > > > something is up with nightly jobs. they no longer have the machine > information from HBASE-19228. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-20293) get_splits returns duplicate split points when region replication is on
[
https://issues.apache.org/jira/browse/HBASE-20293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-20293:
--
Fix Version/s: (was: 3.0.0-alpha-1)
> get_splits returns duplicate split points when region replication is on
> ---
>
> Key: HBASE-20293
> URL: https://issues.apache.org/jira/browse/HBASE-20293
> Project: HBase
> Issue Type: Bug
> Components: shell
>Reporter: Toshihiro Suzuki
>Assignee: Toshihiro Suzuki
>Priority: Minor
> Fix For: 1.4.4, 2.0.0
>
> Attachments: HBASE-20293.branch-1.001.patch,
> HBASE-20293.branch-1.002.patch, HBASE-20293.branch-1.003.patch,
> HBASE-20293.branch-1.004.patch, HBASE-20293.branch-1.005.patch,
> HBASE-20293.master.001.patch, HBASE-20293.master.002.patch,
> HBASE-20293.master.003.patch, HBASE-20293.master.004.patch
>
>
> When region replication is on, get_splits returns duplicate split points like
> the following:
> {code}
> hbase(main):001:0> create "test", "cf", {REGION_REPLICATION => 3}, SPLITS =>
> ["10"]
> Created table test
> Took 1.0975 seconds
> hbase(main):002:0> get_splits "test"
> Total number of splits = 4
> 10
> 10
> 10
> Took 0.0941 seconds
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-20287) After cluster startup list_regions command fails on disabled table
[
https://issues.apache.org/jira/browse/HBASE-20287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-20287:
--
Fix Version/s: (was: 3.0.0-alpha-1)
> After cluster startup list_regions command fails on disabled table
> --
>
> Key: HBASE-20287
> URL: https://issues.apache.org/jira/browse/HBASE-20287
> Project: HBase
> Issue Type: Sub-task
> Components: shell
>Affects Versions: 2.0.0
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-20287.master.001.patch
>
>
> After cluster startup list_regions throw “ERROR: undefined method `toString'
> for nil:NilClass”. If you enable the table and disable it you don't see the
> error again, only after cluster startup.
> {noformat}
> After startup list_regions throw “ERROR: undefined method `toString' for
> nil:NilClass”.
> hbase(main):009:0> list_regions 'ltt'
> ERROR: undefined method `toString' for nil:NilClass
> List all regions for a particular table as an array and also filter
> them by server name (optional) as prefix
> and maximum locality (optional). By default, it will return all the
> regions for the table with any locality.
> The command displays server name, region name, start key, end key,
> size of the region in MB, number of requests
> and the locality. The information can be projected out via an array as
> third parameter. By default all these information
> is displayed. Possible array values are SERVER_NAME, REGION_NAME,
> START_KEY, END_KEY, SIZE, REQ and LOCALITY. Values
> are not case sensitive. If you don't want to filter by server name,
> pass an empty hash / string as shown below.
> Examples:
> hbase> list_regions 'table_name'
> hbase> list_regions 'table_name', 'server_name'
> hbase> list_regions 'table_name', {SERVER_NAME => 'server_name',
> LOCALITY_THRESHOLD => 0.8}
> hbase> list_regions 'table_name', {SERVER_NAME => 'server_name',
> LOCALITY_THRESHOLD => 0.8}, ['SERVER_NAME']
> hbase> list_regions 'table_name', {}, ['SERVER_NAME', 'start_key']
> hbase> list_regions 'table_name', '', ['SERVER_NAME', 'start_key']
> Took 0.0283 seconds{noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-20253) Error message is missing for restore_snapshot
[
https://issues.apache.org/jira/browse/HBASE-20253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-20253:
--
Fix Version/s: (was: 3.0.0-alpha-1)
> Error message is missing for restore_snapshot
> -
>
> Key: HBASE-20253
> URL: https://issues.apache.org/jira/browse/HBASE-20253
> Project: HBase
> Issue Type: Sub-task
> Components: shell
>Affects Versions: 2.0.0
>Reporter: Peter Somogyi
>Assignee: Gabor Bota
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-20253.master.001.patch,
> HBASE-20253.master.002.patch, HBASE-20253.master.003.patch,
> HBASE-20253.master.004.patch
>
>
> When the table is not disabled and restore_snapshot executed the error
> message is useless, only displays the table name.
> hbase(main):007:0> restore_snapshot 'tsnap'
> ERROR: t
> Restore a specified snapshot.
> The restore will replace the content of the original table,
> bringing back the content to the snapshot state.
> The table must be disabled.
> Examples:
> hbase> restore_snapshot 'snapshotName'
> Following command will restore all acl from snapshot table into the table.
> hbase> restore_snapshot 'snapshotName', \{RESTORE_ACL=>true}
> Took 0.1044 seconds
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-20161) disable HBase-Trunk_matrix job
[ https://issues.apache.org/jira/browse/HBASE-20161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-20161: -- Fix Version/s: (was: 3.0.0-alpha-1) > disable HBase-Trunk_matrix job > -- > > Key: HBASE-20161 > URL: https://issues.apache.org/jira/browse/HBASE-20161 > Project: HBase > Issue Type: Task > Components: community, test >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Major > > The nightly master job: > https://builds.apache.org/job/HBase%20Nightly/job/master/ > Is doing the same work and should be where we spend future effort. > This job can go: > https://builds.apache.org/view/H-L/view/HBase/job/HBase-Trunk_matrix/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-20169) NPE when calling HBTU.shutdownMiniCluster (TestAssignmentManagerMetrics is flakey)
[
https://issues.apache.org/jira/browse/HBASE-20169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-20169:
--
Fix Version/s: 2.0.0
(was: 3.0.0-alpha-1)
(was: 2.0.1)
> NPE when calling HBTU.shutdownMiniCluster (TestAssignmentManagerMetrics is
> flakey)
> --
>
> Key: HBASE-20169
> URL: https://issues.apache.org/jira/browse/HBASE-20169
> Project: HBase
> Issue Type: Bug
> Components: test
>Reporter: Duo Zhang
>Assignee: Chia-Ping Tsai
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: HBASE-20169.branch-2.0.001.patch,
> HBASE-20169.branch-2.001.patch, HBASE-20169.branch-2.002.patch,
> HBASE-20169.branch-2.003.patch, HBASE-20169.branch-2.004.patch,
> HBASE-20169.branch-2.005.patch, HBASE-20169.master.001.ADDENDUM.patch,
> HBASE-20169.master.001.ADDENDUM.patch, HBASE-20169.v0.addendum.patch
>
>
> This usually happens when some master or rs has already been down before we
> calling shutdownMiniCluster.
> See
> https://builds.apache.org/job/HBASE-Flaky-Tests/27223/testReport/junit/org.apache.hadoop.hbase.master/TestAssignmentManagerMetrics/org_apache_hadoop_hbase_master_TestAssignmentManagerMetrics/
> and also
> http://104.198.223.121:8080/job/HBASE-Flaky-Tests/34873/testReport/junit/org.apache.hadoop.hbase.master/TestRestartCluster/testRetainAssignmentOnRestart/
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.TestAssignmentManagerMetrics.after(TestAssignmentManagerMetrics.java:100)
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.TestRestartCluster.testRetainAssignmentOnRestart(TestRestartCluster.java:156)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-20112) Include test results from nightly hadoop3 tests in jenkins test results
[ https://issues.apache.org/jira/browse/HBASE-20112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-20112: -- Fix Version/s: 2.0.0 (was: 3.0.0-alpha-1) (was: 2.1.0) (was: 2.0.1) > Include test results from nightly hadoop3 tests in jenkins test results > --- > > Key: HBASE-20112 > URL: https://issues.apache.org/jira/browse/HBASE-20112 > Project: HBase > Issue Type: Task > Components: test >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Critical > Fix For: 1.3.3, 1.4.4, 2.0.0, 1.2.7 > > Attachments: HBASE-20112.0.patch > > > right now our nightly tests that run atop hadoop 3 are reported on pass/fail > but aren't recorded via the jenkins reporting mechanism. > we should add them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-20068) Hadoopcheck project health check uses default maven repo instead of yetus managed ones
[
https://issues.apache.org/jira/browse/HBASE-20068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-20068:
--
Fix Version/s: 2.0.0
(was: 3.0.0-alpha-1)
(was: 2.1.0)
(was: 2.0.1)
> Hadoopcheck project health check uses default maven repo instead of yetus
> managed ones
> --
>
> Key: HBASE-20068
> URL: https://issues.apache.org/jira/browse/HBASE-20068
> Project: HBase
> Issue Type: Bug
> Components: community, test
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Major
> Fix For: 1.3.3, 1.4.4, 2.0.0, 1.2.7
>
> Attachments: HBASE-20068.0.patch, HBASE-20068.1.patch
>
>
> Recently had a precommit run fail hadoop check for all 3 versions with
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:2.5.2:install (default-install)
> on project hbase-thrift: Failed to install metadata
> org.apache.hbase:hbase-thrift:3.0.0-SNAPSHOT/maven-metadata.xml: Could not
> parse metadata
> /home/jenkins/.m2/repository/org/apache/hbase/hbase-thrift/3.0.0-SNAPSHOT/maven-metadata-local.xml:
> in epilog non whitespace content is not allowed but got / (position: END_TAG
> seen ...\n/... @25:2) -> [Help 1]
> {code}
> Looks like maven repo corruption.
> Also the path {{/home/jenkins/.m2/repository}} means that those invocations
> are using the jenkins user repo, which isn't safe since there are multiple
> executors. either the plugin isn't using the yetus provided maven repo path
> or our yetus invocation isn't telling yetus to provide its own maven repo
> path.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-19547) HBase fails building on AArch64 due to asciidoctor-maven-plugin.
[
https://issues.apache.org/jira/browse/HBASE-19547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-19547:
--
Fix Version/s: (was: 3.0.0-alpha-1)
> HBase fails building on AArch64 due to asciidoctor-maven-plugin.
>
>
> Key: HBASE-19547
> URL: https://issues.apache.org/jira/browse/HBASE-19547
> Project: HBase
> Issue Type: Bug
> Components: build, documentation, website
>Affects Versions: 3.0.0-alpha-1
>Reporter: Yuqi Gu
>Assignee: Yuqi Gu
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-19547.patch
>
>
> HBase fails building on AArch64 due to asciidoctor-maven-plugin.
> {code:java}
> mvn clean site package install -DskipTests
> [ERROR] Failed to execute
> goal org.asciidoctor:asciidoctor-maven-plugin:1.5.5:
> process-asciidoc (output-pdf) on project hbase:
> Execution output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.5:
> process-asciidoc failed: (NotImplementedError)
> fstat unimplemented unsupported or native support failed to load ->
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-19506) Support variable sized chunks from ChunkCreator
[ https://issues.apache.org/jira/browse/HBASE-19506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-19506: -- Fix Version/s: 2.0.0 (was: 3.0.0-alpha-1) > Support variable sized chunks from ChunkCreator > --- > > Key: HBASE-19506 > URL: https://issues.apache.org/jira/browse/HBASE-19506 > Project: HBase > Issue Type: Sub-task >Reporter: Anastasia Braginsky >Assignee: Anastasia Braginsky >Priority: Major > Fix For: 2.0.0 > > Attachments: HBASE-19506-V01.patch, HBASE-19506-V02.patch, > HBASE-19506-V03.patch, HBASE-19506-V04.patch, HBASE-19506-V05.patch, > HBASE-19506-V06.patch, HBASE-19506-V07.patch, HBASE-19506-V08.patch, > HBASE-19506-V09.patch > > > When CellChunkMap is created it allocates a special index chunk (or chunks) > where array of cell-representations is stored. When the number of > cell-representations is small, it is preferable to allocate a chunk smaller > than a default value which is 2MB. > On the other hand, those "non-standard size" chunks can not be used in pool. > On-demand allocations in off-heap are costly. So this JIRA is about to > investigate the trade of between memory usage and the final performance. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-19174) Update link to HBase presentations
[ https://issues.apache.org/jira/browse/HBASE-19174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-19174: -- Fix Version/s: 2.0.0 (was: 3.0.0-alpha-1) > Update link to HBase presentations > -- > > Key: HBASE-19174 > URL: https://issues.apache.org/jira/browse/HBASE-19174 > Project: HBase > Issue Type: Improvement > Components: documentation >Reporter: Jan Hentschel >Assignee: Jan Hentschel >Priority: Trivial > Fix For: 2.0.0 > > Attachments: HBASE-19174.master.001.patch, > HBASE-19174.master.002.patch > > > old_news.adoc references to the [Hadoop > wiki|https://wiki.apache.org/hadoop/HBase/HBasePresentations] for past > presentations. The page itself states that it will be decommissioned in the > future. The link should go to the book instead. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-19068) Change all url of apache.org from HTTP to HTTPS in HBase book
[ https://issues.apache.org/jira/browse/HBASE-19068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-19068: -- Fix Version/s: 2.0.0 (was: 3.0.0-alpha-1) > Change all url of apache.org from HTTP to HTTPS in HBase book > - > > Key: HBASE-19068 > URL: https://issues.apache.org/jira/browse/HBASE-19068 > Project: HBase > Issue Type: Improvement > Components: documentation >Reporter: Yung-An He >Assignee: Yung-An He >Priority: Major > Fix For: 2.0.0 > > Attachments: HBASE-19068-master.patch > > > We should change all the links of apache.org from HTTP to HTTPS in our hbase > book due to the security issue. Also, fix the broken link in the package > summary to org.apache.hadoop.metrics. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-18622) Mitigate API compatibility concerns between branch-1 and branch-2
[ https://issues.apache.org/jira/browse/HBASE-18622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-18622: -- Fix Version/s: (was: 3.0.0-alpha-1) > Mitigate API compatibility concerns between branch-1 and branch-2 > - > > Key: HBASE-18622 > URL: https://issues.apache.org/jira/browse/HBASE-18622 > Project: HBase > Issue Type: Bug > Components: API >Reporter: Michael Stack >Assignee: Michael Stack >Priority: Blocker > Fix For: 2.1.0, 2.0.2 > > Attachments: report.1.2_2.0.html.gz > > > This project is to do what [~apurtell] did in the issue "HBASE-18431 Mitigate > compatibility concerns between branch-1.3 and branch-1.4" only do it between > branch-1 and branch-2. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (HBASE-18506) java.lang.AbstractMethodError in hbase REST server
[
https://issues.apache.org/jira/browse/HBASE-18506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang reopened HBASE-18506:
---
> java.lang.AbstractMethodError in hbase REST server
> --
>
> Key: HBASE-18506
> URL: https://issues.apache.org/jira/browse/HBASE-18506
> Project: HBase
> Issue Type: Bug
> Components: REST
>Affects Versions: 3.0.0-alpha-1, 2.0.0-alpha-1
>Reporter: Samir Ahmic
>Assignee: Samir Ahmic
>Priority: Blocker
> Fix For: 3.0.0-alpha-1
>
>
> Just run it this one while testing some scripts. Basically any call to
> service will end up with 500 error. After some checking it looks like we have
> some issues with dependencies incompatibility.
> Here is more details:
> {code}
> Stack trace:
> 2017-08-02 20:46:25,407 WARN [qtp422330142-30] servlet.ServletHandler: Error
> for /status/cluster
> java.lang.AbstractMethodError:
> javax.ws.rs.core.UriBuilder.uri(Ljava/lang/String;)Ljavax/ws/rs/core/UriBuilder;
> at javax.ws.rs.core.UriBuilder.fromUri(UriBuilder.java:119)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:298)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1689)
> at
> org.apache.hadoop.hbase.rest.filter.GzipFilter.doFilter(GzipFilter.java:77)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1676)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1160)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1092)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
> at org.eclipse.jetty.server.Server.handle(Server.java:518)
> at
> org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:308)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:244)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
> at
> org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
> at
> org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
> at
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:246)
> at
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:156)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> and here are suspects from lib dir
> {code}
> $ grep -r "UriBuilder" .
> Binary file ./javax.ws.rs-api-2.0.1.jar matches
> Binary file ./jersey-common-2.25.1.jar matches
> Binary file ./jersey-core-1.9.jar matches
> {code}
> I have also checked hbase-1.2.6 we have only jersey-core-1.9.jar there
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-18506) java.lang.AbstractMethodError in hbase REST server
[
https://issues.apache.org/jira/browse/HBASE-18506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-18506.
---
Fix Version/s: (was: 3.0.0-alpha-1)
Resolution: Implemented
> java.lang.AbstractMethodError in hbase REST server
> --
>
> Key: HBASE-18506
> URL: https://issues.apache.org/jira/browse/HBASE-18506
> Project: HBase
> Issue Type: Bug
> Components: REST
>Affects Versions: 3.0.0-alpha-1, 2.0.0-alpha-1
>Reporter: Samir Ahmic
>Assignee: Samir Ahmic
>Priority: Blocker
>
> Just run it this one while testing some scripts. Basically any call to
> service will end up with 500 error. After some checking it looks like we have
> some issues with dependencies incompatibility.
> Here is more details:
> {code}
> Stack trace:
> 2017-08-02 20:46:25,407 WARN [qtp422330142-30] servlet.ServletHandler: Error
> for /status/cluster
> java.lang.AbstractMethodError:
> javax.ws.rs.core.UriBuilder.uri(Ljava/lang/String;)Ljavax/ws/rs/core/UriBuilder;
> at javax.ws.rs.core.UriBuilder.fromUri(UriBuilder.java:119)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:298)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1689)
> at
> org.apache.hadoop.hbase.rest.filter.GzipFilter.doFilter(GzipFilter.java:77)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1676)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1160)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1092)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
> at org.eclipse.jetty.server.Server.handle(Server.java:518)
> at
> org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:308)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:244)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
> at
> org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
> at
> org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
> at
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:246)
> at
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:156)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> and here are suspects from lib dir
> {code}
> $ grep -r "UriBuilder" .
> Binary file ./javax.ws.rs-api-2.0.1.jar matches
> Binary file ./jersey-common-2.25.1.jar matches
> Binary file ./jersey-core-1.9.jar matches
> {code}
> I have also checked hbase-1.2.6 we have only jersey-core-1.9.jar there
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-18391) List the stuffs which are using the patent grant license (PATENTS file) of Facebook; And then discuss and remove them.
[ https://issues.apache.org/jira/browse/HBASE-18391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-18391: -- Fix Version/s: (was: 3.0.0-alpha-1) > List the stuffs which are using the patent grant license (PATENTS file) of > Facebook; And then discuss and remove them. > -- > > Key: HBASE-18391 > URL: https://issues.apache.org/jira/browse/HBASE-18391 > Project: HBase > Issue Type: Sub-task > Components: community, dependencies >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Blocker > Labels: incompatible > > See ["Apache Foundation disallows use of the Facebook “BSD+Patent” > license"|https://news.ycombinator.com/item?id=14779881] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-18326) Fix and reenable TestMasterProcedureWalLease
[ https://issues.apache.org/jira/browse/HBASE-18326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-18326. --- Fix Version/s: (was: 3.0.0-alpha-1) (was: 2.3.0) Resolution: Not A Problem > Fix and reenable TestMasterProcedureWalLease > > > Key: HBASE-18326 > URL: https://issues.apache.org/jira/browse/HBASE-18326 > Project: HBase > Issue Type: Sub-task > Components: test >Reporter: Michael Stack >Assignee: Szabolcs Bukros >Priority: Blocker > > Fix and reenable flakey important test. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (HBASE-18326) Fix and reenable TestMasterProcedureWalLease
[ https://issues.apache.org/jira/browse/HBASE-18326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reopened HBASE-18326: --- > Fix and reenable TestMasterProcedureWalLease > > > Key: HBASE-18326 > URL: https://issues.apache.org/jira/browse/HBASE-18326 > Project: HBase > Issue Type: Sub-task > Components: test >Reporter: Michael Stack >Assignee: Szabolcs Bukros >Priority: Blocker > Fix For: 3.0.0-alpha-1, 2.3.0 > > > Fix and reenable flakey important test. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-17919) HBase 2.x over hadoop 3.x umbrella
[ https://issues.apache.org/jira/browse/HBASE-17919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-17919: -- Fix Version/s: (was: 3.0.0-alpha-1) > HBase 2.x over hadoop 3.x umbrella > --- > > Key: HBASE-17919 > URL: https://issues.apache.org/jira/browse/HBASE-17919 > Project: HBase > Issue Type: Umbrella > Components: hadoop3 >Affects Versions: 2.0.0 >Reporter: Jonathan Hsieh >Priority: Critical > > We should try to get hbase 2.x branch working against the recently release > hadoop 3.0.0 alphas. These days 3.0.0-alpha2 is the latest. > HBASE-16733 and HBASE-17593 got the compile level checks in but we should > progress to getting unit tests to pass and a build against hadoop3 up. > This umbrella issue will capture issues around this project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HBASE-17852) Add Fault tolerance to HBASE-14417 (Support bulk loaded files in incremental backup)
[
https://issues.apache.org/jira/browse/HBASE-17852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885536#comment-17885536
]
Duo Zhang commented on HBASE-17852:
---
While audit the issues for 3.0.0 release, I found that there is no commit with
HBASE-17852 in our code but the fix version for this issue has 3.0.0-alpha-1.
But I can see this commit
{noformat}
commit a5601c8eac6bfcac7d869574547f505d44e49065
Author: Vladimir Rodionov
Date: Wed Jan 10 16:26:09 2018 -0800
HBASE-19568: Restore of HBase table using incremental backup doesn't
restore rows from an earlier incremental backup
Signed-off-by: Josh Elser
{noformat}
So I guess we used the wrong commit message or something? Anyway, since these
two issues seem to want to fix the same problem, include either one in the
release note is enough?
So I plan to remove the fix version here.
Shout if there are any problems.
Thanks.
> Add Fault tolerance to HBASE-14417 (Support bulk loaded files in incremental
> backup)
>
>
> Key: HBASE-17852
> URL: https://issues.apache.org/jira/browse/HBASE-17852
> Project: HBase
> Issue Type: Sub-task
>Reporter: Vladimir Rodionov
>Assignee: Vladimir Rodionov
>Priority: Major
> Fix For: 3.0.0-alpha-1
>
> Attachments: HBASE-17852-v10.patch, screenshot-1.png
>
>
> Design approach rollback-via-snapshot implemented in this ticket:
> # Before backup create/delete/merge starts we take a snapshot of the backup
> meta-table (backup system table). This procedure is lightweight because meta
> table is small, usually should fit a single region.
> # When operation fails on a server side, we handle this failure by cleaning
> up partial data in backup destination, followed by restoring backup
> meta-table from a snapshot.
> # When operation fails on a client side (abnormal termination, for example),
> next time user will try create/merge/delete he(she) will see error message,
> that system is in inconsistent state and repair is required, he(she) will
> need to run backup repair tool.
> # To avoid multiple writers to the backup system table (backup client and
> BackupObserver's) we introduce small table ONLY to keep listing of bulk
> loaded files. All backup observers will work only with this new tables. The
> reason: in case of a failure during backup create/delete/merge/restore, when
> system performs automatic rollback, some data written by backup observers
> during failed operation may be lost. This is what we try to avoid.
> # Second table keeps only bulk load related references. We do not care about
> consistency of this table, because bulk load is idempotent operation and can
> be repeated after failure. Partially written data in second table does not
> affect on BackupHFileCleaner plugin, because this data (list of bulk loaded
> files) correspond to a files which have not been loaded yet successfully and,
> hence - are not visible to the system
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-17852) Add Fault tolerance to HBASE-14417 (Support bulk loaded files in incremental backup)
[ https://issues.apache.org/jira/browse/HBASE-17852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-17852: -- Fix Version/s: (was: 3.0.0-alpha-1) > Add Fault tolerance to HBASE-14417 (Support bulk loaded files in incremental > backup) > > > Key: HBASE-17852 > URL: https://issues.apache.org/jira/browse/HBASE-17852 > Project: HBase > Issue Type: Sub-task >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov >Priority: Major > Attachments: HBASE-17852-v10.patch, screenshot-1.png > > > Design approach rollback-via-snapshot implemented in this ticket: > # Before backup create/delete/merge starts we take a snapshot of the backup > meta-table (backup system table). This procedure is lightweight because meta > table is small, usually should fit a single region. > # When operation fails on a server side, we handle this failure by cleaning > up partial data in backup destination, followed by restoring backup > meta-table from a snapshot. > # When operation fails on a client side (abnormal termination, for example), > next time user will try create/merge/delete he(she) will see error message, > that system is in inconsistent state and repair is required, he(she) will > need to run backup repair tool. > # To avoid multiple writers to the backup system table (backup client and > BackupObserver's) we introduce small table ONLY to keep listing of bulk > loaded files. All backup observers will work only with this new tables. The > reason: in case of a failure during backup create/delete/merge/restore, when > system performs automatic rollback, some data written by backup observers > during failed operation may be lost. This is what we try to avoid. > # Second table keeps only bulk load related references. We do not care about > consistency of this table, because bulk load is idempotent operation and can > be repeated after failure. Partially written data in second table does not > affect on BackupHFileCleaner plugin, because this data (list of bulk loaded > files) correspond to a files which have not been loaded yet successfully and, > hence - are not visible to the system -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-17664) Remove unnecessary semicolons throughout the code base
[ https://issues.apache.org/jira/browse/HBASE-17664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-17664: -- Fix Version/s: (was: 3.0.0-alpha-1) > Remove unnecessary semicolons throughout the code base > -- > > Key: HBASE-17664 > URL: https://issues.apache.org/jira/browse/HBASE-17664 > Project: HBase > Issue Type: Task >Reporter: Jan Hentschel >Assignee: Jan Hentschel >Priority: Trivial > Attachments: HBASE-17664.master.001.patch > > > Currently there are a lot of places throughout the code base which have > unnecessary semicolons. They should be removed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (HBASE-28844) Align the fixed issues in git and jira
[
https://issues.apache.org/jira/browse/HBASE-28844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885509#comment-17885509
]
Duo Zhang edited comment on HBASE-28844 at 9/28/24 6:21 AM:
I've written a simple script to output the differences.
https://github.com/Apache9/hbase-release-audit/blob/main/audit-git-commit-jira-issue.py
This is the result
{noformat}
Commit to previous release but not in current release:
HBASE-12350
HBASE-17553
HBASE-18187
HBASE-18190
HBASE-18282
HBASE-18431
HBASE-18514
HBASE-18594
HBASE-18595
HBASE-18615
HBASE-18653
HBASE-18817
HBASE-18819
HBASE-18828
HBASE-18833
HBASE-18933
HBASE-19197
HBASE-19315
HBASE-19407
HBASE-19648
HBASE-19670
HBASE-19716
HBASE-19860
HBASE-19888
HBASE-20113
HBASE-20142
HBASE-20233
HBASE-20246
HBASE-20247
HBASE-20415
HBASE-20462
HBASE-20464
Issues in jira but not in git commits:
HBASE-13126 Umbrella for release notes
HBASE-13992 In 2.0.0 but reverted(hbase-spark)
HBASE-14123 In 2.0.0 but reverted(backup&restore)
HBASE-14150 In 2.0.0 but reverted(hbase-spark)
HBASE-14158 In 2.0.0 but reverted(hbase-spark)
HBASE-14159 In 2.0.0 but reverted(hbase-spark)
HBASE-14161 No actual code commit, jenkins change, remove fix version
HBASE-14181 In 2.0.0 but reverted(hbase-spark)
HBASE-14184 In 2.0.0 but reverted(hbase-spark)
HBASE-14340 In 2.0.0 but reverted(hbase-spark)
HBASE-14375 In 2.0.0 but reverted(hbase-spark)
HBASE-14377 In 2.0.0 but reverted(hbase-spark)
HBASE-14406 In 2.0.0 but reverted(hbase-spark)
HBASE-14515 In 2.0.0 but reverted(hbase-spark)
HBASE-14789 In 2.0.0 but reverted(hbase-spark)
HBASE-14849 In 2.0.0 but reverted(hbase-spark)
HBASE-15161 Umbrella for release notes
HBASE-15184 In 2.0.0 but reverted(hbase-spark)
HBASE-15282 In 2.0.0 but reverted(hbase-spark)
HBASE-15291 Should be in 2.0.0, fixed
HBASE-15310 In 2.0.0 but reverted(hbase-spark)
HBASE-15333 In 2.0.0 but reverted(hbase-spark)
HBASE-15336
HBASE-15434
HBASE-15466
HBASE-15473
HBASE-15572
HBASE-15597
HBASE-15809
HBASE-16638
HBASE-16804
HBASE-16823
HBASE-17546
HBASE-17547
HBASE-17549
HBASE-17574
HBASE-17664
HBASE-17852
HBASE-17909
HBASE-17918
HBASE-17919
HBASE-17933
HBASE-18070
HBASE-18095
HBASE-18175
HBASE-18176
HBASE-18326
HBASE-18391
HBASE-18506
HBASE-18622
HBASE-18646
HBASE-18659
HBASE-19064
HBASE-19068
HBASE-19174
HBASE-19397
HBASE-19506
HBASE-19547
HBASE-20006
HBASE-20046
HBASE-20068
HBASE-20112
HBASE-20152
HBASE-20161
HBASE-20169
HBASE-20253
HBASE-20287
HBASE-20293
HBASE-20335
HBASE-20338
HBASE-20360
HBASE-20364
HBASE-20376
HBASE-20379
HBASE-20389
HBASE-20404
HBASE-20409
HBASE-20410
HBASE-20438
HBASE-20439
HBASE-20440
HBASE-20441
HBASE-20442
HBASE-20443
HBASE-20540
HBASE-20610
HBASE-20751
HBASE-20934
HBASE-21078
HBASE-21113
HBASE-21169
HBASE-21192
HBASE-21335
HBASE-21360
HBASE-21430
HBASE-21512
HBASE-21540
HBASE-21745
HBASE-21879
HBASE-22120
HBASE-22218
HBASE-22484
HBASE-22514
HBASE-22740
HBASE-22834
HBASE-22953
HBASE-22992
HBASE-23100
HBASE-23150
HBASE-23224
HBASE-23601
HBASE-23797
HBASE-23841
HBASE-24001
HBASE-24109
HBASE-24169
HBASE-24177
HBASE-24213
HBASE-24217
HBASE-24250
HBASE-24457
HBASE-24507
HBASE-24573
HBASE-25099
HBASE-25450
HBASE-25649
HBASE-25658
HBASE-25666
HBASE-25826
HBASE-25865
HBASE-25876
HBASE-25920
HBASE-26023
HBASE-26067
HBASE-26233
HBASE-26275
HBASE-26321
HBASE-26372
HBASE-26419
HBASE-26487
HBASE-26789
HBASE-26874
HBASE-26898
HBASE-26932
HBASE-26949
HBASE-27108
HBASE-27109
HBASE-27110
HBASE-28020
HBASE-28021
HBASE-2803
[jira] [Updated] (HBASE-15466) precommit should not run all java goals when given a docs-only patch
[ https://issues.apache.org/jira/browse/HBASE-15466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-15466: -- Fix Version/s: (was: 3.0.0-alpha-1) > precommit should not run all java goals when given a docs-only patch > > > Key: HBASE-15466 > URL: https://issues.apache.org/jira/browse/HBASE-15466 > Project: HBase > Issue Type: Improvement > Components: build >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Major > Fix For: 1.3.3, 1.4.4, 2.0.0, 1.2.7 > > Attachments: HBASE-15466.0.patch, HBASE-15466.1.patch, > HBASE-15466.2.patch, HBASE-15466.3.patch > > > Right now docs-only patches (those that only impact the top level > src/main/site, src/main/asciidoc, or src/main/xslt) run through all of the > java related precommit checks, including test4tests and the full unit test > suite. > Since we know these paths don't require those checks, we should update our > personality to skip them. (or fix our project structure to match "the maven > way".) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (HBASE-28844) Align the fixed issues in git and jira
[
https://issues.apache.org/jira/browse/HBASE-28844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885509#comment-17885509
]
Duo Zhang edited comment on HBASE-28844 at 9/28/24 3:04 AM:
I've written a simple script to output the differences.
https://github.com/Apache9/hbase-release-audit/blob/main/audit-git-commit-jira-issue.py
This is the result
{noformat}
Commit to previous release but not in current release:
HBASE-12350
HBASE-17553
HBASE-18187
HBASE-18190
HBASE-18282
HBASE-18431
HBASE-18514
HBASE-18594
HBASE-18595
HBASE-18615
HBASE-18653
HBASE-18817
HBASE-18819
HBASE-18828
HBASE-18833
HBASE-18933
HBASE-19197
HBASE-19315
HBASE-19407
HBASE-19648
HBASE-19670
HBASE-19716
HBASE-19860
HBASE-19888
HBASE-20113
HBASE-20142
HBASE-20233
HBASE-20246
HBASE-20247
HBASE-20415
HBASE-20462
HBASE-20464
Issues in jira but not in git commits:
HBASE-13126 Umbrella for release notes
HBASE-13992 In 2.0.0 but reverted
HBASE-14123 In 2.0.0 but reverted
HBASE-14150 In 2.0.0 but reverted
HBASE-14158 In 2.0.0 but reverted
HBASE-14159 In 2.0.0 but reverted
HBASE-14161 No actual code commit, jenkins change, remove fix version
HBASE-14181 In 2.0.0 but reverted
HBASE-14184 In 2.0.0 but reverted
HBASE-14340 In 2.0.0 but reverted
HBASE-14375 In 2.0.0 but reverted
HBASE-14377 In 2.0.0 but reverted
HBASE-14406 In 2.0.0 but reverted
HBASE-14515 In 2.0.0 but reverted
HBASE-14789 In 2.0.0 but reverted
HBASE-14849 In 2.0.0 but reverted
HBASE-15161 Umbrella for release notes
HBASE-15184 In 2.0.0 but reverted
HBASE-15282 In 2.0.0 but reverted
HBASE-15291 Should be in 2.0.0, fixed
HBASE-15310 In 2.0.0 but reverted
HBASE-15333 In 2.0.0 but reverted
HBASE-15336
HBASE-15434
HBASE-15466
HBASE-15473
HBASE-15572
HBASE-15597
HBASE-15809
HBASE-16638
HBASE-16804
HBASE-16823
HBASE-17546
HBASE-17547
HBASE-17549
HBASE-17574
HBASE-17664
HBASE-17852
HBASE-17909
HBASE-17918
HBASE-17919
HBASE-17933
HBASE-18070
HBASE-18095
HBASE-18175
HBASE-18176
HBASE-18326
HBASE-18391
HBASE-18506
HBASE-18622
HBASE-18646
HBASE-18659
HBASE-19064
HBASE-19068
HBASE-19174
HBASE-19397
HBASE-19506
HBASE-19547
HBASE-20006
HBASE-20046
HBASE-20068
HBASE-20112
HBASE-20152
HBASE-20161
HBASE-20169
HBASE-20253
HBASE-20287
HBASE-20293
HBASE-20335
HBASE-20338
HBASE-20360
HBASE-20364
HBASE-20376
HBASE-20379
HBASE-20389
HBASE-20404
HBASE-20409
HBASE-20410
HBASE-20438
HBASE-20439
HBASE-20440
HBASE-20441
HBASE-20442
HBASE-20443
HBASE-20540
HBASE-20610
HBASE-20751
HBASE-20934
HBASE-21078
HBASE-21113
HBASE-21169
HBASE-21192
HBASE-21335
HBASE-21360
HBASE-21430
HBASE-21512
HBASE-21540
HBASE-21745
HBASE-21879
HBASE-22120
HBASE-22218
HBASE-22484
HBASE-22514
HBASE-22740
HBASE-22834
HBASE-22953
HBASE-22992
HBASE-23100
HBASE-23150
HBASE-23224
HBASE-23601
HBASE-23797
HBASE-23841
HBASE-24001
HBASE-24109
HBASE-24169
HBASE-24177
HBASE-24213
HBASE-24217
HBASE-24250
HBASE-24457
HBASE-24507
HBASE-24573
HBASE-25099
HBASE-25450
HBASE-25649
HBASE-25658
HBASE-25666
HBASE-25826
HBASE-25865
HBASE-25876
HBASE-25920
HBASE-26023
HBASE-26067
HBASE-26233
HBASE-26275
HBASE-26321
HBASE-26372
HBASE-26419
HBASE-26487
HBASE-26789
HBASE-26874
HBASE-26898
HBASE-26932
HBASE-26949
HBASE-27108
HBASE-27109
HBASE-27110
HBASE-28020
HBASE-28021
HBASE-28032
HBASE-28047
HBASE-28063
HBASE-28151
HBASE-28196
HBASE-28198
HBASE-28519
HBASE-28674
HBASE-28713
Issues in git commits but not in jira:
HBASE-13866
HBASE-14
[jira] [Updated] (HBASE-15291) FileSystem not closed in secure bulkLoad
[ https://issues.apache.org/jira/browse/HBASE-15291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-15291: -- Fix Version/s: 2.0.0 (was: 3.0.0-alpha-1) (was: 2.1.0) (was: 2.0.1) > FileSystem not closed in secure bulkLoad > > > Key: HBASE-15291 > URL: https://issues.apache.org/jira/browse/HBASE-15291 > Project: HBase > Issue Type: Bug >Affects Versions: 1.0.2, 0.98.16.1 >Reporter: Yong Zhang >Assignee: Ashish Singhi >Priority: Major > Fix For: 1.3.3, 1.4.4, 2.0.0, 1.2.7 > > Attachments: HBASE-15291-branch-1.2.patch, > HBASE-15291-branch-1.patch, HBASE-15291-revert-master.patch, > HBASE-15291.001.patch, HBASE-15291.002.patch, HBASE-15291.003.patch, > HBASE-15291.004.patch, HBASE-15291.addendum, HBASE-15291.patch, > HBASE-15291.v1.patch, HBASE-15291.v2.patch, HBASE-15291.v2.patch, patch > > > FileSystem not closed in secure bulkLoad after bulkLoad finish, it will > cause memory used more and more if too many bulkLoad . -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-14161) Add hbase-spark integration tests to IT jenkins job
[ https://issues.apache.org/jira/browse/HBASE-14161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-14161: -- Fix Version/s: (was: 3.0.0-alpha-1) > Add hbase-spark integration tests to IT jenkins job > --- > > Key: HBASE-14161 > URL: https://issues.apache.org/jira/browse/HBASE-14161 > Project: HBase > Issue Type: Task > Components: build >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Major > > expand the set of ITs we run to include the new hbase-spark tests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-14123) HBase Backup/Restore Phase 2
[ https://issues.apache.org/jira/browse/HBASE-14123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-14123: -- Component/s: backup&restore > HBase Backup/Restore Phase 2 > > > Key: HBASE-14123 > URL: https://issues.apache.org/jira/browse/HBASE-14123 > Project: HBase > Issue Type: Umbrella > Components: backup&restore >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov >Priority: Blocker > Fix For: 3.0.0-alpha-1 > > Attachments: 14123-master.v14.txt, 14123-master.v15.txt, > 14123-master.v16.txt, 14123-master.v17.txt, 14123-master.v18.txt, > 14123-master.v19.txt, 14123-master.v2.txt, 14123-master.v20.txt, > 14123-master.v21.txt, 14123-master.v24.txt, 14123-master.v25.txt, > 14123-master.v27.txt, 14123-master.v28.txt, 14123-master.v29.full.txt, > 14123-master.v3.txt, 14123-master.v30.txt, 14123-master.v31.txt, > 14123-master.v32.txt, 14123-master.v33.txt, 14123-master.v34.txt, > 14123-master.v35.txt, 14123-master.v36.txt, 14123-master.v37.txt, > 14123-master.v38.txt, 14123-master.v5.txt, 14123-master.v6.txt, > 14123-master.v7.txt, 14123-master.v8.txt, 14123-master.v9.txt, 14123-v14.txt, > 14123.master.v39.patch, 14123.master.v40.patch, 14123.master.v41.patch, > 14123.master.v42.patch, 14123.master.v44.patch, 14123.master.v45.patch, > 14123.master.v46.patch, 14123.master.v48.patch, 14123.master.v49.patch, > 14123.master.v50.patch, 14123.master.v51.patch, 14123.master.v52.patch, > 14123.master.v54.patch, 14123.master.v56.patch, 14123.master.v57.patch, > 14123.master.v58.patch, 14123.master.v59.patch, 14123.master.v60.patch, > 14123.master.v61.patch, Backup-restoreinHBase2.0 (1).pdf, > Backup-restoreinHBase2.0 (3).pdf, Backup-restoreinHBase2.0 (4).pdf, > Backup-restoreinHBase2.0.pdf, HBASE-14123-for-7912-v1.patch, > HBASE-14123-for-7912-v6.patch, HBASE-14123-v1.patch, HBASE-14123-v10.patch, > HBASE-14123-v11.patch, HBASE-14123-v12.patch, HBASE-14123-v13.patch, > HBASE-14123-v15.patch, HBASE-14123-v16.patch, HBASE-14123-v2.patch, > HBASE-14123-v3.patch, HBASE-14123-v4.patch, HBASE-14123-v5.patch, > HBASE-14123-v6.patch, HBASE-14123-v7.patch, HBASE-14123-v9.patch > > > Phase 2 umbrella JIRA. See HBASE-7912 for design document and description. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-13992) Integrate SparkOnHBase into HBase
[ https://issues.apache.org/jira/browse/HBASE-13992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-13992: -- Fix Version/s: 3.0.0-alpha-1 > Integrate SparkOnHBase into HBase > - > > Key: HBASE-13992 > URL: https://issues.apache.org/jira/browse/HBASE-13992 > Project: HBase > Issue Type: New Feature > Components: hbase-connectors, spark >Reporter: Theodore michael Malaska >Assignee: Theodore michael Malaska >Priority: Major > Fix For: 3.0.0-alpha-1, connector-1.0.0 > > Attachments: HBASE-13992.10.patch, HBASE-13992.11.patch, > HBASE-13992.12.patch, HBASE-13992.5.patch, HBASE-13992.6.patch, > HBASE-13992.7.patch, HBASE-13992.8.patch, HBASE-13992.9.patch, > HBASE-13992.patch, HBASE-13992.patch.3, HBASE-13992.patch.4, > HBASE-13992.patch.5 > > > This Jira is to ask if SparkOnHBase can find a home in side HBase core. > Here is the github: > https://github.com/cloudera-labs/SparkOnHBase > I am the core author of this project and the license is Apache 2.0 > A blog explaining this project is here > http://blog.cloudera.com/blog/2014/12/new-in-cloudera-labs-sparkonhbase/ > A spark Streaming example is here > http://blog.cloudera.com/blog/2014/11/how-to-do-near-real-time-sessionization-with-spark-streaming-and-apache-hadoop/ > A real customer using this in produce is blogged here > http://blog.cloudera.com/blog/2015/03/how-edmunds-com-used-spark-streaming-to-build-a-near-real-time-dashboard/ > Please debate and let me know what I can do to make this happen. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-13992) Integrate SparkOnHBase into HBase
[ https://issues.apache.org/jira/browse/HBASE-13992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-13992: -- Fix Version/s: (was: 3.0.0-alpha-1) > Integrate SparkOnHBase into HBase > - > > Key: HBASE-13992 > URL: https://issues.apache.org/jira/browse/HBASE-13992 > Project: HBase > Issue Type: New Feature > Components: hbase-connectors, spark >Reporter: Theodore michael Malaska >Assignee: Theodore michael Malaska >Priority: Major > Fix For: connector-1.0.0 > > Attachments: HBASE-13992.10.patch, HBASE-13992.11.patch, > HBASE-13992.12.patch, HBASE-13992.5.patch, HBASE-13992.6.patch, > HBASE-13992.7.patch, HBASE-13992.8.patch, HBASE-13992.9.patch, > HBASE-13992.patch, HBASE-13992.patch.3, HBASE-13992.patch.4, > HBASE-13992.patch.5 > > > This Jira is to ask if SparkOnHBase can find a home in side HBase core. > Here is the github: > https://github.com/cloudera-labs/SparkOnHBase > I am the core author of this project and the license is Apache 2.0 > A blog explaining this project is here > http://blog.cloudera.com/blog/2014/12/new-in-cloudera-labs-sparkonhbase/ > A spark Streaming example is here > http://blog.cloudera.com/blog/2014/11/how-to-do-near-real-time-sessionization-with-spark-streaming-and-apache-hadoop/ > A real customer using this in produce is blogged here > http://blog.cloudera.com/blog/2015/03/how-edmunds-com-used-spark-streaming-to-build-a-near-real-time-dashboard/ > Please debate and let me know what I can do to make this happen. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HBASE-28844) Align the fixed issues in git and jira
[
https://issues.apache.org/jira/browse/HBASE-28844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885509#comment-17885509
]
Duo Zhang commented on HBASE-28844:
---
I've written a simple script to output the differences.
https://github.com/Apache9/hbase-release-audit/blob/main/audit-git-commit-jira-issue.py
This is the result
{noformat}
Commit to previous release but not in current release:
HBASE-12350
HBASE-17553
HBASE-18187
HBASE-18190
HBASE-18282
HBASE-18431
HBASE-18514
HBASE-18594
HBASE-18595
HBASE-18615
HBASE-18653
HBASE-18817
HBASE-18819
HBASE-18828
HBASE-18833
HBASE-18933
HBASE-19197
HBASE-19315
HBASE-19407
HBASE-19648
HBASE-19670
HBASE-19716
HBASE-19860
HBASE-19888
HBASE-20113
HBASE-20142
HBASE-20233
HBASE-20246
HBASE-20247
HBASE-20415
HBASE-20462
HBASE-20464
Issues in jira but not in git commits:
HBASE-13126
HBASE-13992
HBASE-14123
HBASE-14150
HBASE-14158
HBASE-14159
HBASE-14161
HBASE-14181
HBASE-14184
HBASE-14340
HBASE-14375
HBASE-14377
HBASE-14406
HBASE-14515
HBASE-14789
HBASE-14849
HBASE-15161
HBASE-15184
HBASE-15282
HBASE-15291
HBASE-15310
HBASE-15333
HBASE-15336
HBASE-15434
HBASE-15466
HBASE-15473
HBASE-15572
HBASE-15597
HBASE-15809
HBASE-16638
HBASE-16804
HBASE-16823
HBASE-17546
HBASE-17547
HBASE-17549
HBASE-17574
HBASE-17664
HBASE-17852
HBASE-17909
HBASE-17918
HBASE-17919
HBASE-17933
HBASE-18070
HBASE-18095
HBASE-18175
HBASE-18176
HBASE-18326
HBASE-18391
HBASE-18506
HBASE-18622
HBASE-18646
HBASE-18659
HBASE-19064
HBASE-19068
HBASE-19174
HBASE-19397
HBASE-19506
HBASE-19547
HBASE-20006
HBASE-20046
HBASE-20068
HBASE-20112
HBASE-20152
HBASE-20161
HBASE-20169
HBASE-20253
HBASE-20287
HBASE-20293
HBASE-20335
HBASE-20338
HBASE-20360
HBASE-20364
HBASE-20376
HBASE-20379
HBASE-20389
HBASE-20404
HBASE-20409
HBASE-20410
HBASE-20438
HBASE-20439
HBASE-20440
HBASE-20441
HBASE-20442
HBASE-20443
HBASE-20540
HBASE-20610
HBASE-20751
HBASE-20934
HBASE-21078
HBASE-21113
HBASE-21169
HBASE-21192
HBASE-21335
HBASE-21360
HBASE-21430
HBASE-21512
HBASE-21540
HBASE-21745
HBASE-21879
HBASE-22120
HBASE-22218
HBASE-22484
HBASE-22514
HBASE-22740
HBASE-22834
HBASE-22953
HBASE-22992
HBASE-23100
HBASE-23150
HBASE-23224
HBASE-23601
HBASE-23797
HBASE-23841
HBASE-24001
HBASE-24109
HBASE-24169
HBASE-24177
HBASE-24213
HBASE-24217
HBASE-24250
HBASE-24457
HBASE-24507
HBASE-24573
HBASE-25099
HBASE-25450
HBASE-25649
HBASE-25658
HBASE-25666
HBASE-25826
HBASE-25865
HBASE-25876
HBASE-25920
HBASE-26023
HBASE-26067
HBASE-26233
HBASE-26275
HBASE-26321
HBASE-26372
HBASE-26419
HBASE-26487
HBASE-26789
HBASE-26874
HBASE-26898
HBASE-26932
HBASE-26949
HBASE-27108
HBASE-27109
HBASE-27110
HBASE-28020
HBASE-28021
HBASE-28032
HBASE-28047
HBASE-28063
HBASE-28151
HBASE-28196
HBASE-28198
HBASE-28519
HBASE-28674
HBASE-28713
Issues in git commits but not in jira:
HBASE-13866
HBASE-14070
HBASE-14348
HBASE-15042
HBASE-17094
HBASE-17518
HBASE-17554
HBASE-18052
HBASE-18200
HBASE-18276
HBASE-18376
HBASE-18626
HBASE-18824
HBASE-19158
HBASE-19488
HBASE-19663
HBASE-19665
HBASE-19791
HBASE-20059
HBASE-20165
HBASE-20214
HBASE-20243
HBASE-20286
HBASE-20291
HBASE-20337
HBASE-20343
HBASE-20347
HBASE-20349
HBASE-20354
HBASE-20361
HBASE-20365
[jira] [Commented] (HBASE-28884) SFT's BrokenStoreFileCleaner may cause data loss
[ https://issues.apache.org/jira/browse/HBASE-28884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885508#comment-17885508 ] Duo Zhang commented on HBASE-28884: --- Seems I forgot to push the send button so the PR has already been merged. I think we should go with some fencing ways to solve the problem, instead of just adding a new check. Or if we think this is safe, at least we should add some comments to explain the reason, otherwise it may cause new confusing in the future. Thanks. > SFT's BrokenStoreFileCleaner may cause data loss > > > Key: HBASE-28884 > URL: https://issues.apache.org/jira/browse/HBASE-28884 > Project: HBase > Issue Type: Bug >Affects Versions: 2.6.0, 3.0.0-beta-1, 2.7.0, 2.5.10 >Reporter: Wellington Chevreuil >Assignee: Wellington Chevreuil >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0-beta-2 > > > When having this BrokenStoreFileCleaner enabled, one of our customers has run > into a data loss situation, probably due to a race condition between regions > getting moved out of the regionserver while the BrokenStoreFileCleaner was > checking this region's files eligibility for deletion. We have seen that the > file got deleted by the given region server, around the same time the region > got closed on this region server. I believe a race condition during region > close is possible here: > 1) In BrokenStoreFileCleaner, for each region online on the given RS, we get > the list of files in the store dirs, then iterate through it [1]; > 2) For each file listed, we perform several checks, including this one [2] > that checks if the file is "active" > The problem is, if the region for the file we are checking got closed between > point #1 and #2, by the time we check if the file is active in [2], the store > may have already been closed as part of the region closure, so this check > would consider the file as deletable. > One simple solution is to check if the store's region is still open before > proceeding with deleting the file. > [1] > https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/BrokenStoreFileCleaner.java#L99 > [2] > https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/BrokenStoreFileCleaner.java#L133 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28870) [hbase-thirdparty] Release hbase-thirdparty 4.1.9
[ https://issues.apache.org/jira/browse/HBASE-28870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28870. --- Resolution: Fixed All done. > [hbase-thirdparty] Release hbase-thirdparty 4.1.9 > - > > Key: HBASE-28870 > URL: https://issues.apache.org/jira/browse/HBASE-28870 > Project: HBase > Issue Type: Umbrella > Components: community, thirdparty >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28874) [hbase-thirdparty] Finish hbase-thirdparty 4.1.9 release
[ https://issues.apache.org/jira/browse/HBASE-28874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28874. --- Assignee: Duo Zhang Resolution: Fixed Done. > [hbase-thirdparty] Finish hbase-thirdparty 4.1.9 release > > > Key: HBASE-28874 > URL: https://issues.apache.org/jira/browse/HBASE-28874 > Project: HBase > Issue Type: Sub-task > Components: community, thirdparty >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > > Release the artifacts on repository.apache.org > Move the binaries from dist-dev to dist-release > Push tag 4.1.9RC0 as tag rel/4.1.9 > Release thirdparty-4.1.9 on JIRA > https://issues.apache.org/jira/projects/HBASE/versions/12355077 > Add release data on https://reporter.apache.org/addrelease.html?hbase > Send announcement email -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (HBASE-28874) [hbase-thirdparty] Finish hbase-thirdparty 4.1.9 release
[ https://issues.apache.org/jira/browse/HBASE-28874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885336#comment-17885336 ] Duo Zhang edited comment on HBASE-28874 at 9/27/24 12:03 PM: - Release the artifacts on repository.apache.org (/) Move the binaries from dist-dev to dist-release (/) Push tag 4.1.9RC0 as tag rel/4.1.9 (/) Release thirdparty-4.1.9 on JIRA https://issues.apache.org/jira/projects/HBASE/versions/12355077 (/) Add release data on https://reporter.apache.org/addrelease.html?hbase (/) Send announcement email (/) was (Author: apache9): Release the artifacts on repository.apache.org (/) Move the binaries from dist-dev to dist-release (/) Push tag 4.1.9RC0 as tag rel/4.1.9 (/) Release thirdparty-4.1.9 on JIRA https://issues.apache.org/jira/projects/HBASE/versions/12355077 (/) Add release data on https://reporter.apache.org/addrelease.html?hbase (/) Send announcement email > [hbase-thirdparty] Finish hbase-thirdparty 4.1.9 release > > > Key: HBASE-28874 > URL: https://issues.apache.org/jira/browse/HBASE-28874 > Project: HBase > Issue Type: Sub-task > Components: community, thirdparty >Reporter: Duo Zhang >Priority: Major > > Release the artifacts on repository.apache.org > Move the binaries from dist-dev to dist-release > Push tag 4.1.9RC0 as tag rel/4.1.9 > Release thirdparty-4.1.9 on JIRA > https://issues.apache.org/jira/projects/HBASE/versions/12355077 > Add release data on https://reporter.apache.org/addrelease.html?hbase > Send announcement email -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (HBASE-28874) [hbase-thirdparty] Finish hbase-thirdparty 4.1.9 release
[ https://issues.apache.org/jira/browse/HBASE-28874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885336#comment-17885336 ] Duo Zhang edited comment on HBASE-28874 at 9/27/24 11:54 AM: - Release the artifacts on repository.apache.org (/) Move the binaries from dist-dev to dist-release (/) Push tag 4.1.9RC0 as tag rel/4.1.9 (/) Release thirdparty-4.1.9 on JIRA https://issues.apache.org/jira/projects/HBASE/versions/12355077 (/) Add release data on https://reporter.apache.org/addrelease.html?hbase Send announcement email was (Author: apache9): Release the artifacts on repository.apache.org (/) Move the binaries from dist-dev to dist-release (/) Push tag 4.1.9RC0 as tag rel/4.1.9 Release thirdparty-4.1.9 on JIRA https://issues.apache.org/jira/projects/HBASE/versions/12355077 Add release data on https://reporter.apache.org/addrelease.html?hbase Send announcement email > [hbase-thirdparty] Finish hbase-thirdparty 4.1.9 release > > > Key: HBASE-28874 > URL: https://issues.apache.org/jira/browse/HBASE-28874 > Project: HBase > Issue Type: Sub-task > Components: community, thirdparty >Reporter: Duo Zhang >Priority: Major > > Release the artifacts on repository.apache.org > Move the binaries from dist-dev to dist-release > Push tag 4.1.9RC0 as tag rel/4.1.9 > Release thirdparty-4.1.9 on JIRA > https://issues.apache.org/jira/projects/HBASE/versions/12355077 > Add release data on https://reporter.apache.org/addrelease.html?hbase > Send announcement email -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-28794) [hbase-thirdparty] Enable infra automation: autolink to Jira and 'pull-request-available' label
[
https://issues.apache.org/jira/browse/HBASE-28794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-28794:
--
Fix Version/s: thirdparty-4.1.9
(was: thirdparty-4.1.10)
> [hbase-thirdparty] Enable infra automation: autolink to Jira and
> 'pull-request-available' label
> ---
>
> Key: HBASE-28794
> URL: https://issues.apache.org/jira/browse/HBASE-28794
> Project: HBase
> Issue Type: Task
> Components: community
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Minor
> Fix For: thirdparty-4.1.9
>
> Attachments: Screenshot 2024-08-21 at 7.38.46 PM.png, Screenshot
> 2024-08-21 at 7.39.25 PM.png
>
>
> Patterns like HBASE-28786 will be clickable, so it's easier to go to the Jira
> page.
> {{.asf.yaml}} provides an option to do this via config: See
> [https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-AutolinksforJira]
> Even without manual configuring this already works for hbase somehow. See
> [https://github.com/apache/hbase/commits/master/]
> Maybe configured at repo level in INFRA?
> But same does not work for hbase-connectors and other repos. Will use this
> config to fix the issue.
> Also will enable label feature for 'pull-request-available', same as hbase
> main repo: HBASE-28325
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (HBASE-28874) [hbase-thirdparty] Finish hbase-thirdparty 4.1.9 release
[ https://issues.apache.org/jira/browse/HBASE-28874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885336#comment-17885336 ] Duo Zhang edited comment on HBASE-28874 at 9/27/24 11:58 AM: - Release the artifacts on repository.apache.org (/) Move the binaries from dist-dev to dist-release (/) Push tag 4.1.9RC0 as tag rel/4.1.9 (/) Release thirdparty-4.1.9 on JIRA https://issues.apache.org/jira/projects/HBASE/versions/12355077 (/) Add release data on https://reporter.apache.org/addrelease.html?hbase (/) Send announcement email was (Author: apache9): Release the artifacts on repository.apache.org (/) Move the binaries from dist-dev to dist-release (/) Push tag 4.1.9RC0 as tag rel/4.1.9 (/) Release thirdparty-4.1.9 on JIRA https://issues.apache.org/jira/projects/HBASE/versions/12355077 (/) Add release data on https://reporter.apache.org/addrelease.html?hbase Send announcement email > [hbase-thirdparty] Finish hbase-thirdparty 4.1.9 release > > > Key: HBASE-28874 > URL: https://issues.apache.org/jira/browse/HBASE-28874 > Project: HBase > Issue Type: Sub-task > Components: community, thirdparty >Reporter: Duo Zhang >Priority: Major > > Release the artifacts on repository.apache.org > Move the binaries from dist-dev to dist-release > Push tag 4.1.9RC0 as tag rel/4.1.9 > Release thirdparty-4.1.9 on JIRA > https://issues.apache.org/jira/projects/HBASE/versions/12355077 > Add release data on https://reporter.apache.org/addrelease.html?hbase > Send announcement email -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28873) [hbase-thirdparty] Put up hbase-thirdparty-4.1.9RC0
[ https://issues.apache.org/jira/browse/HBASE-28873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28873. --- Resolution: Fixed Done. > [hbase-thirdparty] Put up hbase-thirdparty-4.1.9RC0 > --- > > Key: HBASE-28873 > URL: https://issues.apache.org/jira/browse/HBASE-28873 > Project: HBase > Issue Type: Sub-task > Components: community, thirdparty >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-28794) [hbase-thirdparty] Enable infra automation: autolink to Jira and 'pull-request-available' label
[
https://issues.apache.org/jira/browse/HBASE-28794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-28794:
--
Fix Version/s: thirdparty-4.1.10
(was: thirdparty-4.1.9)
> [hbase-thirdparty] Enable infra automation: autolink to Jira and
> 'pull-request-available' label
> ---
>
> Key: HBASE-28794
> URL: https://issues.apache.org/jira/browse/HBASE-28794
> Project: HBase
> Issue Type: Task
> Components: community
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Minor
> Fix For: thirdparty-4.1.10
>
> Attachments: Screenshot 2024-08-21 at 7.38.46 PM.png, Screenshot
> 2024-08-21 at 7.39.25 PM.png
>
>
> Patterns like HBASE-28786 will be clickable, so it's easier to go to the Jira
> page.
> {{.asf.yaml}} provides an option to do this via config: See
> [https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-AutolinksforJira]
> Even without manual configuring this already works for hbase somehow. See
> [https://github.com/apache/hbase/commits/master/]
> Maybe configured at repo level in INFRA?
> But same does not work for hbase-connectors and other repos. Will use this
> config to fix the issue.
> Also will enable label feature for 'pull-request-available', same as hbase
> main repo: HBASE-28325
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-28874) [hbase-thirdparty] Finish hbase-thirdparty 4.1.9 release
[ https://issues.apache.org/jira/browse/HBASE-28874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885336#comment-17885336 ] Duo Zhang commented on HBASE-28874: --- Release the artifacts on repository.apache.org (/) Move the binaries from dist-dev to dist-release (/) Push tag 4.1.9RC0 as tag rel/4.1.9 Release thirdparty-4.1.9 on JIRA https://issues.apache.org/jira/projects/HBASE/versions/12355077 Add release data on https://reporter.apache.org/addrelease.html?hbase Send announcement email > [hbase-thirdparty] Finish hbase-thirdparty 4.1.9 release > > > Key: HBASE-28874 > URL: https://issues.apache.org/jira/browse/HBASE-28874 > Project: HBase > Issue Type: Sub-task > Components: community, thirdparty >Reporter: Duo Zhang >Priority: Major > > Release the artifacts on repository.apache.org > Move the binaries from dist-dev to dist-release > Push tag 4.1.9RC0 as tag rel/4.1.9 > Release thirdparty-4.1.9 on JIRA > https://issues.apache.org/jira/projects/HBASE/versions/12355077 > Add release data on https://reporter.apache.org/addrelease.html?hbase > Send announcement email -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HBASE-28889) Ignored flags in Yetus nightly runs
[
https://issues.apache.org/jira/browse/HBASE-28889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885330#comment-17885330
]
Duo Zhang commented on HBASE-28889:
---
We only need these flags when running general checks, so when running JDK
specific tests, we will get this -0.
But I do not think this is a big problem as it does not fail the build...
> Ignored flags in Yetus nightly runs
> ---
>
> Key: HBASE-28889
> URL: https://issues.apache.org/jira/browse/HBASE-28889
> Project: HBase
> Issue Type: Bug
> Components: test
>Reporter: Istvan Toth
>Priority: Minor
>
> {noformat}
> 22:08:23 | -0 | yetus | 0m 6s | Unprocessed flag(s):
> 22:08:23 | ||| --blanks-tabs-ignore-file
> 22:08:23 | ||| --blanks-eol-ignore-file
> 22:08:23 | ||| --author-ignore-list
> {noformat}
> The flags seem to be still present in the Yetus source code.
> Maybe the modules are no longer getting activated ?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (HBASE-28060) Region server getting crashed during write - A fatal error has been detected by the Java Runtime Environment
[
https://issues.apache.org/jira/browse/HBASE-28060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang reopened HBASE-28060:
---
> Region server getting crashed during write - A fatal error has been detected
> by the Java Runtime Environment
>
>
> Key: HBASE-28060
> URL: https://issues.apache.org/jira/browse/HBASE-28060
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 2.4.14
>Reporter: Pankaj Kumar
>Priority: Critical
> Attachments: hs_err_pid_1772127_84.log
>
>
> In our production environment, Region server JVM is getting crashed randomly
> with the following error logs.
> {code:java}
> Stack: [0xfffdd32d8000,0xfffdd34d8000], sp=0xfffdd34d6000, free
> space=2040k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native
> code)
> v ~StubRoutines::jshort_disjoint_arraycopy
> J 98497 C2
> org.apache.hadoop.hbase.io.ByteBufferListOutputStream.write(Ljava/nio/ByteBuffer;II)V
> (53 bytes) @ 0x8cc9a154 [0x8cc9a040+0x114]
> C [ld-linux-aarch64.so.1+0x40018] _rtld_global+0x0
> [error occurred during error reporting (printing native stack), id 0xb]
> {code}
>
> We are using HBase 2.4.14.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-28060) Region server getting crashed during write - A fatal error has been detected by the Java Runtime Environment
[
https://issues.apache.org/jira/browse/HBASE-28060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-28060.
---
Resolution: Duplicate
> Region server getting crashed during write - A fatal error has been detected
> by the Java Runtime Environment
>
>
> Key: HBASE-28060
> URL: https://issues.apache.org/jira/browse/HBASE-28060
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 2.4.14
>Reporter: Pankaj Kumar
>Priority: Critical
> Attachments: hs_err_pid_1772127_84.log
>
>
> In our production environment, Region server JVM is getting crashed randomly
> with the following error logs.
> {code:java}
> Stack: [0xfffdd32d8000,0xfffdd34d8000], sp=0xfffdd34d6000, free
> space=2040k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native
> code)
> v ~StubRoutines::jshort_disjoint_arraycopy
> J 98497 C2
> org.apache.hadoop.hbase.io.ByteBufferListOutputStream.write(Ljava/nio/ByteBuffer;II)V
> (53 bytes) @ 0x8cc9a154 [0x8cc9a040+0x114]
> C [ld-linux-aarch64.so.1+0x40018] _rtld_global+0x0
> [error occurred during error reporting (printing native stack), id 0xb]
> {code}
>
> We are using HBase 2.4.14.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (HBASE-26024) Region server JVM Crash - A fatal error has been detected by the Java Runtime Environment
[ https://issues.apache.org/jira/browse/HBASE-26024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reopened HBASE-26024: --- > Region server JVM Crash - A fatal error has been detected by the Java Runtime > Environment > - > > Key: HBASE-26024 > URL: https://issues.apache.org/jira/browse/HBASE-26024 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.9 >Reporter: Mohamed Mohideen Meeran >Priority: Major > Attachments: error.log > > > Our production Region servers JVM crashed with the following error logs. > > Register to memory mapping: > RAX=0x2eea8f42 is an unknown value > RBX=0x7f1f8c7900d6 is an unknown value > RCX=0x0021 is an unknown value > RDX=0x is an unknown value > RSP=0x7f1fe3092200 is pointing into the stack for thread: > 0x7f29775fb000 > RBP=0x7f1fe3092200 is pointing into the stack for thread: > 0x7f29775fb000 > RSI=0x7f1f8c7900cc is an unknown value > RDI=0x2eea8f38 is an unknown value > R8 =0x7f28e14a3a38 is an oop > java.nio.DirectByteBuffer > - klass: 'java/nio/DirectByteBuffer' > R9 =0x7f1f8c790094 is an unknown value > R10=0x7f2965053400 is at begin+0 in a stub > StubRoutines::unsafe_arraycopy [0x7f2965053400, 0x7f296505343b[ (59 > bytes) > R11=0x7f28e14a3a38 is an oop > java.nio.DirectByteBuffer > - klass: 'java/nio/DirectByteBuffer' > R12= > [error occurred during error reporting (printing register info), id 0xb] > > Stack: [0x7f1fe2f93000,0x7f1fe3094000], sp=0x7f1fe3092200, free > space=1020k > Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native > code) > v ~StubRoutines::jshort_disjoint_arraycopy > J 18388 C2 > org.apache.hadoop.hbase.io.ByteBufferListOutputStream.write(Ljava/nio/ByteBuffer;II)V > (53 bytes) @ 0x7f2967fa0ea2 [0x7f2967fa0d40+0x162] > J 11722 C2 > org.apache.hadoop.hbase.util.ByteBufferUtils.copyBufferToStream(Ljava/io/OutputStream;Ljava/nio/ByteBuffer;II)V > (75 bytes) @ 0x7f29670aa0fc [0x7f29670a9fa0+0x15c] > J 13251 C2 > org.apache.hadoop.hbase.ByteBufferKeyValue.write(Ljava/io/OutputStream;Z)I > (21 bytes) @ 0x7f2965cbe87c [0x7f2965cbe820+0x5c] > J 8703 C2 > org.apache.hadoop.hbase.KeyValueUtil.oswrite(Lorg/apache/hadoop/hbase/Cell;Ljava/io/OutputStream;Z)I > (259 bytes) @ 0x7f296684a2d4 [0x7f296684a140+0x194] > J 15474 C2 > org.apache.hadoop.hbase.ipc.CellBlockBuilder.buildCellBlockStream(Lorg/apache/hadoop/hbase/codec/Codec;Lorg/apache/hadoop/io/compress/CompressionCodec;Lorg/apache/hadoop/hbase/CellScanner;Lorg/apache/hadoop/hbase/io/ByteBufferPool;)Lorg/apache/hadoop/hbase/io/ByteBufferListOutputStream; > (75 bytes) @ 0x7f29675f9dc8 [0x7f29675f7c80+0x2148] > J 14260 C2 > org.apache.hadoop.hbase.ipc.ServerCall.setResponse(Lorg/apache/hbase/thirdparty/com/google/protobuf/Message;Lorg/apache/hadoop/hbase/CellScanner;Ljava/lang/Throwable;Ljava/lang/String;)V > (408 bytes) @ 0x7f29678ad11c [0x7f29678acec0+0x25c] > J 14732 C2 org.apache.hadoop.hbase.ipc.CallRunner.run()V (1376 bytes) @ > 0x7f296797f690 [0x7f296797e6a0+0xff0] > J 14293 C2 > org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(Lorg/apache/hadoop/hbase/ipc/CallRunner;)V > (268 bytes) @ 0x7f29667b7464 [0x7f29667b72e0+0x184] > J 17796% C1 org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run()V (72 bytes) > @ 0x7f2967c9cbe4 [0x7f2967c9caa0+0x144] > v ~StubRoutines::call_stub > V [libjvm.so+0x65ebbb] JavaCalls::call_helper(JavaValue*, methodHandle*, > JavaCallArguments*, Thread*)+0x108b > V [libjvm.so+0x65ffd7] JavaCalls::call_virtual(JavaValue*, KlassHandle, > Symbol*, Symbol*, JavaCallArguments*, Thread*)+0x2f7 > V [libjvm.so+0x660497] JavaCalls::call_virtual(JavaValue*, Handle, > KlassHandle, Symbol*, Symbol*, Thread*)+0x47 > V [libjvm.so+0x6ada71] thread_entry(JavaThread*, Thread*)+0x91 > V [libjvm.so+0x9f24f1] JavaThread::thread_main_inner()+0xf1 > V [libjvm.so+0x9f26d8] JavaThread::run()+0x1b8 > V [libjvm.so+0x8af502] java_start(Thread*)+0x122 > C [libpthread.so.0+0x7dc5] start_thread+0xc5 > > we used the workaround by switching *hbase.rpc.server.impl* back to > SimpleRpcServer as mentioned in the following JIRA > https://issues.apache.org/jira/browse/HBASE-22539?focusedCommentId=16855688&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16855688 > Also, attached the error logs during JVM crash. Any help? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-28060) Region server getting crashed during write - A fatal error has been detected by the Java Runtime Environment
[
https://issues.apache.org/jira/browse/HBASE-28060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-28060:
--
Fix Version/s: (was: 2.7.0)
(was: 3.0.0-beta-2)
(was: 2.6.1)
(was: 2.5.11)
> Region server getting crashed during write - A fatal error has been detected
> by the Java Runtime Environment
>
>
> Key: HBASE-28060
> URL: https://issues.apache.org/jira/browse/HBASE-28060
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 2.4.14
>Reporter: Pankaj Kumar
>Priority: Critical
> Attachments: hs_err_pid_1772127_84.log
>
>
> In our production environment, Region server JVM is getting crashed randomly
> with the following error logs.
> {code:java}
> Stack: [0xfffdd32d8000,0xfffdd34d8000], sp=0xfffdd34d6000, free
> space=2040k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native
> code)
> v ~StubRoutines::jshort_disjoint_arraycopy
> J 98497 C2
> org.apache.hadoop.hbase.io.ByteBufferListOutputStream.write(Ljava/nio/ByteBuffer;II)V
> (53 bytes) @ 0x8cc9a154 [0x8cc9a040+0x114]
> C [ld-linux-aarch64.so.1+0x40018] _rtld_global+0x0
> [error occurred during error reporting (printing native stack), id 0xb]
> {code}
>
> We are using HBase 2.4.14.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-26024) Region server JVM Crash - A fatal error has been detected by the Java Runtime Environment
[ https://issues.apache.org/jira/browse/HBASE-26024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-26024. --- Resolution: Duplicate > Region server JVM Crash - A fatal error has been detected by the Java Runtime > Environment > - > > Key: HBASE-26024 > URL: https://issues.apache.org/jira/browse/HBASE-26024 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.9 >Reporter: Mohamed Mohideen Meeran >Priority: Major > Attachments: error.log > > > Our production Region servers JVM crashed with the following error logs. > > Register to memory mapping: > RAX=0x2eea8f42 is an unknown value > RBX=0x7f1f8c7900d6 is an unknown value > RCX=0x0021 is an unknown value > RDX=0x is an unknown value > RSP=0x7f1fe3092200 is pointing into the stack for thread: > 0x7f29775fb000 > RBP=0x7f1fe3092200 is pointing into the stack for thread: > 0x7f29775fb000 > RSI=0x7f1f8c7900cc is an unknown value > RDI=0x2eea8f38 is an unknown value > R8 =0x7f28e14a3a38 is an oop > java.nio.DirectByteBuffer > - klass: 'java/nio/DirectByteBuffer' > R9 =0x7f1f8c790094 is an unknown value > R10=0x7f2965053400 is at begin+0 in a stub > StubRoutines::unsafe_arraycopy [0x7f2965053400, 0x7f296505343b[ (59 > bytes) > R11=0x7f28e14a3a38 is an oop > java.nio.DirectByteBuffer > - klass: 'java/nio/DirectByteBuffer' > R12= > [error occurred during error reporting (printing register info), id 0xb] > > Stack: [0x7f1fe2f93000,0x7f1fe3094000], sp=0x7f1fe3092200, free > space=1020k > Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native > code) > v ~StubRoutines::jshort_disjoint_arraycopy > J 18388 C2 > org.apache.hadoop.hbase.io.ByteBufferListOutputStream.write(Ljava/nio/ByteBuffer;II)V > (53 bytes) @ 0x7f2967fa0ea2 [0x7f2967fa0d40+0x162] > J 11722 C2 > org.apache.hadoop.hbase.util.ByteBufferUtils.copyBufferToStream(Ljava/io/OutputStream;Ljava/nio/ByteBuffer;II)V > (75 bytes) @ 0x7f29670aa0fc [0x7f29670a9fa0+0x15c] > J 13251 C2 > org.apache.hadoop.hbase.ByteBufferKeyValue.write(Ljava/io/OutputStream;Z)I > (21 bytes) @ 0x7f2965cbe87c [0x7f2965cbe820+0x5c] > J 8703 C2 > org.apache.hadoop.hbase.KeyValueUtil.oswrite(Lorg/apache/hadoop/hbase/Cell;Ljava/io/OutputStream;Z)I > (259 bytes) @ 0x7f296684a2d4 [0x7f296684a140+0x194] > J 15474 C2 > org.apache.hadoop.hbase.ipc.CellBlockBuilder.buildCellBlockStream(Lorg/apache/hadoop/hbase/codec/Codec;Lorg/apache/hadoop/io/compress/CompressionCodec;Lorg/apache/hadoop/hbase/CellScanner;Lorg/apache/hadoop/hbase/io/ByteBufferPool;)Lorg/apache/hadoop/hbase/io/ByteBufferListOutputStream; > (75 bytes) @ 0x7f29675f9dc8 [0x7f29675f7c80+0x2148] > J 14260 C2 > org.apache.hadoop.hbase.ipc.ServerCall.setResponse(Lorg/apache/hbase/thirdparty/com/google/protobuf/Message;Lorg/apache/hadoop/hbase/CellScanner;Ljava/lang/Throwable;Ljava/lang/String;)V > (408 bytes) @ 0x7f29678ad11c [0x7f29678acec0+0x25c] > J 14732 C2 org.apache.hadoop.hbase.ipc.CallRunner.run()V (1376 bytes) @ > 0x7f296797f690 [0x7f296797e6a0+0xff0] > J 14293 C2 > org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(Lorg/apache/hadoop/hbase/ipc/CallRunner;)V > (268 bytes) @ 0x7f29667b7464 [0x7f29667b72e0+0x184] > J 17796% C1 org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run()V (72 bytes) > @ 0x7f2967c9cbe4 [0x7f2967c9caa0+0x144] > v ~StubRoutines::call_stub > V [libjvm.so+0x65ebbb] JavaCalls::call_helper(JavaValue*, methodHandle*, > JavaCallArguments*, Thread*)+0x108b > V [libjvm.so+0x65ffd7] JavaCalls::call_virtual(JavaValue*, KlassHandle, > Symbol*, Symbol*, JavaCallArguments*, Thread*)+0x2f7 > V [libjvm.so+0x660497] JavaCalls::call_virtual(JavaValue*, Handle, > KlassHandle, Symbol*, Symbol*, Thread*)+0x47 > V [libjvm.so+0x6ada71] thread_entry(JavaThread*, Thread*)+0x91 > V [libjvm.so+0x9f24f1] JavaThread::thread_main_inner()+0xf1 > V [libjvm.so+0x9f26d8] JavaThread::run()+0x1b8 > V [libjvm.so+0x8af502] java_start(Thread*)+0x122 > C [libpthread.so.0+0x7dc5] start_thread+0xc5 > > we used the workaround by switching *hbase.rpc.server.impl* back to > SimpleRpcServer as mentioned in the following JIRA > https://issues.apache.org/jira/browse/HBASE-22539?focusedCommentId=16855688&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16855688 > Also, attached the error logs during JVM crash. Any help? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-26024) Region server JVM Crash - A fatal error has been detected by the Java Runtime Environment
[ https://issues.apache.org/jira/browse/HBASE-26024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-26024: -- Fix Version/s: (was: 2.7.0) (was: 3.0.0-beta-2) (was: 2.6.1) (was: 2.5.11) > Region server JVM Crash - A fatal error has been detected by the Java Runtime > Environment > - > > Key: HBASE-26024 > URL: https://issues.apache.org/jira/browse/HBASE-26024 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.9 >Reporter: Mohamed Mohideen Meeran >Priority: Major > Attachments: error.log > > > Our production Region servers JVM crashed with the following error logs. > > Register to memory mapping: > RAX=0x2eea8f42 is an unknown value > RBX=0x7f1f8c7900d6 is an unknown value > RCX=0x0021 is an unknown value > RDX=0x is an unknown value > RSP=0x7f1fe3092200 is pointing into the stack for thread: > 0x7f29775fb000 > RBP=0x7f1fe3092200 is pointing into the stack for thread: > 0x7f29775fb000 > RSI=0x7f1f8c7900cc is an unknown value > RDI=0x2eea8f38 is an unknown value > R8 =0x7f28e14a3a38 is an oop > java.nio.DirectByteBuffer > - klass: 'java/nio/DirectByteBuffer' > R9 =0x7f1f8c790094 is an unknown value > R10=0x7f2965053400 is at begin+0 in a stub > StubRoutines::unsafe_arraycopy [0x7f2965053400, 0x7f296505343b[ (59 > bytes) > R11=0x7f28e14a3a38 is an oop > java.nio.DirectByteBuffer > - klass: 'java/nio/DirectByteBuffer' > R12= > [error occurred during error reporting (printing register info), id 0xb] > > Stack: [0x7f1fe2f93000,0x7f1fe3094000], sp=0x7f1fe3092200, free > space=1020k > Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native > code) > v ~StubRoutines::jshort_disjoint_arraycopy > J 18388 C2 > org.apache.hadoop.hbase.io.ByteBufferListOutputStream.write(Ljava/nio/ByteBuffer;II)V > (53 bytes) @ 0x7f2967fa0ea2 [0x7f2967fa0d40+0x162] > J 11722 C2 > org.apache.hadoop.hbase.util.ByteBufferUtils.copyBufferToStream(Ljava/io/OutputStream;Ljava/nio/ByteBuffer;II)V > (75 bytes) @ 0x7f29670aa0fc [0x7f29670a9fa0+0x15c] > J 13251 C2 > org.apache.hadoop.hbase.ByteBufferKeyValue.write(Ljava/io/OutputStream;Z)I > (21 bytes) @ 0x7f2965cbe87c [0x7f2965cbe820+0x5c] > J 8703 C2 > org.apache.hadoop.hbase.KeyValueUtil.oswrite(Lorg/apache/hadoop/hbase/Cell;Ljava/io/OutputStream;Z)I > (259 bytes) @ 0x7f296684a2d4 [0x7f296684a140+0x194] > J 15474 C2 > org.apache.hadoop.hbase.ipc.CellBlockBuilder.buildCellBlockStream(Lorg/apache/hadoop/hbase/codec/Codec;Lorg/apache/hadoop/io/compress/CompressionCodec;Lorg/apache/hadoop/hbase/CellScanner;Lorg/apache/hadoop/hbase/io/ByteBufferPool;)Lorg/apache/hadoop/hbase/io/ByteBufferListOutputStream; > (75 bytes) @ 0x7f29675f9dc8 [0x7f29675f7c80+0x2148] > J 14260 C2 > org.apache.hadoop.hbase.ipc.ServerCall.setResponse(Lorg/apache/hbase/thirdparty/com/google/protobuf/Message;Lorg/apache/hadoop/hbase/CellScanner;Ljava/lang/Throwable;Ljava/lang/String;)V > (408 bytes) @ 0x7f29678ad11c [0x7f29678acec0+0x25c] > J 14732 C2 org.apache.hadoop.hbase.ipc.CallRunner.run()V (1376 bytes) @ > 0x7f296797f690 [0x7f296797e6a0+0xff0] > J 14293 C2 > org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(Lorg/apache/hadoop/hbase/ipc/CallRunner;)V > (268 bytes) @ 0x7f29667b7464 [0x7f29667b72e0+0x184] > J 17796% C1 org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run()V (72 bytes) > @ 0x7f2967c9cbe4 [0x7f2967c9caa0+0x144] > v ~StubRoutines::call_stub > V [libjvm.so+0x65ebbb] JavaCalls::call_helper(JavaValue*, methodHandle*, > JavaCallArguments*, Thread*)+0x108b > V [libjvm.so+0x65ffd7] JavaCalls::call_virtual(JavaValue*, KlassHandle, > Symbol*, Symbol*, JavaCallArguments*, Thread*)+0x2f7 > V [libjvm.so+0x660497] JavaCalls::call_virtual(JavaValue*, Handle, > KlassHandle, Symbol*, Symbol*, Thread*)+0x47 > V [libjvm.so+0x6ada71] thread_entry(JavaThread*, Thread*)+0x91 > V [libjvm.so+0x9f24f1] JavaThread::thread_main_inner()+0xf1 > V [libjvm.so+0x9f26d8] JavaThread::run()+0x1b8 > V [libjvm.so+0x8af502] java_start(Thread*)+0x122 > C [libpthread.so.0+0x7dc5] start_thread+0xc5 > > we used the workaround by switching *hbase.rpc.server.impl* back to > SimpleRpcServer as mentioned in the following JIRA > https://issues.apache.org/jira/browse/HBASE-22539?focusedCommentId=16855688&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16855688 > Also, attached the error logs during JVM crash. Any help? -- This message was sent by Atlassian Jira (v8.20.10#820010)
