Since the source metrics would not be available in case the master cluster
is down,
your best bet would be sink.ageOfLastAppliedOp at the slave cluster.
Its value is the timestamp of the last WALEdit that is applied to the
slave.
On Wed, May 22, 2013 at 10:02 AM, N Dm nid...@gmail.com wrote:
Himanshu,
Thanks a lot. Your suggestion saved me a lot of time if have to figure it out
myself
Demai on the run
On May 22, 2013, at 11:00 AM, Himanshu Vashishtha hv.cs...@gmail.com wrote:
Since the source metrics would not be available in case the master cluster
is down,
your best bet
Hi Himanshu,
I have a follow up question on these metrics. I see that both these metrics
basically diff against the timestamp of the WALEdit. The timestamp on the
WALEdit is generated by the region server in source cluster. So if there is
some clock skew (even 1 second) on the slave cluster, the
[
https://issues.apache.org/jira/browse/HBASE-8591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-8591.
--
Resolution: Fixed
Fix Version/s: 0.98.0
Hadoop Flags: Reviewed
Committed to trunk. Thanks
