hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Saad Mufti <saad.mu...@gmail.com>
Subject Re: HBase 1.0 Per Put TTL Not Being Obeyed On Replication
Date Fri, 28 Apr 2017 17:06:29 GMT
Thanks for the feedback, I have confirmed that in both the main and replica
cluster, hbase.replication.rpc.codec is set to:


I have also run a couple of tests and it looks like the TTL is not being
obeyed on the replica for any entry. Almost as if the TTL cell tags are not
being replicated. I couldn't find any significant clock skew. If it
matters, the HBase version on both sides is 1.0.0-cdh5.5.2

Any ideas?



On Thu, Apr 27, 2017 at 3:24 AM, Anoop John <anoop.hbase@gmail.com> wrote:

> Ya can u check whether the replica cluster is NOT removing ANY of the
> TTL expired cells (as per ur expectation from master cluster) or some.
> Is there too much clock time skew for the source RS and peer cluster
> RS? Just check.
> BTW can u see what is the hbase.replication.rpc.codec configuration
> value in both clusters?
> -Anoop-
> On Thu, Apr 27, 2017 at 2:08 AM, Saad Mufti <saad.mufti@gmail.com> wrote:
> > Hi,
> >
> > I have a main HBase 1.x cluster and some of the tables are being
> replicated
> > to a separate HBase cluster of the same version, and the table schemas
> are
> > identical. The column family being used has TTL set to "FOREVER", but we
> do
> > a per put TTL in every Put we issue on the main cluster.
> >
> > Data is being replicated but we recently caught a number of data items
> that
> > have disappeared in the main cluster as expected based on their TTL but
> not
> > in the replica. Both HBase clusters have hfile.format.version set to 3 so
> > TTL tags should be obeyed. I haven't checked yet whether it is a case of
> > the replica not obeying ANY TTL's or just some.
> >
> > Before we dig deeper, I was hoping someone in the community would point
> it
> > out if we have missed any obvious gotchas.
> >
> > Thanks.
> >
> > -------
> > Saad

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message