You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Michael Stack (Jira)" <ji...@apache.org> on 2020/01/03 05:15:00 UTC
[jira] [Updated] (HBASE-23098) [bulkload] If one of the peers in a
cluster is configured with NAMESPACE level, its hfile-refs(zk) will be
backlogged
[ https://issues.apache.org/jira/browse/HBASE-23098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Stack updated HBASE-23098:
----------------------------------
Fix Version/s: 2.3.0
3.0.0
Hadoop Flags: Reviewed
Resolution: Fixed
Status: Resolved (was: Patch Available)
Merged to master and branch-2. Shout if need it elsewhere [~yiran].
> [bulkload] If one of the peers in a cluster is configured with NAMESPACE level, its hfile-refs(zk) will be backlogged
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-23098
> URL: https://issues.apache.org/jira/browse/HBASE-23098
> Project: HBase
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Yiran Wu
> Assignee: Yiran Wu
> Priority: Major
> Fix For: 3.0.0, 2.3.0
>
> Attachments: HBASE-23098.v0.patch, HBASE-23098.v1.patch
>
>
> If one of the peers in a cluster is configured with NAMESPACE level, its hfile-refs(zk) will be backlogged.
> We have three tables in the cluster and table name is
> ns1:test
> default:table1
> default:bulkload
> and this Cluster have three peers
> {code:java}
> add_peer 's1', CLUSTER_KEY => "cluster1:2181:/hbase"
> add_peer 's2', CLUSTER_KEY => "cluster2:2181:/hbase", TABLE_CFS => \{ "table1" => [] }
> add_peer 's3', CLUSTER_KEY => "cluster3:2182:/hbase-prod", NAMESPACES => ["ns1"]
> {code}
> ns1's hfile-refs backlogged when we bulk load files to the default:bulkload
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)