-Re: [jira] [Resolved] (HBASE-8591) Doc Improvement: Replication blog
Himanshu Vashishtha 2013-05-22, 18:00
Since the source metrics would not be available in case the master cluster
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
On Wed, May 22, 2013 at 10:02 AM, N Dm <[EMAIL PROTECTED]> wrote:
> Stack and Himanshu,
> many thanks for putting this together. Particularly the info from
> Replication Metrics, whichs help a lot to understand the replication.
> A quick question on source.ageOfLastShippedOp. In the case that master
> cluster down, the user will like to know what the delta between master and
> slave. In another word, to find out the portion of mutation that already
> commit on Master, but haven't replicated yet. Is source.ageOfLastShippedOp
> the right place to look at? will it be available even with HBASE down?
> Again thanks for the doc and appreciate it.
> On Tue, May 21, 2013 at 10:39 PM, stack (JIRA) <[EMAIL PROTECTED]> wrote:
> > [
> > stack resolved HBASE-8591.
> > --------------------------
> > Resolution: Fixed
> > Fix Version/s: 0.98.0
> > Hadoop Flags: Reviewed
> > Committed to trunk. Thanks Himanshu (And Chris for review)
> > > Doc Improvement: Replication blog
> > > ---------------------------------
> > >
> > > Key: HBASE-8591
> > > URL: https://issues.apache.org/jira/browse/HBASE-8591
> > > Project: HBase
> > > Issue Type: Task
> > > Components: documentation, Replication
> > > Affects Versions: 0.95.0
> > > Reporter: Himanshu Vashishtha
> > > Assignee: Himanshu Vashishtha
> > > Fix For: 0.98.0
> > >
> > > Attachments: HBase-8591.patch, HBase-8591-v1.patch
> > >
> > >
> > > Add a section for source level metrics and some truth about table batch
> > ops at sink.
> > --
> > This message is automatically generated by JIRA.
> > If you think it was sent incorrectly, please contact your JIRA
> > administrators
> > For more information on JIRA, see: