You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Maddineni Sukumar (JIRA)" <ji...@apache.org> on 2017/02/07 20:08:41 UTC
[jira] [Updated] (HBASE-17610) Replication source ageOfLastShipped
value not updated properly in below scenarios
[ https://issues.apache.org/jira/browse/HBASE-17610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maddineni Sukumar updated HBASE-17610:
--------------------------------------
Description:
AgeOfLastShipped value not updated properly when CrossRealm trust is broken between primary and its peer cluster(Secured clusters).
1. Region Server running and cross realm trust broken
2. Cross realm broken and then RegionServer restarted
was:
For every client connect call to RS we are logging below log line in DEBUG mode which is causing too many logs in RegionServer.
2017-01-18 17:51:40,739 DEBUG [.reader=4,port=60020] security.HBaseSaslRpcServer - SASL server GSSAPI callback: setting canonicalized client ID: hbase/hostname-xxx@KDC
> Replication source ageOfLastShipped value not updated properly in below scenarios
> ---------------------------------------------------------------------------------
>
> Key: HBASE-17610
> URL: https://issues.apache.org/jira/browse/HBASE-17610
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 1.2.4, 1.1.8
> Reporter: Maddineni Sukumar
> Assignee: Maddineni Sukumar
> Priority: Minor
> Labels: easyfix
> Fix For: 2.0.0, 1.4.0, 1.3.1, 1.2.5, 1.1.9
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> AgeOfLastShipped value not updated properly when CrossRealm trust is broken between primary and its peer cluster(Secured clusters).
> 1. Region Server running and cross realm trust broken
> 2. Cross realm broken and then RegionServer restarted
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)