hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16938) TableCFsUpdater maybe failed due to no write permission on peerNode
Date Fri, 11 Nov 2016 03:46:58 GMT

    [ https://issues.apache.org/jira/browse/HBASE-16938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15656030#comment-15656030
] 

Hudson commented on HBASE-16938:
--------------------------------

ABORTED: Integrated in Jenkins build HBase-1.4 #528 (See [https://builds.apache.org/job/HBase-1.4/528/])
HBASE-16938 TableCFsUpdater maybe failed due to no write permission on (enis: rev a6397e3b0c5a9c938c0a00cb5d3cd762d498afd1)
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/replication/master/TableCFsUpdater.java


> TableCFsUpdater maybe failed due to no write permission on peerNode
> -------------------------------------------------------------------
>
>                 Key: HBASE-16938
>                 URL: https://issues.apache.org/jira/browse/HBASE-16938
>             Project: HBase
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 2.0.0, 1.4.0
>            Reporter: Guanghao Zhang
>            Assignee: Guanghao Zhang
>             Fix For: 2.0.0, 1.4.0
>
>         Attachments: HBASE-16938.patch, HBASE-16938.patch
>
>
> After HBASE-11393, replication table-cfs use a PB object. So it need copy the old string
config to new PB object when upgrade cluster. In our use case, we have different kerberos
for different cluster, etc. online serve cluster and offline processing cluster. And we use
a unify global admin kerberos for all clusters. The peer node is created by client. So only
global admin has the write  permission for it. When upgrade cluster, HMaster doesn't has the
write permission on peer node, it maybe failed to copy old table-cfs string to new PB Object.
I thought it need a tool for client to do this copy job.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message