Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # user >> HBase Replication ageOfLastShippedOp


Copy link to this message
-
Re: HBase Replication ageOfLastShippedOp
The problem is that when the recovered edits log is done processing
(Replicating) (queue = 0), the metrics still reports its
agetOfLastShippedOp instead of the current live active log, which seems
like a bug.

On Tue, Jun 18, 2013 at 9:55 PM, Elliott Clark <[EMAIL PROTECTED]> wrote:

> On Tue, Jun 18, 2013 at 1:09 AM, Asaf Mesika <[EMAIL PROTECTED]>
> wrote:
>
> > Does HBase Region Server arbitrarily chooses which one to publish to its
> >
>
> The metrics reports the last source to report in.  So for recovered edits
> since it will probably have higher throughput than the live log, you'll
> more often see that value.  In trunk and 0.95/0.96 this has been fixed and
> every source exposes it's own ageOfLastShippedLog as well as one global
> one.
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB