[
https://issues.apache.org/jira/browse/HBASE-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
leizhang updated HBASE-24781:
-----------------------------
Description:
Supposed that we have an peer with id 1, when execute shell cmd disable_peer
'1' , then i can see the SizeOfLogQueue metric of all regionservers +1 ,
after 10 times disable_peer ops , it will increase to 11, and it will never
decrease to 1 in fulture .
I can see the function ReplicationSourceManager.refreshSources(peerId) called
, it will enqueue the current wals to the source , maybe when the current wal
is already in the replication queue , we try to add a duplicated wal to the
source ,which cause the same wal increase the SizeOfLogQueue metric twice ?
thx
was:
Supposed that we have an peer with id 1, when execute shell cmd disable_peer
'1' , then i can see the SizeOfLogQueue metric of all regionservers +1 ,
after 10 times disable_peer ops , it will increase to 11, and it will never
decrease to 1 in fulture .
I can see the function ReplicationSourceManager.refreshSources(peerId) called
, it will enqueue the current wals to the source , maybe when the current wal
is already in the replication queue , we try to add a duplicated wal to the
source ,which cause the same wal increase the SizeOfLogQueue twice ? thx
> [Replication] When execute shell cmd "disable_peer peerId"，the master web UI
> show a wrong number of SizeOfLogQueue
> -------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-24781
> URL: https://issues.apache.org/jira/browse/HBASE-24781
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Affects Versions: 2.2.5
> Reporter: leizhang
> Priority: Major
>
> Supposed that we have an peer with id 1, when execute shell cmd
> disable_peer '1' , then i can see the SizeOfLogQueue metric of all
> regionservers +1 , after 10 times disable_peer ops , it will increase to
> 11, and it will never decrease to 1 in fulture .
> I can see the function ReplicationSourceManager.refreshSources(peerId)
> called , it will enqueue the current wals to the source , maybe when the
> current wal is already in the replication queue , we try to add a duplicated
> wal to the source ,which cause the same wal increase the SizeOfLogQueue
> metric twice ? thx
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
