phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mujtaba Chohan <mujt...@apache.org>
Subject Re: How to tell when an insertion has "finished"
Date Thu, 28 Jul 2016 23:02:35 GMT
Oh sorry I thought OP was referring to HDFS level replication.

On Thu, Jul 28, 2016 at 3:48 PM, James Taylor <jamestaylor@apache.org>
wrote:

> I believe you can also measure the depth of the replication queue to know
> what's pending. HBase replication is asynchronous, so you're right that
> Phoenix would return while replication may still be occurring.
>
> On Thu, Jul 28, 2016 at 12:06 PM, Mujtaba Chohan <mujtaba@apache.org>
> wrote:
>
>> Query running first time would be slower since data is not in HBase cache
>> rather than things being not settled. Replication shouldn't be putting load
>> on cluster which you can check by turning replication off. On HBase side to
>> force things to be optimal before running perf queries is to do a major
>> compaction and wait for compaction to complete.
>>
>> - mujtaba
>>
>> On Thu, Jul 28, 2016 at 8:09 AM, Heather, James (ELS) <
>> james.heather@elsevier.com> wrote:
>>
>>> If you upsert lots of rows into a table, presumably Phoenix will return
>>> as soon as HBase has received the data, but before the data has been
>>> replicated?
>>>
>>>
>>> Is there a way to tell when everything has "settled", i.e., when
>>> everything has finished replicating or whatever it needs to do?
>>>
>>>
>>> The reason I ask is that this might affect our benchmarking. If we add
>>> lots of rows, and then run some sample queries straight away, they might
>>> return more slowly initially, if the replication is still taking place.
>>>
>>>
>>> (Does this make sense? I'm not completely clear on how HBase replication
>>> works anyway.)
>>>
>>>
>>> James
>>>
>>> ------------------------------
>>>
>>> Elsevier Limited. Registered Office: The Boulevard, Langford Lane,
>>> Kidlington, Oxford, OX5 1GB, United Kingdom, Registration No. 1982084,
>>> Registered in England and Wales.
>>>
>>
>>
>

Mime
View raw message