[
https://issues.apache.org/jira/browse/HBASE-16938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624262#comment-15624262
]
Heng Chen commented on HBASE-16938:
-----------------------------------
The patch looks OK to me. It extracts the updater to be one tool, so we could
run it alone and no harm to current logic. :)
> 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
> Attachments: 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)
