[jira] [Updated] (HBASE-28904) Supports enabling storage policy in the data copying scenario of bulkload
[ https://issues.apache.org/jira/browse/HBASE-28904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He updated HBASE-28904: Summary: Supports enabling storage policy in the data copying scenario of bulkload (was: Supports enabling storage policy in the data copying scenario of bulkload.) > Supports enabling storage policy in the data copying scenario of bulkload > - > > Key: HBASE-28904 > URL: https://issues.apache.org/jira/browse/HBASE-28904 > Project: HBase > Issue Type: Improvement >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Major > > In the current HBase bulkload scenario, if a tiered storage policy is set for > the column family of a table and the operation involves different HDFS > clusters, the storage policy for the data imported via bulkload will not take > effect. We hope to enable the automatic activation of tiered storage policy > in the data copying scenario of bulkload. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28904) Supports enabling storage policy in the data copying scenario of bulkload.
Liangjun He created HBASE-28904: --- Summary: Supports enabling storage policy in the data copying scenario of bulkload. Key: HBASE-28904 URL: https://issues.apache.org/jira/browse/HBASE-28904 Project: HBase Issue Type: Improvement Reporter: Liangjun He Assignee: Liangjun He In the current HBase bulkload scenario, if a tiered storage policy is set for the column family of a table and the operation involves different HDFS clusters, the storage policy for the data imported via bulkload will not take effect. We hope to enable the automatic activation of tiered storage policy in the data copying scenario of bulkload. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28648) Change the deprecation cycle for RegionObserver.postInstantiateDeleteTracker
[ https://issues.apache.org/jira/browse/HBASE-28648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He resolved HBASE-28648. - Fix Version/s: 3.0.0-beta-2 Resolution: Fixed > Change the deprecation cycle for RegionObserver.postInstantiateDeleteTracker > > > Key: HBASE-28648 > URL: https://issues.apache.org/jira/browse/HBASE-28648 > Project: HBase > Issue Type: Sub-task > Components: Coprocessors >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0-beta-2 > > > Visibility label feature still use this method so it can not be removed in > 3.0.0. Should change the deprecation cycle javadoc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (HBASE-28648) Change the deprecation cycle for RegionObserver.postInstantiateDeleteTracker
[ https://issues.apache.org/jira/browse/HBASE-28648 ] Liangjun He deleted comment on HBASE-28648: - was (Author: heliangjun): OK, Sir > Change the deprecation cycle for RegionObserver.postInstantiateDeleteTracker > > > Key: HBASE-28648 > URL: https://issues.apache.org/jira/browse/HBASE-28648 > Project: HBase > Issue Type: Sub-task > Components: Coprocessors >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > Labels: pull-request-available > > Visibility label feature still use this method so it can not be removed in > 3.0.0. Should change the deprecation cycle javadoc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HBASE-28648) Change the deprecation cycle for RegionObserver.postInstantiateDeleteTracker
[ https://issues.apache.org/jira/browse/HBASE-28648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870363#comment-17870363 ] Liangjun He commented on HBASE-28648: - OK, Sir > Change the deprecation cycle for RegionObserver.postInstantiateDeleteTracker > > > Key: HBASE-28648 > URL: https://issues.apache.org/jira/browse/HBASE-28648 > Project: HBase > Issue Type: Sub-task > Components: Coprocessors >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > > Visibility label feature still use this method so it can not be removed in > 3.0.0. Should change the deprecation cycle javadoc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HBASE-28648) Change the deprecation cycle for RegionObserver.postInstantiateDeleteTracker
[ https://issues.apache.org/jira/browse/HBASE-28648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870306#comment-17870306 ] Liangjun He commented on HBASE-28648: - [~zhangduo] Should we remove this method in version 4.0.0, or instead, remove the deprecation flag from the method? > Change the deprecation cycle for RegionObserver.postInstantiateDeleteTracker > > > Key: HBASE-28648 > URL: https://issues.apache.org/jira/browse/HBASE-28648 > Project: HBase > Issue Type: Sub-task > Components: Coprocessors >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > > Visibility label feature still use this method so it can not be removed in > 3.0.0. Should change the deprecation cycle javadoc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HBASE-28648) Change the deprecation cycle for RegionObserver.postInstantiateDeleteTracker
[ https://issues.apache.org/jira/browse/HBASE-28648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He reassigned HBASE-28648: --- Assignee: Liangjun He > Change the deprecation cycle for RegionObserver.postInstantiateDeleteTracker > > > Key: HBASE-28648 > URL: https://issues.apache.org/jira/browse/HBASE-28648 > Project: HBase > Issue Type: Sub-task > Components: Coprocessors >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > > Visibility label feature still use this method so it can not be removed in > 3.0.0. Should change the deprecation cycle javadoc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28389) HBase backup yarn queue parameter ignored
[
https://issues.apache.org/jira/browse/HBASE-28389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Liangjun He resolved HBASE-28389.
-
Fix Version/s: 2.7.0
3.0.0-beta-2
2.6.1
Resolution: Fixed
> HBase backup yarn queue parameter ignored
> -
>
> Key: HBASE-28389
> URL: https://issues.apache.org/jira/browse/HBASE-28389
> Project: HBase
> Issue Type: Bug
> Components: backup&restore
>Affects Versions: 2.6.0
> Environment: HBase branch-2.6
>Reporter: Dieter De Paepe
>Assignee: Liangjun He
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1
>
>
> It seems the parameter to specify the yarn queue for HBase backup (`-q`) is
> ignored:
> {code:java}
> hbase backup create full hdfs:///tmp/backups/hbasetest/hbase -q hbase-backup
> {code}
> gets executed on the "default" queue.
> Setting the queue through the configuration does work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-28389) HBase backup yarn queue parameter ignored
[
https://issues.apache.org/jira/browse/HBASE-28389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Liangjun He updated HBASE-28389:
Summary: HBase backup yarn queue parameter ignored (was: Hbase backup yarn
queue parameter ignored)
> HBase backup yarn queue parameter ignored
> -
>
> Key: HBASE-28389
> URL: https://issues.apache.org/jira/browse/HBASE-28389
> Project: HBase
> Issue Type: Bug
> Components: backup&restore
>Affects Versions: 2.6.0
> Environment: HBase branch-2.6
>Reporter: Dieter De Paepe
>Assignee: Liangjun He
>Priority: Major
>
> It seems the parameter to specify the yarn queue for HBase backup (`-q`) is
> ignored:
> {code:java}
> hbase backup create full hdfs:///tmp/backups/hbasetest/hbase -q hbase-backup
> {code}
> gets executed on the "default" queue.
> Setting the queue through the configuration does work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (HBASE-28389) Hbase backup yarn queue parameter ignored
[
https://issues.apache.org/jira/browse/HBASE-28389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Liangjun He reassigned HBASE-28389:
---
Assignee: Liangjun He
> Hbase backup yarn queue parameter ignored
> -
>
> Key: HBASE-28389
> URL: https://issues.apache.org/jira/browse/HBASE-28389
> Project: HBase
> Issue Type: Bug
> Components: backup&restore
>Affects Versions: 2.6.0
> Environment: HBase branch-2.6
>Reporter: Dieter De Paepe
>Assignee: Liangjun He
>Priority: Major
>
> It seems the parameter to specify the yarn queue for HBase backup (`-q`) is
> ignored:
> {code:java}
> hbase backup create full hdfs:///tmp/backups/hbasetest/hbase -q hbase-backup
> {code}
> gets executed on the "default" queue.
> Setting the queue through the configuration does work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-28734) Improve HBase shell snapshot command Doc with TTL option
[
https://issues.apache.org/jira/browse/HBASE-28734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Liangjun He resolved HBASE-28734.
-
Resolution: Fixed
> Improve HBase shell snapshot command Doc with TTL option
> -
>
> Key: HBASE-28734
> URL: https://issues.apache.org/jira/browse/HBASE-28734
> Project: HBase
> Issue Type: Improvement
> Components: shell
>Reporter: Ashok shetty
>Assignee: Liangjun He
>Priority: Minor
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1, 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.11
>
>
> The current HBase shell snapshot command allows users to create a snapshot of
> a specific table. While this command is useful, it could be enhanced by
> adding a TTL (Time-to-Live) option. This would allow users to specify a time
> period after which the snapshot would automatically be deleted.
> I propose we introduce a TTL option in the snapshot command doc as follows:
> hbase> snapshot 'sourceTable', 'snapshotName', \{TTL => '7d'}
> This would create a snapshot of 'sourceTable' called 'snapshotName' that
> would automatically be deleted after 7 days. The addition document of a TTL
> option would provide a better user experience and assist with efficient
> storage management.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work started] (HBASE-28734) Improve HBase shell snapshot command Doc with TTL option
[
https://issues.apache.org/jira/browse/HBASE-28734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HBASE-28734 started by Liangjun He.
---
> Improve HBase shell snapshot command Doc with TTL option
> -
>
> Key: HBASE-28734
> URL: https://issues.apache.org/jira/browse/HBASE-28734
> Project: HBase
> Issue Type: Improvement
> Components: shell
>Reporter: Ashok shetty
>Assignee: Liangjun He
>Priority: Minor
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1, 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.11
>
>
> The current HBase shell snapshot command allows users to create a snapshot of
> a specific table. While this command is useful, it could be enhanced by
> adding a TTL (Time-to-Live) option. This would allow users to specify a time
> period after which the snapshot would automatically be deleted.
> I propose we introduce a TTL option in the snapshot command doc as follows:
> hbase> snapshot 'sourceTable', 'snapshotName', \{TTL => '7d'}
> This would create a snapshot of 'sourceTable' called 'snapshotName' that
> would automatically be deleted after 7 days. The addition document of a TTL
> option would provide a better user experience and assist with efficient
> storage management.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-28734) Improve HBase shell snapshot command Doc with TTL option
[
https://issues.apache.org/jira/browse/HBASE-28734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Liangjun He updated HBASE-28734:
Fix Version/s: 2.7.0
3.0.0-beta-2
2.6.1
2.5.11
> Improve HBase shell snapshot command Doc with TTL option
> -
>
> Key: HBASE-28734
> URL: https://issues.apache.org/jira/browse/HBASE-28734
> Project: HBase
> Issue Type: Improvement
> Components: shell
>Reporter: Ashok shetty
>Assignee: Liangjun He
>Priority: Minor
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1, 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.11
>
>
> The current HBase shell snapshot command allows users to create a snapshot of
> a specific table. While this command is useful, it could be enhanced by
> adding a TTL (Time-to-Live) option. This would allow users to specify a time
> period after which the snapshot would automatically be deleted.
> I propose we introduce a TTL option in the snapshot command doc as follows:
> hbase> snapshot 'sourceTable', 'snapshotName', \{TTL => '7d'}
> This would create a snapshot of 'sourceTable' called 'snapshotName' that
> would automatically be deleted after 7 days. The addition document of a TTL
> option would provide a better user experience and assist with efficient
> storage management.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-28734) Improve HBase shell snapshot command Doc with TTL option
[
https://issues.apache.org/jira/browse/HBASE-28734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867618#comment-17867618
]
Liangjun He commented on HBASE-28734:
-
I have cherry-picked this PR to branch-2, branch-2.5, branch-2.6, and branch-3.
> Improve HBase shell snapshot command Doc with TTL option
> -
>
> Key: HBASE-28734
> URL: https://issues.apache.org/jira/browse/HBASE-28734
> Project: HBase
> Issue Type: Improvement
> Components: shell
>Reporter: Ashok shetty
>Assignee: Liangjun He
>Priority: Minor
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1
>
>
> The current HBase shell snapshot command allows users to create a snapshot of
> a specific table. While this command is useful, it could be enhanced by
> adding a TTL (Time-to-Live) option. This would allow users to specify a time
> period after which the snapshot would automatically be deleted.
> I propose we introduce a TTL option in the snapshot command doc as follows:
> hbase> snapshot 'sourceTable', 'snapshotName', \{TTL => '7d'}
> This would create a snapshot of 'sourceTable' called 'snapshotName' that
> would automatically be deleted after 7 days. The addition document of a TTL
> option would provide a better user experience and assist with efficient
> storage management.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-28734) Improve HBase shell snapshot command Doc with TTL option
[
https://issues.apache.org/jira/browse/HBASE-28734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867615#comment-17867615
]
Liangjun He commented on HBASE-28734:
-
[~zhangduo] The TTL support for snapshots was introduced in
[HBASE-22648|https://issues.apache.org/jira/browse/HBASE-22648] .
> Improve HBase shell snapshot command Doc with TTL option
> -
>
> Key: HBASE-28734
> URL: https://issues.apache.org/jira/browse/HBASE-28734
> Project: HBase
> Issue Type: Improvement
> Components: shell
>Reporter: Ashok shetty
>Assignee: Liangjun He
>Priority: Minor
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1
>
>
> The current HBase shell snapshot command allows users to create a snapshot of
> a specific table. While this command is useful, it could be enhanced by
> adding a TTL (Time-to-Live) option. This would allow users to specify a time
> period after which the snapshot would automatically be deleted.
> I propose we introduce a TTL option in the snapshot command doc as follows:
> hbase> snapshot 'sourceTable', 'snapshotName', \{TTL => '7d'}
> This would create a snapshot of 'sourceTable' called 'snapshotName' that
> would automatically be deleted after 7 days. The addition document of a TTL
> option would provide a better user experience and assist with efficient
> storage management.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-28734) Improve HBase shell snapshot command Doc with TTL option
[
https://issues.apache.org/jira/browse/HBASE-28734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867613#comment-17867613
]
Liangjun He commented on HBASE-28734:
-
[~zhangduo] I see that snapshot already supports TTL in version 2.5. Is it OK
to cherry-pick pr to branch-2.5, branch-2.6, branch-2, and branch-3?
> Improve HBase shell snapshot command Doc with TTL option
> -
>
> Key: HBASE-28734
> URL: https://issues.apache.org/jira/browse/HBASE-28734
> Project: HBase
> Issue Type: Improvement
> Components: shell
>Reporter: Ashok shetty
>Assignee: Liangjun He
>Priority: Minor
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1
>
>
> The current HBase shell snapshot command allows users to create a snapshot of
> a specific table. While this command is useful, it could be enhanced by
> adding a TTL (Time-to-Live) option. This would allow users to specify a time
> period after which the snapshot would automatically be deleted.
> I propose we introduce a TTL option in the snapshot command doc as follows:
> hbase> snapshot 'sourceTable', 'snapshotName', \{TTL => '7d'}
> This would create a snapshot of 'sourceTable' called 'snapshotName' that
> would automatically be deleted after 7 days. The addition document of a TTL
> option would provide a better user experience and assist with efficient
> storage management.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-28734) Improve HBase shell snapshot command Doc with TTL option
[
https://issues.apache.org/jira/browse/HBASE-28734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867610#comment-17867610
]
Liangjun He commented on HBASE-28734:
-
Thanks [~zhangduo] for reviewing.
> Improve HBase shell snapshot command Doc with TTL option
> -
>
> Key: HBASE-28734
> URL: https://issues.apache.org/jira/browse/HBASE-28734
> Project: HBase
> Issue Type: Improvement
> Components: shell
>Reporter: Ashok shetty
>Assignee: Liangjun He
>Priority: Minor
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1
>
>
> The current HBase shell snapshot command allows users to create a snapshot of
> a specific table. While this command is useful, it could be enhanced by
> adding a TTL (Time-to-Live) option. This would allow users to specify a time
> period after which the snapshot would automatically be deleted.
> I propose we introduce a TTL option in the snapshot command doc as follows:
> hbase> snapshot 'sourceTable', 'snapshotName', \{TTL => '7d'}
> This would create a snapshot of 'sourceTable' called 'snapshotName' that
> would automatically be deleted after 7 days. The addition document of a TTL
> option would provide a better user experience and assist with efficient
> storage management.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-28734) Improve HBase shell snapshot command Doc with TTL option
[
https://issues.apache.org/jira/browse/HBASE-28734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Liangjun He resolved HBASE-28734.
-
Fix Version/s: 4.0.0-alpha-1
Resolution: Fixed
> Improve HBase shell snapshot command Doc with TTL option
> -
>
> Key: HBASE-28734
> URL: https://issues.apache.org/jira/browse/HBASE-28734
> Project: HBase
> Issue Type: Improvement
> Components: shell
>Reporter: Ashok shetty
>Assignee: Liangjun He
>Priority: Minor
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1
>
>
> The current HBase shell snapshot command allows users to create a snapshot of
> a specific table. While this command is useful, it could be enhanced by
> adding a TTL (Time-to-Live) option. This would allow users to specify a time
> period after which the snapshot would automatically be deleted.
> I propose we introduce a TTL option in the snapshot command doc as follows:
> hbase> snapshot 'sourceTable', 'snapshotName', \{TTL => '7d'}
> This would create a snapshot of 'sourceTable' called 'snapshotName' that
> would automatically be deleted after 7 days. The addition document of a TTL
> option would provide a better user experience and assist with efficient
> storage management.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (HBASE-28734) Improve HBase shell snapshot command Doc with TTL option
[
https://issues.apache.org/jira/browse/HBASE-28734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Liangjun He reassigned HBASE-28734:
---
Assignee: Liangjun He
> Improve HBase shell snapshot command Doc with TTL option
> -
>
> Key: HBASE-28734
> URL: https://issues.apache.org/jira/browse/HBASE-28734
> Project: HBase
> Issue Type: Improvement
> Components: shell
>Reporter: Ashok shetty
>Assignee: Liangjun He
>Priority: Minor
>
> The current HBase shell snapshot command allows users to create a snapshot of
> a specific table. While this command is useful, it could be enhanced by
> adding a TTL (Time-to-Live) option. This would allow users to specify a time
> period after which the snapshot would automatically be deleted.
> I propose we introduce a TTL option in the snapshot command doc as follows:
> hbase> snapshot 'sourceTable', 'snapshotName', \{TTL => '7d'}
> This would create a snapshot of 'sourceTable' called 'snapshotName' that
> would automatically be deleted after 7 days. The addition document of a TTL
> option would provide a better user experience and assist with efficient
> storage management.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-28744) Add a new command-line option for table backup in our ref guide
[ https://issues.apache.org/jira/browse/HBASE-28744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867602#comment-17867602 ] Liangjun He commented on HBASE-28744: - Thanks [~zhangduo] for reviewing. > Add a new command-line option for table backup in our ref guide > --- > > Key: HBASE-28744 > URL: https://issues.apache.org/jira/browse/HBASE-28744 > Project: HBase > Issue Type: Task > Components: documentation >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Major > Labels: pull-request-available > Fix For: 4.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28744) Add a new command-line option for table backup in our ref guide
[ https://issues.apache.org/jira/browse/HBASE-28744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He resolved HBASE-28744. - Resolution: Fixed > Add a new command-line option for table backup in our ref guide > --- > > Key: HBASE-28744 > URL: https://issues.apache.org/jira/browse/HBASE-28744 > Project: HBase > Issue Type: Task > Components: documentation >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Major > Labels: pull-request-available > Fix For: 4.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HBASE-28702) TestBackupMerge fails 100% of times on flaky dashboard
[ https://issues.apache.org/jira/browse/HBASE-28702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867564#comment-17867564 ] Liangjun He commented on HBASE-28702: - Thanks [~zhangduo] and [~bbeaudreault] for reviewing. > TestBackupMerge fails 100% of times on flaky dashboard > -- > > Key: HBASE-28702 > URL: https://issues.apache.org/jira/browse/HBASE-28702 > Project: HBase > Issue Type: Bug > Components: backup&restore >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28702) TestBackupMerge fails 100% of times on flaky dashboard
[ https://issues.apache.org/jira/browse/HBASE-28702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He resolved HBASE-28702. - Resolution: Fixed > TestBackupMerge fails 100% of times on flaky dashboard > -- > > Key: HBASE-28702 > URL: https://issues.apache.org/jira/browse/HBASE-28702 > Project: HBase > Issue Type: Bug > Components: backup&restore >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HBASE-28702) TestBackupMerge fails 100% of times on flaky dashboard
[ https://issues.apache.org/jira/browse/HBASE-28702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867562#comment-17867562 ] Liangjun He commented on HBASE-28702: - I have cherry-picked this pr to branch-2, branch-2.6, branch-3 > TestBackupMerge fails 100% of times on flaky dashboard > -- > > Key: HBASE-28702 > URL: https://issues.apache.org/jira/browse/HBASE-28702 > Project: HBase > Issue Type: Bug > Components: backup&restore >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28744) Add a new command-line option for table backup in our ref guide
Liangjun He created HBASE-28744: --- Summary: Add a new command-line option for table backup in our ref guide Key: HBASE-28744 URL: https://issues.apache.org/jira/browse/HBASE-28744 Project: HBase Issue Type: Task Components: documentation Reporter: Liangjun He Assignee: Liangjun He Fix For: 4.0.0-alpha-1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HBASE-28702) TestBackupMerge fails 100% of times on flaky dashboard
[ https://issues.apache.org/jira/browse/HBASE-28702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He reassigned HBASE-28702: --- Assignee: Liangjun He > TestBackupMerge fails 100% of times on flaky dashboard > -- > > Key: HBASE-28702 > URL: https://issues.apache.org/jira/browse/HBASE-28702 > Project: HBase > Issue Type: Bug > Components: backup&restore >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Critical > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HBASE-28656) Optimize the verifyCopyResult logic in ExportSnapshot
[ https://issues.apache.org/jira/browse/HBASE-28656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859563#comment-17859563 ] Liangjun He commented on HBASE-28656: - I have cherry-picked this pr to branch-2, branch-2.6, branch-2.5 > Optimize the verifyCopyResult logic in ExportSnapshot > - > > Key: HBASE-28656 > URL: https://issues.apache.org/jira/browse/HBASE-28656 > Project: HBase > Issue Type: Improvement >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.9 > > > In [HBASE-28625|https://issues.apache.org/jira/browse/HBASE-28625], we added > checksum logic comparison for ExportSnapshot files, but the checksum > verification scenarios were too simple. This issue aims to address the > existing problem. For detailed discussion, please refer to PR > [5950|https://github.com/apache/hbase/pull/5950]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-28656) Optimize the verifyCopyResult logic in ExportSnapshot
[ https://issues.apache.org/jira/browse/HBASE-28656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He updated HBASE-28656: Fix Version/s: 2.7.0 2.6.1 2.5.9 > Optimize the verifyCopyResult logic in ExportSnapshot > - > > Key: HBASE-28656 > URL: https://issues.apache.org/jira/browse/HBASE-28656 > Project: HBase > Issue Type: Improvement >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.9 > > > In [HBASE-28625|https://issues.apache.org/jira/browse/HBASE-28625], we added > checksum logic comparison for ExportSnapshot files, but the checksum > verification scenarios were too simple. This issue aims to address the > existing problem. For detailed discussion, please refer to PR > [5950|https://github.com/apache/hbase/pull/5950]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-28656) Optimize the verifyCopyResult logic in ExportSnapshot
[ https://issues.apache.org/jira/browse/HBASE-28656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He updated HBASE-28656: Description: In [HBASE-28625|https://issues.apache.org/jira/browse/HBASE-28625], we added checksum logic comparison for ExportSnapshot files, but the checksum verification scenarios were too simple. This issue aims to address the existing problem. For detailed discussion, please refer to PR [5950|https://github.com/apache/hbase/pull/5950]. (was: In [HBASE-28625|https://issues.apache.org/jira/browse/HBASE-28625], we added checksum logic comparison for ExportSnapshot files, but the checksum verification scenarios were too simple. This issue aims to address the existing problem.) > Optimize the verifyCopyResult logic in ExportSnapshot > - > > Key: HBASE-28656 > URL: https://issues.apache.org/jira/browse/HBASE-28656 > Project: HBase > Issue Type: Improvement >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Critical > Labels: pull-request-available > > In [HBASE-28625|https://issues.apache.org/jira/browse/HBASE-28625], we added > checksum logic comparison for ExportSnapshot files, but the checksum > verification scenarios were too simple. This issue aims to address the > existing problem. For detailed discussion, please refer to PR > [5950|https://github.com/apache/hbase/pull/5950]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-28656) Optimize the verifyCopyResult logic in ExportSnapshot
[ https://issues.apache.org/jira/browse/HBASE-28656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He updated HBASE-28656: Summary: Optimize the verifyCopyResult logic in ExportSnapshot (was: Optimize the checksum logic in ExportSnapshot) > Optimize the verifyCopyResult logic in ExportSnapshot > - > > Key: HBASE-28656 > URL: https://issues.apache.org/jira/browse/HBASE-28656 > Project: HBase > Issue Type: Improvement >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Critical > > In [HBASE-28625|https://issues.apache.org/jira/browse/HBASE-28625], we added > checksum logic comparison for ExportSnapshot files, but the checksum > verification scenarios were too simple. This issue aims to address the > existing problem. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-28656) Optimize the checksum logic in ExportSnapshot
[ https://issues.apache.org/jira/browse/HBASE-28656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He updated HBASE-28656: Description: In [HBASE-28625|https://issues.apache.org/jira/browse/HBASE-28625], we added checksum logic comparison for ExportSnapshot files, but the checksum verification scenarios were too simple. This issue aims to address the existing problem. (was: In [HBASE-28652|https://issues.apache.org/jira/browse/HBASE-28652], we added checksum logic comparison for ExportSnapshot files, but the checksum verification scenarios were too simple. This issue aims to address the existing problem.) > Optimize the checksum logic in ExportSnapshot > - > > Key: HBASE-28656 > URL: https://issues.apache.org/jira/browse/HBASE-28656 > Project: HBase > Issue Type: Improvement >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Critical > > In [HBASE-28625|https://issues.apache.org/jira/browse/HBASE-28625], we added > checksum logic comparison for ExportSnapshot files, but the checksum > verification scenarios were too simple. This issue aims to address the > existing problem. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-28656) Optimize the checksum logic in ExportSnapshot
[ https://issues.apache.org/jira/browse/HBASE-28656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He updated HBASE-28656: Description: In [HBASE-28652|https://issues.apache.org/jira/browse/HBASE-28652], we added checksum logic comparison for ExportSnapshot files, but the checksum verification scenarios were too simple. This issue aims to address the existing problem. (was: ExportSnapshot should verify checksums for the source file and the target file) > Optimize the checksum logic in ExportSnapshot > - > > Key: HBASE-28656 > URL: https://issues.apache.org/jira/browse/HBASE-28656 > Project: HBase > Issue Type: Improvement >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Critical > > In [HBASE-28652|https://issues.apache.org/jira/browse/HBASE-28652], we added > checksum logic comparison for ExportSnapshot files, but the checksum > verification scenarios were too simple. This issue aims to address the > existing problem. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-28656) Optimize the checksum logic in ExportSnapshot
[ https://issues.apache.org/jira/browse/HBASE-28656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He updated HBASE-28656: Description: ExportSnapshot should verify checksums for the source file and the target file > Optimize the checksum logic in ExportSnapshot > - > > Key: HBASE-28656 > URL: https://issues.apache.org/jira/browse/HBASE-28656 > Project: HBase > Issue Type: Improvement >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Critical > > ExportSnapshot should verify checksums for the source file and the target file -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28656) Optimize the checksum logic in ExportSnapshot
Liangjun He created HBASE-28656: --- Summary: Optimize the checksum logic in ExportSnapshot Key: HBASE-28656 URL: https://issues.apache.org/jira/browse/HBASE-28656 Project: HBase Issue Type: Improvement Reporter: Liangjun He Assignee: Liangjun He -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HBASE-28625) ExportSnapshot should verify checksums for the source file and the target file
[ https://issues.apache.org/jira/browse/HBASE-28625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17852728#comment-17852728 ] Liangjun He commented on HBASE-28625: - I have cherry-picked this pr to branch-3, branch-2, branch-2.6, branch-2.5. > ExportSnapshot should verify checksums for the source file and the target file > -- > > Key: HBASE-28625 > URL: https://issues.apache.org/jira/browse/HBASE-28625 > Project: HBase > Issue Type: Improvement >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0-beta-2 > > > In our cluster, we encountered cases where the target hfile was corrupted > after executing ExportSnapshot. [HBASE-13588 > |https://issues.apache.org/jira/browse/HBASE-13588] can only checksum data > transferred, but cannot solve our problem. Therefore, we believe it is > necessary to verify checksums on the files exported by ExportSnapshot. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HBASE-28625) ExportSnapshot should verify checksums for the source file and the target file
[ https://issues.apache.org/jira/browse/HBASE-28625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17852727#comment-17852727 ] Liangjun He commented on HBASE-28625: - I have cherry-picked this pr to branch-3, branch-2, branch-2.6, branch-2.5. [~zhangduo] > ExportSnapshot should verify checksums for the source file and the target file > -- > > Key: HBASE-28625 > URL: https://issues.apache.org/jira/browse/HBASE-28625 > Project: HBase > Issue Type: Improvement >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0-beta-2 > > > In our cluster, we encountered cases where the target hfile was corrupted > after executing ExportSnapshot. [HBASE-13588 > |https://issues.apache.org/jira/browse/HBASE-13588] can only checksum data > transferred, but cannot solve our problem. Therefore, we believe it is > necessary to verify checksums on the files exported by ExportSnapshot. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (HBASE-28625) ExportSnapshot should verify checksums for the source file and the target file
[ https://issues.apache.org/jira/browse/HBASE-28625 ] Liangjun He deleted comment on HBASE-28625: - was (Author: heliangjun): I have cherry-picked this pr to branch-3, branch-2, branch-2.6, branch-2.5. [~zhangduo] > ExportSnapshot should verify checksums for the source file and the target file > -- > > Key: HBASE-28625 > URL: https://issues.apache.org/jira/browse/HBASE-28625 > Project: HBase > Issue Type: Improvement >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0-beta-2 > > > In our cluster, we encountered cases where the target hfile was corrupted > after executing ExportSnapshot. [HBASE-13588 > |https://issues.apache.org/jira/browse/HBASE-13588] can only checksum data > transferred, but cannot solve our problem. Therefore, we believe it is > necessary to verify checksums on the files exported by ExportSnapshot. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28625) ExportSnapshot should verify checksums for the source file and the target file
[ https://issues.apache.org/jira/browse/HBASE-28625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He resolved HBASE-28625. - Fix Version/s: 3.0.0-beta-2 Resolution: Fixed > ExportSnapshot should verify checksums for the source file and the target file > -- > > Key: HBASE-28625 > URL: https://issues.apache.org/jira/browse/HBASE-28625 > Project: HBase > Issue Type: Improvement >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0-beta-2 > > > In our cluster, we encountered cases where the target hfile was corrupted > after executing ExportSnapshot. [HBASE-13588 > |https://issues.apache.org/jira/browse/HBASE-13588] can only checksum data > transferred, but cannot solve our problem. Therefore, we believe it is > necessary to verify checksums on the files exported by ExportSnapshot. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-28625) ExportSnapshot should verify checksums for the source file and the target file
[ https://issues.apache.org/jira/browse/HBASE-28625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He updated HBASE-28625: Description: In our cluster, we encountered cases where the target hfile was corrupted after executing ExportSnapshot. [HBASE-13588 |https://issues.apache.org/jira/browse/HBASE-13588] can only checksum data transferred, but cannot solve our problem. Therefore, we believe it is necessary to verify checksums on the files exported by ExportSnapshot. (was: In our cluster, we encountered cases where the target hfile was corrupted after executing ExportSnapshot. [HBASE-13588 |https://issues.apache.org/jira/browse/HBASE-13588] can only checksum data transferred, but cannot solve our problem. Therefore, we believe it is necessary to perform checksum verification on the files exported by ExportSnapshot.) > ExportSnapshot should verify checksums for the source file and the target file > -- > > Key: HBASE-28625 > URL: https://issues.apache.org/jira/browse/HBASE-28625 > Project: HBase > Issue Type: Improvement >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Major > > In our cluster, we encountered cases where the target hfile was corrupted > after executing ExportSnapshot. [HBASE-13588 > |https://issues.apache.org/jira/browse/HBASE-13588] can only checksum data > transferred, but cannot solve our problem. Therefore, we believe it is > necessary to verify checksums on the files exported by ExportSnapshot. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-28625) ExportSnapshot should verify checksums for the source file and the target file
[ https://issues.apache.org/jira/browse/HBASE-28625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He updated HBASE-28625: Description: In our cluster, we encountered cases where the target hfile was corrupted after executing ExportSnapshot. [HBASE-13588 |https://issues.apache.org/jira/browse/HBASE-13588] can only checksum data transferred, but cannot solve our problem. Therefore, we believe it is necessary to perform checksum verification on the files exported by ExportSnapshot. > ExportSnapshot should verify checksums for the source file and the target file > -- > > Key: HBASE-28625 > URL: https://issues.apache.org/jira/browse/HBASE-28625 > Project: HBase > Issue Type: Improvement >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Major > > In our cluster, we encountered cases where the target hfile was corrupted > after executing ExportSnapshot. [HBASE-13588 > |https://issues.apache.org/jira/browse/HBASE-13588] can only checksum data > transferred, but cannot solve our problem. Therefore, we believe it is > necessary to perform checksum verification on the files exported by > ExportSnapshot. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28625) ExportSnapshot should verify checksums for the source file and the target file
Liangjun He created HBASE-28625: --- Summary: ExportSnapshot should verify checksums for the source file and the target file Key: HBASE-28625 URL: https://issues.apache.org/jira/browse/HBASE-28625 Project: HBase Issue Type: Improvement Reporter: Liangjun He Assignee: Liangjun He -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HBASE-28587) Remove deprecated methods in Cell
[ https://issues.apache.org/jira/browse/HBASE-28587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He reassigned HBASE-28587: --- Assignee: (was: Liangjun He) > Remove deprecated methods in Cell > - > > Key: HBASE-28587 > URL: https://issues.apache.org/jira/browse/HBASE-28587 > Project: HBase > Issue Type: Sub-task > Components: API, Client >Reporter: Duo Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (HBASE-28588) Remove deprecated methods in WAL
[ https://issues.apache.org/jira/browse/HBASE-28588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-28588 started by Liangjun He. --- > Remove deprecated methods in WAL > > > Key: HBASE-28588 > URL: https://issues.apache.org/jira/browse/HBASE-28588 > Project: HBase > Issue Type: Sub-task > Components: wal >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work stopped] (HBASE-28587) Remove deprecated methods in Cell
[ https://issues.apache.org/jira/browse/HBASE-28587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-28587 stopped by Liangjun He. --- > Remove deprecated methods in Cell > - > > Key: HBASE-28587 > URL: https://issues.apache.org/jira/browse/HBASE-28587 > Project: HBase > Issue Type: Sub-task > Components: API, Client >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work stopped] (HBASE-28588) Remove deprecated methods in WAL
[ https://issues.apache.org/jira/browse/HBASE-28588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-28588 stopped by Liangjun He. --- > Remove deprecated methods in WAL > > > Key: HBASE-28588 > URL: https://issues.apache.org/jira/browse/HBASE-28588 > Project: HBase > Issue Type: Sub-task > Components: wal >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (HBASE-28588) Remove deprecated methods in WAL
[ https://issues.apache.org/jira/browse/HBASE-28588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-28588 started by Liangjun He. --- > Remove deprecated methods in WAL > > > Key: HBASE-28588 > URL: https://issues.apache.org/jira/browse/HBASE-28588 > Project: HBase > Issue Type: Sub-task > Components: wal >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (HBASE-28587) Remove deprecated methods in Cell
[ https://issues.apache.org/jira/browse/HBASE-28587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-28587 started by Liangjun He. --- > Remove deprecated methods in Cell > - > > Key: HBASE-28587 > URL: https://issues.apache.org/jira/browse/HBASE-28587 > Project: HBase > Issue Type: Sub-task > Components: API, Client >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-28581) Remove deprecated methods in TableDescriotorBuilder
[ https://issues.apache.org/jira/browse/HBASE-28581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He updated HBASE-28581: Summary: Remove deprecated methods in TableDescriotorBuilder (was: Remove deprecated methods in TableDescriptor) > Remove deprecated methods in TableDescriotorBuilder > --- > > Key: HBASE-28581 > URL: https://issues.apache.org/jira/browse/HBASE-28581 > Project: HBase > Issue Type: Sub-task > Components: API, Client >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HBASE-28588) Remove deprecated methods in WAL
[ https://issues.apache.org/jira/browse/HBASE-28588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He reassigned HBASE-28588: --- Assignee: Liangjun He > Remove deprecated methods in WAL > > > Key: HBASE-28588 > URL: https://issues.apache.org/jira/browse/HBASE-28588 > Project: HBase > Issue Type: Sub-task > Components: wal >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HBASE-28587) Remove deprecated methods in Cell
[ https://issues.apache.org/jira/browse/HBASE-28587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He reassigned HBASE-28587: --- Assignee: Liangjun He > Remove deprecated methods in Cell > - > > Key: HBASE-28587 > URL: https://issues.apache.org/jira/browse/HBASE-28587 > Project: HBase > Issue Type: Sub-task > Components: API, Client >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (HBASE-28581) Remove deprecated methods in TableDescriptor
[ https://issues.apache.org/jira/browse/HBASE-28581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-28581 started by Liangjun He. --- > Remove deprecated methods in TableDescriptor > > > Key: HBASE-28581 > URL: https://issues.apache.org/jira/browse/HBASE-28581 > Project: HBase > Issue Type: Sub-task > Components: API, Client >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (HBASE-28576) Remove FirstKeyValueMatchingQualifiersFilter
[ https://issues.apache.org/jira/browse/HBASE-28576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-28576 started by Liangjun He. --- > Remove FirstKeyValueMatchingQualifiersFilter > > > Key: HBASE-28576 > URL: https://issues.apache.org/jira/browse/HBASE-28576 > Project: HBase > Issue Type: Sub-task > Components: Filters >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HBASE-28581) Remove deprecated methods in TableDescriptor
[ https://issues.apache.org/jira/browse/HBASE-28581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He reassigned HBASE-28581: --- Assignee: Liangjun He > Remove deprecated methods in TableDescriptor > > > Key: HBASE-28581 > URL: https://issues.apache.org/jira/browse/HBASE-28581 > Project: HBase > Issue Type: Sub-task > Components: API, Client >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HBASE-28576) Remove FirstKeyValueMatchingQualifiersFilter
[ https://issues.apache.org/jira/browse/HBASE-28576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He reassigned HBASE-28576: --- Assignee: Liangjun He > Remove FirstKeyValueMatchingQualifiersFilter > > > Key: HBASE-28576 > URL: https://issues.apache.org/jira/browse/HBASE-28576 > Project: HBase > Issue Type: Sub-task > Components: Filters >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HBASE-27936) NPE in StoreFileReader.passesGeneralRowPrefixBloomFilter()
[
https://issues.apache.org/jira/browse/HBASE-27936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735816#comment-17735816
]
Liangjun He commented on HBASE-27936:
-
[~zhangduo] sir, Perhaps “CONFIGURATION =>
{'RowPrefixBloomFilter.prefix_length' => '10'}” cause the problem?
> NPE in StoreFileReader.passesGeneralRowPrefixBloomFilter()
> --
>
> Key: HBASE-27936
> URL: https://issues.apache.org/jira/browse/HBASE-27936
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Reporter: Liangjun He
>Assignee: Duo Zhang
>Priority: Major
>
> When executing itbll, we encountered the following NPE exception：
> {code:java}
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.regionserver.StoreFileReader.passesGeneralRowPrefixBloomFilter(StoreFileReader.java:352)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileReader.passesBloomFilter(StoreFileReader.java:265)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.shouldUseScanner(StoreFileScanner.java:483)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.selectScannersFrom(StoreScanner.java:467)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:320)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:289)
> at
> org.apache.hadoop.hbase.regionserver.compactions.Compactor.createScanner(Compactor.java:544)
> at
> org.apache.hadoop.hbase.regionserver.compactions.Compactor$1.createScanner(Compactor.java:269)
> at
> org.apache.hadoop.hbase.regionserver.compactions.Compactor.compact(Compactor.java:358)
> at
> org.apache.hadoop.hbase.regionserver.compactions.DefaultCompactor.compact(DefaultCompactor.java:64)
> at
> org.apache.hadoop.hbase.regionserver.DefaultStoreEngine$DefaultCompactionContext.compact(DefaultStoreEngine.java:122)
> at
> org.apache.hadoop.hbase.regionserver.HStore.compact(HStore.java:1176)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.compact(HRegion.java:2407)
> at
> org.apache.hadoop.hbase.regionserver.CompactSplit$CompactionRunner.doCompaction(CompactSplit.java:667)
> at
> org.apache.hadoop.hbase.regionserver.CompactSplit$CompactionRunner.run(CompactSplit.java:716)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:750)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-27936) NPE in StoreFileReader.passesGeneralRowPrefixBloomFilter()
[
https://issues.apache.org/jira/browse/HBASE-27936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733098#comment-17733098
]
Liangjun He commented on HBASE-27936:
-
This issue is discussed in HBASE-27919.
> NPE in StoreFileReader.passesGeneralRowPrefixBloomFilter()
> --
>
> Key: HBASE-27936
> URL: https://issues.apache.org/jira/browse/HBASE-27936
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Reporter: Liangjun He
>Priority: Major
>
> When executing itbll, we encountered the following NPE exception：
> {code:java}
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.regionserver.StoreFileReader.passesGeneralRowPrefixBloomFilter(StoreFileReader.java:352)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileReader.passesBloomFilter(StoreFileReader.java:265)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.shouldUseScanner(StoreFileScanner.java:483)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.selectScannersFrom(StoreScanner.java:467)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:320)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:289)
> at
> org.apache.hadoop.hbase.regionserver.compactions.Compactor.createScanner(Compactor.java:544)
> at
> org.apache.hadoop.hbase.regionserver.compactions.Compactor$1.createScanner(Compactor.java:269)
> at
> org.apache.hadoop.hbase.regionserver.compactions.Compactor.compact(Compactor.java:358)
> at
> org.apache.hadoop.hbase.regionserver.compactions.DefaultCompactor.compact(DefaultCompactor.java:64)
> at
> org.apache.hadoop.hbase.regionserver.DefaultStoreEngine$DefaultCompactionContext.compact(DefaultStoreEngine.java:122)
> at
> org.apache.hadoop.hbase.regionserver.HStore.compact(HStore.java:1176)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.compact(HRegion.java:2407)
> at
> org.apache.hadoop.hbase.regionserver.CompactSplit$CompactionRunner.doCompaction(CompactSplit.java:667)
> at
> org.apache.hadoop.hbase.regionserver.CompactSplit$CompactionRunner.run(CompactSplit.java:716)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:750)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-27919) Run ITBLL for branch-3
[ https://issues.apache.org/jira/browse/HBASE-27919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733096#comment-17733096 ] Liangjun He commented on HBASE-27919: - I have created HBASE-27936 to track NPE problem. > Run ITBLL for branch-3 > -- > > Key: HBASE-27919 > URL: https://issues.apache.org/jira/browse/HBASE-27919 > Project: HBase > Issue Type: Sub-task > Components: integration tests >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (HBASE-27919) Run ITBLL for branch-3
[
https://issues.apache.org/jira/browse/HBASE-27919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732962#comment-17732962
]
Liangjun He edited comment on HBASE-27919 at 6/15/23 2:21 PM:
--
Setup a 5 slave nodes cluster, and run this command:
{code:java}
hbase org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList
-DIntegrationTestBigLinkedList.table=itbll -m slowDeterministic Loop 10 10
1 /tmp/biglinkedlist 100
{code}
Some RegionServer are experiencing the following error:
{code:java}
java.lang.NullPointerException
at
org.apache.hadoop.hbase.regionserver.StoreFileReader.passesGeneralRowPrefixBloomFilter(StoreFileReader.java:352)
at
org.apache.hadoop.hbase.regionserver.StoreFileReader.passesBloomFilter(StoreFileReader.java:265)
at
org.apache.hadoop.hbase.regionserver.StoreFileScanner.shouldUseScanner(StoreFileScanner.java:483)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.selectScannersFrom(StoreScanner.java:467)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:320)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:289)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor.createScanner(Compactor.java:544)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor$1.createScanner(Compactor.java:269)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor.compact(Compactor.java:358)
at
org.apache.hadoop.hbase.regionserver.compactions.DefaultCompactor.compact(DefaultCompactor.java:64)
at
org.apache.hadoop.hbase.regionserver.DefaultStoreEngine$DefaultCompactionContext.compact(DefaultStoreEngine.java:122)
at org.apache.hadoop.hbase.regionserver.HStore.compact(HStore.java:1176)
at
org.apache.hadoop.hbase.regionserver.HRegion.compact(HRegion.java:2407)
at
org.apache.hadoop.hbase.regionserver.CompactSplit$CompactionRunner.doCompaction(CompactSplit.java:667)
at
org.apache.hadoop.hbase.regionserver.CompactSplit$CompactionRunner.run(CompactSplit.java:716)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)
{code}
And the definition of the itbll table is as follows:
{code:java}
'itbll', {TABLE_ATTRIBUTES => {METADATA => {'SPLIT_POLICY' =>
'org.apache.hadoop.hbase.regionserver.ConstantSizeRegionSplitPolicy',
'hbase.store.file-tracker.impl' => 'DEFAULT'}}}, {NAME => 'EPvNy', VERSIONS =>
'3', MIN_VERSIONS => '3', METADATA => {'COMPRESSION_COMPACT' => 'BZIP2'}},
{NAME => 'IrePz', VERSIONS => '3', MIN_VERSIONS => '3', METADATA =>
{'COMPRESSION_COMPACT' => 'BZIP2'}}, {NAME => 'big', VERSIONS => '3',
MIN_VERSIONS => '3', BLOOMFILTER => 'ROWCOL', METADATA =>
{'COMPRESSION_COMPACT' => 'BZIP2'}}, {NAME => 'meta', VERSIONS => '3',
MIN_VERSIONS => '3', BLOOMFILTER => 'ROWCOL', METADATA =>
{'COMPRESSION_COMPACT' => 'BZIP2'}, CONFIGURATION =>
{'RowPrefixBloomFilter.prefix_length' => '10'}}, {NAME => 'tiny', VERSIONS =>
'3', MIN_VERSIONS => '3', BLOOMFILTER => 'ROWCOL', METADATA =>
{'COMPRESSION_COMPACT' => 'BZIP2'}}
{code}
[~zhangduo] sir, can you take a look at this issue, thanks?
I have created HBASE-27936 to track it.
was (Author: heliangjun):
Setup a 5 slave nodes cluster, and run this command:
{code:java}
hbase org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList
-DIntegrationTestBigLinkedList.table=itbll -m slowDeterministic Loop 10 10
1 /tmp/biglinkedlist 100
{code}
Some RegionServer are experiencing the following error:
{code:java}
java.lang.NullPointerException
at
org.apache.hadoop.hbase.regionserver.StoreFileReader.passesGeneralRowPrefixBloomFilter(StoreFileReader.java:352)
at
org.apache.hadoop.hbase.regionserver.StoreFileReader.passesBloomFilter(StoreFileReader.java:265)
at
org.apache.hadoop.hbase.regionserver.StoreFileScanner.shouldUseScanner(StoreFileScanner.java:483)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.selectScannersFrom(StoreScanner.java:467)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:320)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:289)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor.createScanner(Compactor.java:544)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor$1.createScanner(Compactor.java:269)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor.compact(Compactor.java:358)
at
org.apache.hadoop.hbase.regionserver.compactions.DefaultCompactor.compact(DefaultCompactor.java:64)
at
org.apache.hadoop.hbase.regionserver.DefaultStoreEngine$DefaultCompactionContext.
[jira] [Updated] (HBASE-27936) NPE in StoreFileReader.passesGeneralRowPrefixBloomFilter()
[
https://issues.apache.org/jira/browse/HBASE-27936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Liangjun He updated HBASE-27936:
External issue URL: (was:
https://issues.apache.org/jira/browse/HBASE-27919)
> NPE in StoreFileReader.passesGeneralRowPrefixBloomFilter()
> --
>
> Key: HBASE-27936
> URL: https://issues.apache.org/jira/browse/HBASE-27936
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Reporter: Liangjun He
>Priority: Major
>
> When executing itbll, we encountered the following NPE exception：
> {code:java}
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.regionserver.StoreFileReader.passesGeneralRowPrefixBloomFilter(StoreFileReader.java:352)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileReader.passesBloomFilter(StoreFileReader.java:265)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.shouldUseScanner(StoreFileScanner.java:483)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.selectScannersFrom(StoreScanner.java:467)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:320)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:289)
> at
> org.apache.hadoop.hbase.regionserver.compactions.Compactor.createScanner(Compactor.java:544)
> at
> org.apache.hadoop.hbase.regionserver.compactions.Compactor$1.createScanner(Compactor.java:269)
> at
> org.apache.hadoop.hbase.regionserver.compactions.Compactor.compact(Compactor.java:358)
> at
> org.apache.hadoop.hbase.regionserver.compactions.DefaultCompactor.compact(DefaultCompactor.java:64)
> at
> org.apache.hadoop.hbase.regionserver.DefaultStoreEngine$DefaultCompactionContext.compact(DefaultStoreEngine.java:122)
> at
> org.apache.hadoop.hbase.regionserver.HStore.compact(HStore.java:1176)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.compact(HRegion.java:2407)
> at
> org.apache.hadoop.hbase.regionserver.CompactSplit$CompactionRunner.doCompaction(CompactSplit.java:667)
> at
> org.apache.hadoop.hbase.regionserver.CompactSplit$CompactionRunner.run(CompactSplit.java:716)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:750)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-27936) NPE in StoreFileReader.passesGeneralRowPrefixBloomFilter()
[
https://issues.apache.org/jira/browse/HBASE-27936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Liangjun He updated HBASE-27936:
External issue ID: (was: HBASE-27919)
External issue URL: https://issues.apache.org/jira/browse/HBASE-27919
> NPE in StoreFileReader.passesGeneralRowPrefixBloomFilter()
> --
>
> Key: HBASE-27936
> URL: https://issues.apache.org/jira/browse/HBASE-27936
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Reporter: Liangjun He
>Priority: Major
>
> When executing itbll, we encountered the following NPE exception：
> {code:java}
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.regionserver.StoreFileReader.passesGeneralRowPrefixBloomFilter(StoreFileReader.java:352)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileReader.passesBloomFilter(StoreFileReader.java:265)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.shouldUseScanner(StoreFileScanner.java:483)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.selectScannersFrom(StoreScanner.java:467)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:320)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:289)
> at
> org.apache.hadoop.hbase.regionserver.compactions.Compactor.createScanner(Compactor.java:544)
> at
> org.apache.hadoop.hbase.regionserver.compactions.Compactor$1.createScanner(Compactor.java:269)
> at
> org.apache.hadoop.hbase.regionserver.compactions.Compactor.compact(Compactor.java:358)
> at
> org.apache.hadoop.hbase.regionserver.compactions.DefaultCompactor.compact(DefaultCompactor.java:64)
> at
> org.apache.hadoop.hbase.regionserver.DefaultStoreEngine$DefaultCompactionContext.compact(DefaultStoreEngine.java:122)
> at
> org.apache.hadoop.hbase.regionserver.HStore.compact(HStore.java:1176)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.compact(HRegion.java:2407)
> at
> org.apache.hadoop.hbase.regionserver.CompactSplit$CompactionRunner.doCompaction(CompactSplit.java:667)
> at
> org.apache.hadoop.hbase.regionserver.CompactSplit$CompactionRunner.run(CompactSplit.java:716)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:750)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-27936) NPE in StoreFileReader.passesGeneralRowPrefixBloomFilter()
Liangjun He created HBASE-27936:
---
Summary: NPE in StoreFileReader.passesGeneralRowPrefixBloomFilter()
Key: HBASE-27936
URL: https://issues.apache.org/jira/browse/HBASE-27936
Project: HBase
Issue Type: Bug
Components: regionserver
Reporter: Liangjun He
When executing itbll, we encountered the following NPE exception：
{code:java}
java.lang.NullPointerException
at
org.apache.hadoop.hbase.regionserver.StoreFileReader.passesGeneralRowPrefixBloomFilter(StoreFileReader.java:352)
at
org.apache.hadoop.hbase.regionserver.StoreFileReader.passesBloomFilter(StoreFileReader.java:265)
at
org.apache.hadoop.hbase.regionserver.StoreFileScanner.shouldUseScanner(StoreFileScanner.java:483)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.selectScannersFrom(StoreScanner.java:467)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:320)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:289)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor.createScanner(Compactor.java:544)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor$1.createScanner(Compactor.java:269)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor.compact(Compactor.java:358)
at
org.apache.hadoop.hbase.regionserver.compactions.DefaultCompactor.compact(DefaultCompactor.java:64)
at
org.apache.hadoop.hbase.regionserver.DefaultStoreEngine$DefaultCompactionContext.compact(DefaultStoreEngine.java:122)
at org.apache.hadoop.hbase.regionserver.HStore.compact(HStore.java:1176)
at
org.apache.hadoop.hbase.regionserver.HRegion.compact(HRegion.java:2407)
at
org.apache.hadoop.hbase.regionserver.CompactSplit$CompactionRunner.doCompaction(CompactSplit.java:667)
at
org.apache.hadoop.hbase.regionserver.CompactSplit$CompactionRunner.run(CompactSplit.java:716)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-27919) Run ITBLL for branch-3
[
https://issues.apache.org/jira/browse/HBASE-27919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732985#comment-17732985
]
Liangjun He commented on HBASE-27919:
-
Another error info：
{code:java}
2023-06-09 14:44:15,386 ERROR [regionserver/core-1-2:16020-shortCompactions-0]
util.ResourceLeakDetector: LEAK: RefCnt.release() was not called before it's
garbage-collected. See https://netty.io/wiki/reference-counted-objects.html for
more information.
Recent access records:
Created at:
org.apache.hadoop.hbase.nio.RefCnt.(RefCnt.java:59)
org.apache.hadoop.hbase.nio.RefCnt.create(RefCnt.java:54)
org.apache.hadoop.hbase.regionserver.MemStoreLABImpl.(MemStoreLABImpl.java:108)
sun.reflect.GeneratedConstructorAccessor13.newInstance(Unknown Source)
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
java.lang.reflect.Constructor.newInstance(Constructor.java:423)
org.apache.hadoop.hbase.util.ReflectionUtils.instantiate(ReflectionUtils.java:55)
org.apache.hadoop.hbase.util.ReflectionUtils.instantiateWithCustomCtor(ReflectionUtils.java:43)
org.apache.hadoop.hbase.regionserver.MemStoreLAB.newInstance(MemStoreLAB.java:116)
org.apache.hadoop.hbase.regionserver.SegmentFactory.createMutableSegment(SegmentFactory.java:81)
org.apache.hadoop.hbase.regionserver.AbstractMemStore.resetActive(AbstractMemStore.java:93)
org.apache.hadoop.hbase.regionserver.AbstractMemStore.(AbstractMemStore.java:83)
org.apache.hadoop.hbase.regionserver.DefaultMemStore.(DefaultMemStore.java:79)
sun.reflect.GeneratedConstructorAccessor12.newInstance(Unknown Source)
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
java.lang.reflect.Constructor.newInstance(Constructor.java:423)
org.apache.hadoop.hbase.util.ReflectionUtils.instantiate(ReflectionUtils.java:55)
org.apache.hadoop.hbase.util.ReflectionUtils.newInstance(ReflectionUtils.java:92)
org.apache.hadoop.hbase.regionserver.HStore.getMemstore(HStore.java:377)
org.apache.hadoop.hbase.regionserver.HStore.(HStore.java:283)
org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:6904)
org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:1173)
org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:1170)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
java.lang.Thread.run(Thread.java:750)
{code}
> Run ITBLL for branch-3
> --
>
> Key: HBASE-27919
> URL: https://issues.apache.org/jira/browse/HBASE-27919
> Project: HBase
> Issue Type: Sub-task
> Components: integration tests
>Reporter: Duo Zhang
>Assignee: Liangjun He
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (HBASE-27919) Run ITBLL for branch-3
[
https://issues.apache.org/jira/browse/HBASE-27919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732962#comment-17732962
]
Liangjun He edited comment on HBASE-27919 at 6/15/23 9:44 AM:
--
Setup a 5 slave nodes cluster, and run this command:
{code:java}
hbase org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList
-DIntegrationTestBigLinkedList.table=itbll -m slowDeterministic Loop 10 10
1 /tmp/biglinkedlist 100
{code}
Some RegionServer are experiencing the following error:
{code:java}
java.lang.NullPointerException
at
org.apache.hadoop.hbase.regionserver.StoreFileReader.passesGeneralRowPrefixBloomFilter(StoreFileReader.java:352)
at
org.apache.hadoop.hbase.regionserver.StoreFileReader.passesBloomFilter(StoreFileReader.java:265)
at
org.apache.hadoop.hbase.regionserver.StoreFileScanner.shouldUseScanner(StoreFileScanner.java:483)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.selectScannersFrom(StoreScanner.java:467)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:320)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:289)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor.createScanner(Compactor.java:544)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor$1.createScanner(Compactor.java:269)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor.compact(Compactor.java:358)
at
org.apache.hadoop.hbase.regionserver.compactions.DefaultCompactor.compact(DefaultCompactor.java:64)
at
org.apache.hadoop.hbase.regionserver.DefaultStoreEngine$DefaultCompactionContext.compact(DefaultStoreEngine.java:122)
at org.apache.hadoop.hbase.regionserver.HStore.compact(HStore.java:1176)
at
org.apache.hadoop.hbase.regionserver.HRegion.compact(HRegion.java:2407)
at
org.apache.hadoop.hbase.regionserver.CompactSplit$CompactionRunner.doCompaction(CompactSplit.java:667)
at
org.apache.hadoop.hbase.regionserver.CompactSplit$CompactionRunner.run(CompactSplit.java:716)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)
{code}
And the definition of the itbll table is as follows:
{code:java}
'itbll', {TABLE_ATTRIBUTES => {METADATA => {'SPLIT_POLICY' =>
'org.apache.hadoop.hbase.regionserver.ConstantSizeRegionSplitPolicy',
'hbase.store.file-tracker.impl' => 'DEFAULT'}}}, {NAME => 'EPvNy', VERSIONS =>
'3', MIN_VERSIONS => '3', METADATA => {'COMPRESSION_COMPACT' => 'BZIP2'}},
{NAME => 'IrePz', VERSIONS => '3', MIN_VERSIONS => '3', METADATA =>
{'COMPRESSION_COMPACT' => 'BZIP2'}}, {NAME => 'big', VERSIONS => '3',
MIN_VERSIONS => '3', BLOOMFILTER => 'ROWCOL', METADATA =>
{'COMPRESSION_COMPACT' => 'BZIP2'}}, {NAME => 'meta', VERSIONS => '3',
MIN_VERSIONS => '3', BLOOMFILTER => 'ROWCOL', METADATA =>
{'COMPRESSION_COMPACT' => 'BZIP2'}, CONFIGURATION =>
{'RowPrefixBloomFilter.prefix_length' => '10'}}, {NAME => 'tiny', VERSIONS =>
'3', MIN_VERSIONS => '3', BLOOMFILTER => 'ROWCOL', METADATA =>
{'COMPRESSION_COMPACT' => 'BZIP2'}}
{code}
[~zhangduo] sir, can you take a look at this issue, thanks?
was (Author: heliangjun):
Setup a 5 slave nodes cluster, and run this command:
{code:java}
hbase org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList
-DIntegrationTestBigLinkedList.table=itbll -m slowDeterministic Loop 10 10
1 /tmp/biglinkedlist 100
{code}
Some RegionServer are experiencing the following error:
{code:java}
java.lang.NullPointerException
at
org.apache.hadoop.hbase.regionserver.StoreFileReader.passesGeneralRowPrefixBloomFilter(StoreFileReader.java:352)
at
org.apache.hadoop.hbase.regionserver.StoreFileReader.passesBloomFilter(StoreFileReader.java:265)
at
org.apache.hadoop.hbase.regionserver.StoreFileScanner.shouldUseScanner(StoreFileScanner.java:483)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.selectScannersFrom(StoreScanner.java:467)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:320)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:289)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor.createScanner(Compactor.java:544)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor$1.createScanner(Compactor.java:269)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor.compact(Compactor.java:358)
at
org.apache.hadoop.hbase.regionserver.compactions.DefaultCompactor.compact(DefaultCompactor.java:64)
at
org.apache.hadoop.hbase.regionserver.DefaultStoreEngine$DefaultCompactionContext.compact(DefaultStoreEngine.java:122)
[jira] [Comment Edited] (HBASE-27919) Run ITBLL for branch-3
[
https://issues.apache.org/jira/browse/HBASE-27919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732962#comment-17732962
]
Liangjun He edited comment on HBASE-27919 at 6/15/23 9:42 AM:
--
Setup a 5 slave nodes cluster, and run this command:
{code:java}
hbase org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList
-DIntegrationTestBigLinkedList.table=itbll -m slowDeterministic Loop 10 10
1 /tmp/biglinkedlist 100
{code}
Some RegionServer are experiencing the following error:
{code:java}
java.lang.NullPointerException
at
org.apache.hadoop.hbase.regionserver.StoreFileReader.passesGeneralRowPrefixBloomFilter(StoreFileReader.java:352)
at
org.apache.hadoop.hbase.regionserver.StoreFileReader.passesBloomFilter(StoreFileReader.java:265)
at
org.apache.hadoop.hbase.regionserver.StoreFileScanner.shouldUseScanner(StoreFileScanner.java:483)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.selectScannersFrom(StoreScanner.java:467)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:320)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:289)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor.createScanner(Compactor.java:544)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor$1.createScanner(Compactor.java:269)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor.compact(Compactor.java:358)
at
org.apache.hadoop.hbase.regionserver.compactions.DefaultCompactor.compact(DefaultCompactor.java:64)
at
org.apache.hadoop.hbase.regionserver.DefaultStoreEngine$DefaultCompactionContext.compact(DefaultStoreEngine.java:122)
at org.apache.hadoop.hbase.regionserver.HStore.compact(HStore.java:1176)
at
org.apache.hadoop.hbase.regionserver.HRegion.compact(HRegion.java:2407)
at
org.apache.hadoop.hbase.regionserver.CompactSplit$CompactionRunner.doCompaction(CompactSplit.java:667)
at
org.apache.hadoop.hbase.regionserver.CompactSplit$CompactionRunner.run(CompactSplit.java:716)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)
{code}
And the definition of the itbll table is as follows:
{code:java}
'itbll', {TABLE_ATTRIBUTES => {METADATA => {'SPLIT_POLICY' =>
'org.apache.hadoop.hbase.regionserver.ConstantSizeRegionSplitPolicy',
'hbase.store.file-tracker.impl' => 'DEFAULT'}}}, {NAME => 'EPvNy', VERSIONS =>
'3', MIN_VERSIONS => '3', METADATA => {'COMPRESSION_COMPACT' => 'BZIP2'}},
{NAME => 'IrePz', VERSIONS => '3', MIN_VERSIONS => '3', METADATA =>
{'COMPRESSION_COMPACT' => 'BZIP2'}}, {NAME => 'big', VERSIONS => '3',
MIN_VERSIONS => '3', BLOOMFILTER => 'ROWCOL', METADATA =>
{'COMPRESSION_COMPACT' => 'BZIP2'}}, {NAME => 'meta', VERSIONS => '3',
MIN_VERSIONS => '3', BLOOMFILTER => 'ROWCOL', METADATA =>
{'COMPRESSION_COMPACT' => 'BZIP2'}, CONFIGURATION =>
{'RowPrefixBloomFilter.prefix_length' => '10'}}, {NAME => 'tiny', VERSIONS =>
'3', MIN_VERSIONS => '3', BLOOMFILTER => 'ROWCOL', METADATA =>
{'COMPRESSION_COMPACT' => 'BZIP2'}}
{code}
was (Author: heliangjun):
Setup a 5 slave nodes cluster, and run this command:
{code:java}
hbase org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList
-DIntegrationTestBigLinkedList.table=itbll_table -m slowDeterministic Loop 10
10 1 /tmp/biglinkedlist 100
{code}
Some RegionServer are experiencing the following error:
{code:java}
java.lang.NullPointerException
at
org.apache.hadoop.hbase.regionserver.StoreFileReader.passesGeneralRowPrefixBloomFilter(StoreFileReader.java:352)
at
org.apache.hadoop.hbase.regionserver.StoreFileReader.passesBloomFilter(StoreFileReader.java:265)
at
org.apache.hadoop.hbase.regionserver.StoreFileScanner.shouldUseScanner(StoreFileScanner.java:483)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.selectScannersFrom(StoreScanner.java:467)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:320)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:289)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor.createScanner(Compactor.java:544)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor$1.createScanner(Compactor.java:269)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor.compact(Compactor.java:358)
at
org.apache.hadoop.hbase.regionserver.compactions.DefaultCompactor.compact(DefaultCompactor.java:64)
at
org.apache.hadoop.hbase.regionserver.DefaultStoreEngine$DefaultCompactionContext.compact(DefaultStoreEngine.java:122)
at org.apache.hadoop.hbase.regionserver.HStore.co
[jira] [Comment Edited] (HBASE-27919) Run ITBLL for branch-3
[
https://issues.apache.org/jira/browse/HBASE-27919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732962#comment-17732962
]
Liangjun He edited comment on HBASE-27919 at 6/15/23 9:41 AM:
--
Setup a 5 slave nodes cluster, and run this command:
{code:java}
hbase org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList
-DIntegrationTestBigLinkedList.table=itbll_table -m slowDeterministic Loop 10
10 1 /tmp/biglinkedlist 100
{code}
Some RegionServer are experiencing the following error:
{code:java}
java.lang.NullPointerException
at
org.apache.hadoop.hbase.regionserver.StoreFileReader.passesGeneralRowPrefixBloomFilter(StoreFileReader.java:352)
at
org.apache.hadoop.hbase.regionserver.StoreFileReader.passesBloomFilter(StoreFileReader.java:265)
at
org.apache.hadoop.hbase.regionserver.StoreFileScanner.shouldUseScanner(StoreFileScanner.java:483)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.selectScannersFrom(StoreScanner.java:467)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:320)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:289)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor.createScanner(Compactor.java:544)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor$1.createScanner(Compactor.java:269)
at
org.apache.hadoop.hbase.regionserver.compactions.Compactor.compact(Compactor.java:358)
at
org.apache.hadoop.hbase.regionserver.compactions.DefaultCompactor.compact(DefaultCompactor.java:64)
at
org.apache.hadoop.hbase.regionserver.DefaultStoreEngine$DefaultCompactionContext.compact(DefaultStoreEngine.java:122)
at org.apache.hadoop.hbase.regionserver.HStore.compact(HStore.java:1176)
at
org.apache.hadoop.hbase.regionserver.HRegion.compact(HRegion.java:2407)
at
org.apache.hadoop.hbase.regionserver.CompactSplit$CompactionRunner.doCompaction(CompactSplit.java:667)
at
org.apache.hadoop.hbase.regionserver.CompactSplit$CompactionRunner.run(CompactSplit.java:716)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)
{code}
And the definition of the itbll table is as follows:
{code:java}
'itbll', {TABLE_ATTRIBUTES => {METADATA => {'SPLIT_POLICY' =>
'org.apache.hadoop.hbase.regionserver.ConstantSizeRegionSplitPolicy',
'hbase.store.file-tracker.impl' => 'DEFAULT'}}}, {NAME => 'EPvNy', VERSIONS =>
'3', MIN_VERSIONS => '3', METADATA => {'COMPRESSION_COMPACT' => 'BZIP2'}},
{NAME => 'IrePz', VERSIONS => '3', MIN_VERSIONS => '3', METADATA =>
{'COMPRESSION_COMPACT' => 'BZIP2'}}, {NAME => 'big', VERSIONS => '3',
MIN_VERSIONS => '3', BLOOMFILTER => 'ROWCOL', METADATA =>
{'COMPRESSION_COMPACT' => 'BZIP2'}}, {NAME => 'meta', VERSIONS => '3',
MIN_VERSIONS => '3', BLOOMFILTER => 'ROWCOL', METADATA =>
{'COMPRESSION_COMPACT' => 'BZIP2'}, CONFIGURATION =>
{'RowPrefixBloomFilter.prefix_length' => '10'}}, {NAME => 'tiny', VERSIONS =>
'3', MIN_VERSIONS => '3', BLOOMFILTER => 'ROWCOL', METADATA =>
{'COMPRESSION_COMPACT' => 'BZIP2'}}
{code}
was (Author: heliangjun):
Setup a 5 slave nodes cluster, and run this command:
{code:java}
hbase org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList
-DIntegrationTestBigLinkedList.table=itbll_table -m slowDeterministic Loop 10
10 1 /tmp/biglinkedlist 100
{code}
> Run ITBLL for branch-3
> --
>
> Key: HBASE-27919
> URL: https://issues.apache.org/jira/browse/HBASE-27919
> Project: HBase
> Issue Type: Sub-task
> Components: integration tests
>Reporter: Duo Zhang
>Assignee: Liangjun He
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (HBASE-27919) Run ITBLL for branch-3
[
https://issues.apache.org/jira/browse/HBASE-27919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732962#comment-17732962
]
Liangjun He edited comment on HBASE-27919 at 6/15/23 9:36 AM:
--
Setup a 5 slave nodes cluster, and run this command:
{code:shell}
hbase org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList
-DIntegrationTestBigLinkedList.table=itbll_table -m slowDeterministic Loop 10
10 1 /tmp/biglinkedlist 100
{code}
was (Author: heliangjun):
Setup a 5 slave nodes cluster, and run this command:
{quote}hbase org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList
-DIntegrationTestBigLinkedList.table=itbll_table -m slowDeterministic Loop 10
10 1 /tmp/biglinkedlist 100{quote}
> Run ITBLL for branch-3
> --
>
> Key: HBASE-27919
> URL: https://issues.apache.org/jira/browse/HBASE-27919
> Project: HBase
> Issue Type: Sub-task
> Components: integration tests
>Reporter: Duo Zhang
>Assignee: Liangjun He
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (HBASE-27919) Run ITBLL for branch-3
[
https://issues.apache.org/jira/browse/HBASE-27919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732962#comment-17732962
]
Liangjun He edited comment on HBASE-27919 at 6/15/23 9:36 AM:
--
Setup a 5 slave nodes cluster, and run this command:
{code:java}
hbase org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList
-DIntegrationTestBigLinkedList.table=itbll_table -m slowDeterministic Loop 10
10 1 /tmp/biglinkedlist 100
{code}
was (Author: heliangjun):
Setup a 5 slave nodes cluster, and run this command:
{code:shell}
hbase org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList
-DIntegrationTestBigLinkedList.table=itbll_table -m slowDeterministic Loop 10
10 1 /tmp/biglinkedlist 100
{code}
> Run ITBLL for branch-3
> --
>
> Key: HBASE-27919
> URL: https://issues.apache.org/jira/browse/HBASE-27919
> Project: HBase
> Issue Type: Sub-task
> Components: integration tests
>Reporter: Duo Zhang
>Assignee: Liangjun He
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-27919) Run ITBLL for branch-3
[
https://issues.apache.org/jira/browse/HBASE-27919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732962#comment-17732962
]
Liangjun He commented on HBASE-27919:
-
Setup a 5 slave nodes cluster, and run this command:
{quote}hbase org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList
-DIntegrationTestBigLinkedList.table=itbll_table -m slowDeterministic Loop 10
10 1 /tmp/biglinkedlist 100{quote}
> Run ITBLL for branch-3
> --
>
> Key: HBASE-27919
> URL: https://issues.apache.org/jira/browse/HBASE-27919
> Project: HBase
> Issue Type: Sub-task
> Components: integration tests
>Reporter: Duo Zhang
>Assignee: Liangjun He
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (HBASE-27919) Run ITBLL for branch-3
[ https://issues.apache.org/jira/browse/HBASE-27919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He reassigned HBASE-27919: --- Assignee: Liangjun He > Run ITBLL for branch-3 > -- > > Key: HBASE-27919 > URL: https://issues.apache.org/jira/browse/HBASE-27919 > Project: HBase > Issue Type: Sub-task > Components: integration tests >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27809) Attach move replication queue storage from zookeeper to a separated HBase table design doc to git repo
Liangjun He created HBASE-27809: --- Summary: Attach move replication queue storage from zookeeper to a separated HBase table design doc to git repo Key: HBASE-27809 URL: https://issues.apache.org/jira/browse/HBASE-27809 Project: HBase Issue Type: Sub-task Components: documentation, Replication Reporter: Liangjun He Assignee: Liangjun He -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-22978) Online slow response log
[
https://issues.apache.org/jira/browse/HBASE-22978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Liangjun He updated HBASE-22978:
Attachment: (was: Alluxio 开源AI和大数据存储编排平台.pdf)
> Online slow response log
>
>
> Key: HBASE-22978
> URL: https://issues.apache.org/jira/browse/HBASE-22978
> Project: HBase
> Issue Type: New Feature
> Components: Admin, Operability, regionserver, shell
>Affects Versions: 3.0.0-alpha-1, 2.3.0
>Reporter: Andrew Kyle Purtell
>Assignee: Viraj Jasani
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0
>
> Attachments:
> NamedQueue_Framework_Design_HBASE-24528_HBASE-22978_HBASE-24718.pdf, Screen
> Shot 2019-10-19 at 2.31.59 AM.png, Screen Shot 2019-10-19 at 2.32.54 AM.png,
> Screen Shot 2019-10-19 at 2.34.11 AM.png, Screen Shot 2019-10-19 at 2.36.14
> AM.png
>
>
> Today when an individual RPC exceeds a configurable time bound we log a
> complaint by way of the logging subsystem. These log lines look like:
> {noformat}
> 2019-08-30 22:10:36,195 WARN [,queue=15,port=60020] ipc.RpcServer -
> (responseTooSlow):
> {"call":"Scan(org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ScanRequest)",
> "starttimems":1567203007549,
> "responsesize":6819737,
> "method":"Scan",
> "param":"region { type: REGION_NAME value:
> \"tsdb,\\000\\000\\215\\f)o\\024\\302\\220\\000\\000\\000\\000\\000\\001\\000\\000\\000\\000\\000\\006\\000\\000\\000\\000\\000\\005\\000\\000",
> "processingtimems":28646,
> "client":"10.253.196.215:41116",
> "queuetimems":22453,
> "class":"HRegionServer"}
> {noformat}
> Unfortunately we often truncate the request parameters, like in the above
> example. We do this because the human readable representation is verbose, the
> rate of too slow warnings may be high, and the combination of these things
> can overwhelm the log capture system. The truncation is unfortunate because
> it eliminates much of the utility of the warnings. For example, the region
> name, the start and end keys, and the filter hierarchy are all important
> clues for debugging performance problems caused by moderate to low
> selectivity queries or queries made at a high rate.
> We can maintain an in-memory ring buffer of requests that were judged to be
> too slow in addition to the responseTooSlow logging. The in-memory
> representation can be complete and compressed. A new admin API and shell
> command can provide access to the ring buffer for online performance
> debugging. A modest sizing of the ring buffer will prevent excessive memory
> utilization for a minor performance debugging feature by limiting the total
> number of retained records. There is some chance a high rate of requests will
> cause information on other interesting requests to be overwritten before it
> can be read. This is the nature of a ring buffer and an acceptable trade off.
> The write request types do not require us to retain all information submitted
> in the request. We don't need to retain all key-values in the mutation, which
> may be too large to comfortably retain. We only need a unique set of row
> keys, or even a min/max range, and total counts.
> The consumers of this information will be debugging tools. We can afford to
> apply fast compression to ring buffer entries (if codec support is
> available), something like snappy or zstandard, and decompress on the fly
> when servicing the retrieval API request. This will minimize the impact of
> retaining more information about slow requests than we do today.
> This proposal is for retention of request information only, the same
> information provided by responseTooSlow warnings. Total size of response
> serialization, possibly also total cell or row counts, should be sufficient
> to characterize the response.
> Optionally persist new entries added to the ring buffer into one or more
> files in HDFS in a write-behind manner. If the HDFS writer blocks or falls
> behind and we are unable to persist an entry before it is overwritten, that
> is fine. Response too slow logging is best effort. If we can detect this make
> a note of it in the log file. Provide a tool for parsing, dumping, filtering,
> and pretty printing the slow logs written to HDFS. The tool and the shell can
> share and reuse some utility classes and methods for accomplishing that.
> —
> New shell commands:
> {{get_slow_responses [ ... , ] [ , \{
> } ]}}
> Retrieve, decode, and pretty print the contents of the too slow response ring
> buffer maintained by the given list of servers; or all servers in the cluster
> if no list is provided. Optionally provide a map of parameters for filtering
> as additional argument. The TABLE filter, which expects a string containing a
> table name, will include only entries pertaining to that table. The REGION
> filter
[jira] [Updated] (HBASE-22978) Online slow response log
[
https://issues.apache.org/jira/browse/HBASE-22978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Liangjun He updated HBASE-22978:
Attachment: (was: Flink Table Store 流计算存储.pptx)
> Online slow response log
>
>
> Key: HBASE-22978
> URL: https://issues.apache.org/jira/browse/HBASE-22978
> Project: HBase
> Issue Type: New Feature
> Components: Admin, Operability, regionserver, shell
>Affects Versions: 3.0.0-alpha-1, 2.3.0
>Reporter: Andrew Kyle Purtell
>Assignee: Viraj Jasani
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0
>
> Attachments:
> NamedQueue_Framework_Design_HBASE-24528_HBASE-22978_HBASE-24718.pdf, Screen
> Shot 2019-10-19 at 2.31.59 AM.png, Screen Shot 2019-10-19 at 2.32.54 AM.png,
> Screen Shot 2019-10-19 at 2.34.11 AM.png, Screen Shot 2019-10-19 at 2.36.14
> AM.png
>
>
> Today when an individual RPC exceeds a configurable time bound we log a
> complaint by way of the logging subsystem. These log lines look like:
> {noformat}
> 2019-08-30 22:10:36,195 WARN [,queue=15,port=60020] ipc.RpcServer -
> (responseTooSlow):
> {"call":"Scan(org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ScanRequest)",
> "starttimems":1567203007549,
> "responsesize":6819737,
> "method":"Scan",
> "param":"region { type: REGION_NAME value:
> \"tsdb,\\000\\000\\215\\f)o\\024\\302\\220\\000\\000\\000\\000\\000\\001\\000\\000\\000\\000\\000\\006\\000\\000\\000\\000\\000\\005\\000\\000",
> "processingtimems":28646,
> "client":"10.253.196.215:41116",
> "queuetimems":22453,
> "class":"HRegionServer"}
> {noformat}
> Unfortunately we often truncate the request parameters, like in the above
> example. We do this because the human readable representation is verbose, the
> rate of too slow warnings may be high, and the combination of these things
> can overwhelm the log capture system. The truncation is unfortunate because
> it eliminates much of the utility of the warnings. For example, the region
> name, the start and end keys, and the filter hierarchy are all important
> clues for debugging performance problems caused by moderate to low
> selectivity queries or queries made at a high rate.
> We can maintain an in-memory ring buffer of requests that were judged to be
> too slow in addition to the responseTooSlow logging. The in-memory
> representation can be complete and compressed. A new admin API and shell
> command can provide access to the ring buffer for online performance
> debugging. A modest sizing of the ring buffer will prevent excessive memory
> utilization for a minor performance debugging feature by limiting the total
> number of retained records. There is some chance a high rate of requests will
> cause information on other interesting requests to be overwritten before it
> can be read. This is the nature of a ring buffer and an acceptable trade off.
> The write request types do not require us to retain all information submitted
> in the request. We don't need to retain all key-values in the mutation, which
> may be too large to comfortably retain. We only need a unique set of row
> keys, or even a min/max range, and total counts.
> The consumers of this information will be debugging tools. We can afford to
> apply fast compression to ring buffer entries (if codec support is
> available), something like snappy or zstandard, and decompress on the fly
> when servicing the retrieval API request. This will minimize the impact of
> retaining more information about slow requests than we do today.
> This proposal is for retention of request information only, the same
> information provided by responseTooSlow warnings. Total size of response
> serialization, possibly also total cell or row counts, should be sufficient
> to characterize the response.
> Optionally persist new entries added to the ring buffer into one or more
> files in HDFS in a write-behind manner. If the HDFS writer blocks or falls
> behind and we are unable to persist an entry before it is overwritten, that
> is fine. Response too slow logging is best effort. If we can detect this make
> a note of it in the log file. Provide a tool for parsing, dumping, filtering,
> and pretty printing the slow logs written to HDFS. The tool and the shell can
> share and reuse some utility classes and methods for accomplishing that.
> —
> New shell commands:
> {{get_slow_responses [ ... , ] [ , \{
> } ]}}
> Retrieve, decode, and pretty print the contents of the too slow response ring
> buffer maintained by the given list of servers; or all servers in the cluster
> if no list is provided. Optionally provide a map of parameters for filtering
> as additional argument. The TABLE filter, which expects a string containing a
> table name, will include only entries pertaining to that table. The REGION
> filt
[jira] [Assigned] (HBASE-27516) Document the table based replication queue storage in ref guide
[ https://issues.apache.org/jira/browse/HBASE-27516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He reassigned HBASE-27516: --- Assignee: Liangjun He > Document the table based replication queue storage in ref guide > --- > > Key: HBASE-27516 > URL: https://issues.apache.org/jira/browse/HBASE-27516 > Project: HBase > Issue Type: Sub-task > Components: documentation, Replication >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HBASE-27274) Re-enable the disabled tests when implementing HBASE-27212
[ https://issues.apache.org/jira/browse/HBASE-27274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17711930#comment-17711930 ] Liangjun He commented on HBASE-27274: - Only TestHBaseFsckReplication needs to be enabled now. I will create a PR for it. > Re-enable the disabled tests when implementing HBASE-27212 > -- > > Key: HBASE-27274 > URL: https://issues.apache.org/jira/browse/HBASE-27274 > Project: HBase > Issue Type: Sub-task > Components: test >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > > For landing the first basic framework of the new replication queue storage > implementation, we have to disable several UTs. This issue is used to track > these tests to make sure we finally re-enabled them all. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-22978) Online slow response log
[
https://issues.apache.org/jira/browse/HBASE-22978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Liangjun He updated HBASE-22978:
Attachment: Alluxio 开源AI和大数据存储编排平台.pdf
Flink Table Store 流计算存储.pptx
> Online slow response log
>
>
> Key: HBASE-22978
> URL: https://issues.apache.org/jira/browse/HBASE-22978
> Project: HBase
> Issue Type: New Feature
> Components: Admin, Operability, regionserver, shell
>Affects Versions: 3.0.0-alpha-1, 2.3.0
>Reporter: Andrew Kyle Purtell
>Assignee: Viraj Jasani
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0
>
> Attachments: Alluxio 开源AI和大数据存储编排平台.pdf, Flink Table Store
> 流计算存储.pptx,
> NamedQueue_Framework_Design_HBASE-24528_HBASE-22978_HBASE-24718.pdf, Screen
> Shot 2019-10-19 at 2.31.59 AM.png, Screen Shot 2019-10-19 at 2.32.54 AM.png,
> Screen Shot 2019-10-19 at 2.34.11 AM.png, Screen Shot 2019-10-19 at 2.36.14
> AM.png
>
>
> Today when an individual RPC exceeds a configurable time bound we log a
> complaint by way of the logging subsystem. These log lines look like:
> {noformat}
> 2019-08-30 22:10:36,195 WARN [,queue=15,port=60020] ipc.RpcServer -
> (responseTooSlow):
> {"call":"Scan(org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ScanRequest)",
> "starttimems":1567203007549,
> "responsesize":6819737,
> "method":"Scan",
> "param":"region { type: REGION_NAME value:
> \"tsdb,\\000\\000\\215\\f)o\\024\\302\\220\\000\\000\\000\\000\\000\\001\\000\\000\\000\\000\\000\\006\\000\\000\\000\\000\\000\\005\\000\\000",
> "processingtimems":28646,
> "client":"10.253.196.215:41116",
> "queuetimems":22453,
> "class":"HRegionServer"}
> {noformat}
> Unfortunately we often truncate the request parameters, like in the above
> example. We do this because the human readable representation is verbose, the
> rate of too slow warnings may be high, and the combination of these things
> can overwhelm the log capture system. The truncation is unfortunate because
> it eliminates much of the utility of the warnings. For example, the region
> name, the start and end keys, and the filter hierarchy are all important
> clues for debugging performance problems caused by moderate to low
> selectivity queries or queries made at a high rate.
> We can maintain an in-memory ring buffer of requests that were judged to be
> too slow in addition to the responseTooSlow logging. The in-memory
> representation can be complete and compressed. A new admin API and shell
> command can provide access to the ring buffer for online performance
> debugging. A modest sizing of the ring buffer will prevent excessive memory
> utilization for a minor performance debugging feature by limiting the total
> number of retained records. There is some chance a high rate of requests will
> cause information on other interesting requests to be overwritten before it
> can be read. This is the nature of a ring buffer and an acceptable trade off.
> The write request types do not require us to retain all information submitted
> in the request. We don't need to retain all key-values in the mutation, which
> may be too large to comfortably retain. We only need a unique set of row
> keys, or even a min/max range, and total counts.
> The consumers of this information will be debugging tools. We can afford to
> apply fast compression to ring buffer entries (if codec support is
> available), something like snappy or zstandard, and decompress on the fly
> when servicing the retrieval API request. This will minimize the impact of
> retaining more information about slow requests than we do today.
> This proposal is for retention of request information only, the same
> information provided by responseTooSlow warnings. Total size of response
> serialization, possibly also total cell or row counts, should be sufficient
> to characterize the response.
> Optionally persist new entries added to the ring buffer into one or more
> files in HDFS in a write-behind manner. If the HDFS writer blocks or falls
> behind and we are unable to persist an entry before it is overwritten, that
> is fine. Response too slow logging is best effort. If we can detect this make
> a note of it in the log file. Provide a tool for parsing, dumping, filtering,
> and pretty printing the slow logs written to HDFS. The tool and the shell can
> share and reuse some utility classes and methods for accomplishing that.
> —
> New shell commands:
> {{get_slow_responses [ ... , ] [ , \{
> } ]}}
> Retrieve, decode, and pretty print the contents of the too slow response ring
> buffer maintained by the given list of servers; or all servers in the cluster
> if no list is provided. Optionally provide a map of parameters for filtering
> as additional argument. The TABLE filter, which expects a string conta
[jira] [Updated] (HBASE-27623) Start a new ReplicationSyncUp after the previous failed
[ https://issues.apache.org/jira/browse/HBASE-27623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He updated HBASE-27623: Summary: Start a new ReplicationSyncUp after the previous failed (was: Start a new ReplicationSyncUp after the previous ReplicationSyncUp failed) > Start a new ReplicationSyncUp after the previous failed > --- > > Key: HBASE-27623 > URL: https://issues.apache.org/jira/browse/HBASE-27623 > Project: HBase > Issue Type: Sub-task > Components: Replication, tooling >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27623) Start a new ReplicationSyncUp after the previous ReplicationSyncUp failed
[ https://issues.apache.org/jira/browse/HBASE-27623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He updated HBASE-27623: Summary: Start a new ReplicationSyncUp after the previous ReplicationSyncUp failed (was: Avoid starting two ReplicationSyncUp at the same time) > Start a new ReplicationSyncUp after the previous ReplicationSyncUp failed > - > > Key: HBASE-27623 > URL: https://issues.apache.org/jira/browse/HBASE-27623 > Project: HBase > Issue Type: Sub-task > Components: Replication, tooling >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HBASE-27623) Avoid starting two ReplicationSyncUp at the same time
[ https://issues.apache.org/jira/browse/HBASE-27623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17705400#comment-17705400 ] Liangjun He commented on HBASE-27623: - [~zhangduo] Yeah, Sir. If we want to start a new ReplicationSyncUp after the previous ReplicationSyncUp failed, this is indeed a good idea. I will create a pr for this. > Avoid starting two ReplicationSyncUp at the same time > - > > Key: HBASE-27623 > URL: https://issues.apache.org/jira/browse/HBASE-27623 > Project: HBase > Issue Type: Sub-task > Components: Replication, tooling >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HBASE-27274) Re-enable the disabled tests when implementing HBASE-27212
[ https://issues.apache.org/jira/browse/HBASE-27274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He reassigned HBASE-27274: --- Assignee: Liangjun He > Re-enable the disabled tests when implementing HBASE-27212 > -- > > Key: HBASE-27274 > URL: https://issues.apache.org/jira/browse/HBASE-27274 > Project: HBase > Issue Type: Sub-task > Components: test >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > > For landing the first basic framework of the new replication queue storage > implementation, we have to disable several UTs. This issue is used to track > these tests to make sure we finally re-enabled them all. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27623) Avoid starting two ReplicationSyncUp at the same time
Liangjun He created HBASE-27623: --- Summary: Avoid starting two ReplicationSyncUp at the same time Key: HBASE-27623 URL: https://issues.apache.org/jira/browse/HBASE-27623 Project: HBase Issue Type: Sub-task Components: Replication, tooling Reporter: Liangjun He Assignee: Liangjun He -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (HBASE-27216) Revisit the ReplicationSyncUp tool
[ https://issues.apache.org/jira/browse/HBASE-27216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-27216 started by Liangjun He. --- > Revisit the ReplicationSyncUp tool > -- > > Key: HBASE-27216 > URL: https://issues.apache.org/jira/browse/HBASE-27216 > Project: HBase > Issue Type: Sub-task > Components: Replication, tooling >Reporter: Duo Zhang >Assignee: Liangjun He >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27489) Fix several problems after HBASE-27304
[ https://issues.apache.org/jira/browse/HBASE-27489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He updated HBASE-27489: Description: In the HBASE-27304, we support using IP to expose master/rs service to client. But there are several problems that need to be fixed, see #[4732|https://github.com/apache/hbase/pull/4732] for details. This issue is used to track and fix these problems. (was: In the HBASE-27304, we support using IP to expose master/rs service to client. But there are several problems that need to be fixed. This issue is used to track and fix these problems.) > Fix several problems after HBASE-27304 > -- > > Key: HBASE-27489 > URL: https://issues.apache.org/jira/browse/HBASE-27489 > Project: HBase > Issue Type: Bug > Components: master, regionserver >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Minor > > In the HBASE-27304, we support using IP to expose master/rs service to > client. But there are several problems that need to be fixed, see > #[4732|https://github.com/apache/hbase/pull/4732] for details. This issue is > used to track and fix these problems. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27483) Expose table and region storefiles accessed days and size to the metrics
[ https://issues.apache.org/jira/browse/HBASE-27483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He updated HBASE-27483: Description: At present, we have no metrics to show the hot and cold status of region/table storefiles, but from the perspective of storage cost, users are very concerned about the hot and cold status of their table data. So, it's necessary to expose region/table storefiles accessed days and size to the metrics. was: At present, we have no metrics to show the hot and cold status of region/table data, but from the perspective of storage cost, users are very concerned about the hot and cold status of their table data. So, it's necessary to expose region storefiles accessed days and size to the metrics. > Expose table and region storefiles accessed days and size to the metrics > > > Key: HBASE-27483 > URL: https://issues.apache.org/jira/browse/HBASE-27483 > Project: HBase > Issue Type: New Feature > Components: regionserver >Affects Versions: 3.0.0-alpha-4 >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Minor > Fix For: 3.0.0-alpha-4 > > > At present, we have no metrics to show the hot and cold status of > region/table storefiles, but from the perspective of storage cost, users are > very concerned about the hot and cold status of their table data. > So, it's necessary to expose region/table storefiles accessed days and size > to the metrics. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27483) Expose table and region storefiles accessed days and size to the metrics
[ https://issues.apache.org/jira/browse/HBASE-27483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LiangJun He updated HBASE-27483: Priority: Minor (was: Major) > Expose table and region storefiles accessed days and size to the metrics > > > Key: HBASE-27483 > URL: https://issues.apache.org/jira/browse/HBASE-27483 > Project: HBase > Issue Type: New Feature > Components: regionserver >Affects Versions: 3.0.0-alpha-4 >Reporter: LiangJun He >Assignee: LiangJun He >Priority: Minor > Fix For: 3.0.0-alpha-4 > > > At present, we have no metrics to show the hot and cold status of > region/table data, but from the perspective of storage cost, users are very > concerned about the hot and cold status of their table data. > So, it's necessary to expose region storefiles accessed days and size to the > metrics. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27444) Add tool commands list_enabled_tables and list_disabled_tables
[ https://issues.apache.org/jira/browse/HBASE-27444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LiangJun He updated HBASE-27444: Release Note: Introduce two shell commands 'list_enabled_tables' and 'list_disabled_tables' to list enabled or disabled tables. > Add tool commands list_enabled_tables and list_disabled_tables > -- > > Key: HBASE-27444 > URL: https://issues.apache.org/jira/browse/HBASE-27444 > Project: HBase > Issue Type: New Feature > Components: master >Affects Versions: 3.0.0-alpha-4 >Reporter: LiangJun He >Assignee: LiangJun He >Priority: Minor > Fix For: 2.6.0, 3.0.0-alpha-4 > > > Currently, there is no command line tool to get the all enabled or disabled > tables, which can only be seen through the HMaster UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HBASE-27505) [hbase-thirdparty] Set updatePomFile for maven-flatten-plugin
[ https://issues.apache.org/jira/browse/HBASE-27505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LiangJun He reassigned HBASE-27505: --- Assignee: LiangJun He > [hbase-thirdparty] Set updatePomFile for maven-flatten-plugin > - > > Key: HBASE-27505 > URL: https://issues.apache.org/jira/browse/HBASE-27505 > Project: HBase > Issue Type: Bug > Components: build, pom, thirdparty >Reporter: Duo Zhang >Assignee: LiangJun He >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27483) Expose table/region storefiles accessed days and size to the metrics
[ https://issues.apache.org/jira/browse/HBASE-27483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LiangJun He updated HBASE-27483: Summary: Expose table/region storefiles accessed days and size to the metrics (was: Expose region storefiles accessed days and size to the metrics) > Expose table/region storefiles accessed days and size to the metrics > > > Key: HBASE-27483 > URL: https://issues.apache.org/jira/browse/HBASE-27483 > Project: HBase > Issue Type: New Feature > Components: regionserver >Affects Versions: 3.0.0-alpha-4 >Reporter: LiangJun He >Assignee: LiangJun He >Priority: Major > Fix For: 3.0.0-alpha-4 > > > At present, we have no metrics to show the hot and cold status of > region/table data, but from the perspective of storage cost, users are very > concerned about the hot and cold status of their table data. > So, it's necessary to expose region storefiles accessed days and size to the > metrics. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27483) Expose table and region storefiles accessed days and size to the metrics
[ https://issues.apache.org/jira/browse/HBASE-27483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LiangJun He updated HBASE-27483: Summary: Expose table and region storefiles accessed days and size to the metrics (was: Expose table/region storefiles accessed days and size to the metrics) > Expose table and region storefiles accessed days and size to the metrics > > > Key: HBASE-27483 > URL: https://issues.apache.org/jira/browse/HBASE-27483 > Project: HBase > Issue Type: New Feature > Components: regionserver >Affects Versions: 3.0.0-alpha-4 >Reporter: LiangJun He >Assignee: LiangJun He >Priority: Major > Fix For: 3.0.0-alpha-4 > > > At present, we have no metrics to show the hot and cold status of > region/table data, but from the perspective of storage cost, users are very > concerned about the hot and cold status of their table data. > So, it's necessary to expose region storefiles accessed days and size to the > metrics. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27489) Fix several problems after HBASE-27304
LiangJun He created HBASE-27489: --- Summary: Fix several problems after HBASE-27304 Key: HBASE-27489 URL: https://issues.apache.org/jira/browse/HBASE-27489 Project: HBase Issue Type: Bug Components: master, regionserver Reporter: LiangJun He Assignee: LiangJun He In the HBASE-27304, we support using IP to expose master/rs service to client. But there are several problems that need to be fixed. This issue is used to track and fix these problems. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27483) Expose region storefiles accessed days and size to the metrics
[ https://issues.apache.org/jira/browse/HBASE-27483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LiangJun He updated HBASE-27483: Description: At present, we have no metrics to show the hot and cold status of region/table data, but from the perspective of storage cost, users are very concerned about the hot and cold status of their table data. So, it's necessary to expose region storefiles accessed days and size to the metrics. was: At present, we have no metrics to show the hot and cold status of region/table data, but from the perspective of storage cost, users are very concerned about the hot and cold status of their table data. So, it's necessary to > Expose region storefiles accessed days and size to the metrics > -- > > Key: HBASE-27483 > URL: https://issues.apache.org/jira/browse/HBASE-27483 > Project: HBase > Issue Type: New Feature > Components: regionserver >Affects Versions: 3.0.0-alpha-4 >Reporter: LiangJun He >Assignee: LiangJun He >Priority: Major > Fix For: 3.0.0-alpha-4 > > > At present, we have no metrics to show the hot and cold status of > region/table data, but from the perspective of storage cost, users are very > concerned about the hot and cold status of their table data. > So, it's necessary to expose region storefiles accessed days and size to the > metrics. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27483) Expose region storefiles accessed days and size to the metrics
[ https://issues.apache.org/jira/browse/HBASE-27483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LiangJun He updated HBASE-27483: Description: At present, we have no metrics to show the hot and cold status of region/table data, but from the perspective of storage cost, users are very concerned about the hot and cold status of their table data. So, it's necessary to > Expose region storefiles accessed days and size to the metrics > -- > > Key: HBASE-27483 > URL: https://issues.apache.org/jira/browse/HBASE-27483 > Project: HBase > Issue Type: New Feature > Components: regionserver >Affects Versions: 3.0.0-alpha-4 >Reporter: LiangJun He >Assignee: LiangJun He >Priority: Major > Fix For: 3.0.0-alpha-4 > > > At present, we have no metrics to show the hot and cold status of > region/table data, but from the perspective of storage cost, users are very > concerned about the hot and cold status of their table data. > So, it's necessary to -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27482) Expose region/table datalocality data to the metrics
[ https://issues.apache.org/jira/browse/HBASE-27482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LiangJun He updated HBASE-27482: Description: It is necessary to expose the datalocality of region/table to the metrics for collection and monitoring. > Expose region/table datalocality data to the metrics > > > Key: HBASE-27482 > URL: https://issues.apache.org/jira/browse/HBASE-27482 > Project: HBase > Issue Type: New Feature > Components: regionserver >Affects Versions: 3.0.0-alpha-4 >Reporter: LiangJun He >Assignee: LiangJun He >Priority: Major > Fix For: 3.0.0-alpha-4 > > > It is necessary to expose the datalocality of region/table to the metrics for > collection and monitoring. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27483) Expose region storefiles accessed days and size to the metrics
LiangJun He created HBASE-27483: --- Summary: Expose region storefiles accessed days and size to the metrics Key: HBASE-27483 URL: https://issues.apache.org/jira/browse/HBASE-27483 Project: HBase Issue Type: New Feature Components: regionserver Affects Versions: 3.0.0-alpha-4 Reporter: LiangJun He Assignee: LiangJun He Fix For: 3.0.0-alpha-4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27482) Expose region/table datalocality data to the metrics
LiangJun He created HBASE-27482: --- Summary: Expose region/table datalocality data to the metrics Key: HBASE-27482 URL: https://issues.apache.org/jira/browse/HBASE-27482 Project: HBase Issue Type: New Feature Components: regionserver Affects Versions: 3.0.0-alpha-4 Reporter: LiangJun He Assignee: LiangJun He Fix For: 3.0.0-alpha-4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HBASE-27444) Add tool commands list_enabled_tables and list_disabled_tables
[ https://issues.apache.org/jira/browse/HBASE-27444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629366#comment-17629366 ] LiangJun He commented on HBASE-27444: - [~zhangduo] OK, sir. I will start a new PR for branch-2. > Add tool commands list_enabled_tables and list_disabled_tables > -- > > Key: HBASE-27444 > URL: https://issues.apache.org/jira/browse/HBASE-27444 > Project: HBase > Issue Type: New Feature > Components: master >Affects Versions: 3.0.0-alpha-4 >Reporter: LiangJun He >Assignee: LiangJun He >Priority: Minor > > Currently, there is no command line tool to get the all enabled or disabled > tables, which can only be seen through the HMaster UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27444) Add tool commands list_enabled_tables and list_disabled_tables
[ https://issues.apache.org/jira/browse/HBASE-27444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LiangJun He updated HBASE-27444: Summary: Add tool commands list_enabled_tables and list_disabled_tables (was: Add tool commands list_disabled_tables and list_enabled_tables) > Add tool commands list_enabled_tables and list_disabled_tables > -- > > Key: HBASE-27444 > URL: https://issues.apache.org/jira/browse/HBASE-27444 > Project: HBase > Issue Type: New Feature > Components: master >Affects Versions: 3.0.0-alpha-4 >Reporter: LiangJun He >Assignee: LiangJun He >Priority: Minor > > Currently, there is no command line tool to get the all enabled or disabled > tables, which can only be seen through the HMaster UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27444) Add tool commands list_disabled_tables and list_enabled_tables
[ https://issues.apache.org/jira/browse/HBASE-27444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LiangJun He updated HBASE-27444: Description: Currently, there is no command line tool to get the all enabled or disabled tables, which can only be seen through the HMaster UI. (was: Currently, there is no command line tool to get the all disabled tables, which can only be seen through the HMaster UI.) > Add tool commands list_disabled_tables and list_enabled_tables > -- > > Key: HBASE-27444 > URL: https://issues.apache.org/jira/browse/HBASE-27444 > Project: HBase > Issue Type: New Feature > Components: master >Affects Versions: 3.0.0-alpha-4 >Reporter: LiangJun He >Assignee: LiangJun He >Priority: Minor > > Currently, there is no command line tool to get the all enabled or disabled > tables, which can only be seen through the HMaster UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27444) Add tool commands list_disabled_tables and list_enabled_tables
[ https://issues.apache.org/jira/browse/HBASE-27444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LiangJun He updated HBASE-27444: Summary: Add tool commands list_disabled_tables and list_enabled_tables (was: Add a tool command list_disabled_tables) > Add tool commands list_disabled_tables and list_enabled_tables > -- > > Key: HBASE-27444 > URL: https://issues.apache.org/jira/browse/HBASE-27444 > Project: HBase > Issue Type: New Feature > Components: master >Affects Versions: 3.0.0-alpha-4 >Reporter: LiangJun He >Assignee: LiangJun He >Priority: Minor > > Currently, there is no command line tool to get the all disabled tables, > which can only be seen through the HMaster UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HBASE-27448) Add an admin method to get replication enabled state
[ https://issues.apache.org/jira/browse/HBASE-27448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626361#comment-17626361 ] LiangJun He commented on HBASE-27448: - [~zhangduo] OK, sir. I will start a new PR for branch-2. > Add an admin method to get replication enabled state > > > Key: HBASE-27448 > URL: https://issues.apache.org/jira/browse/HBASE-27448 > Project: HBase > Issue Type: Improvement > Components: Admin, Client >Reporter: Duo Zhang >Assignee: LiangJun He >Priority: Major > > When implementing HBASE-27109, it is a bit surprise to me that there is no > way for me to get the enabled state of a replication peer directly through > Admin interface, I need to call listReplicationPeers to find out the > ReplicationPeerDescription and then get the enabled state. > I think we should add a method in Admin interface for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27444) Add a tool command list_disabled_tables
[ https://issues.apache.org/jira/browse/HBASE-27444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LiangJun He updated HBASE-27444: Description: Currently, there is no command line tool to get the all disabled tables, which can only be seen through the HMaster UI. (was: Currently, there is no command tool to get the all disabled tables, which can only be seen through the HMaster UI.) > Add a tool command list_disabled_tables > --- > > Key: HBASE-27444 > URL: https://issues.apache.org/jira/browse/HBASE-27444 > Project: HBase > Issue Type: New Feature > Components: master >Affects Versions: 3.0.0-alpha-4 >Reporter: LiangJun He >Assignee: LiangJun He >Priority: Minor > > Currently, there is no command line tool to get the all disabled tables, > which can only be seen through the HMaster UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
