[
https://issues.apache.org/jira/browse/HBASE-20193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jingyun Tian updated HBASE-20193:
---------------------------------
Release Note:
After HBASE-20193, we added 2 parts to master's web page.
One is Peers that shows all replication peers and some of their configurations,
like peer id, cluster key, state, bandwidth, and which namespace or table it
will replicate.
The other one is replication status of all regionservers, we added a tab to
region servers division, then we can check the replication delay of all region
servers for any peer. This table shows AgeOfLastShippedOp, SizeOfLogQueue and
ReplicationLag for each regionserver and the table is sort by ReplicationLag in
descending order. By this way we can easily find the problematic region server.
If the replication delay is UNKNOWN, that means this walGroup doesn't start
replicate yet and it may get disabled. ReplicationLag will update once this
peer start replicate.
> Basic Replication Web UI - Regionserver
> ----------------------------------------
>
> Key: HBASE-20193
> URL: https://issues.apache.org/jira/browse/HBASE-20193
> Project: HBase
> Issue Type: Sub-task
> Components: Replication, Usability
> Reporter: Jingyun Tian
> Assignee: Jingyun Tian
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: HBASE-20193.master.001.patch,
> HBASE-20193.master.002.patch, HBASE-20193.master.003.patch,
> HBASE-20193.master.004.patch, HBASE-20193.master.004.patch,
> HBASE-20193.master.005.patch, HBASE-20193.master.006.patch,
> HBASE-20193.master.006.patch, HBASE-20193.master.007.patch,
> HBASE-20193.master.008.patch, HBASE-20193.master.009.patch
>
>
> subtask of HBASE-15809. Implementation of replication UI on Regionserver web
> page.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
