Observer server log should contain INFO level logging on whether it's
getting a diff or getting a snapshot from leader. To estimate how long the
data transfer took, look for "UPTODATE" INFO level log on observer. This is
the message logged after data sync between leader and observer finished.
On W
Michael,
Thanks for your suggestions, so do you know how to find when it is taking
diff or full snapshot? in my case it looks like taking full snapshot. so
from observing leader to snapshotting is taking 30mins.
Ram
On May 16, 2017 2:07 PM, "Michael Han" wrote:
> When an observer (and in gener
Unsubscribe
Mike Richardson
Senior Software Engineer
*MoTuM N.V. | Dellingstraat 34 | B-2800 MECHELEN | Belgium*
T +32(0)15 28 16 63
M +41 7943 69538
www.motum.be
On 16 May 2017 at 23:07, Michael Han wrote:
> When an observer (and in general a follower) restarted, it will go through
>
When an observer (and in general a follower) restarted, it will go through
these stages:
* Look for leader by starting a new leader election round and usually this
is quick as there is already a leader.
* Register with leader and begin synchronize phase - depends on the
observer state the sync mig
With latency that high, I'd expect the thruput to be low, is 30m in line
with what it takes to transfer a gig of data across that pipe?
On Mon, May 15, 2017 at 4:19 PM, rammohan ganapavarapu <
rammohanga...@gmail.com> wrote:
> Hi,
>
> We have a zookeeper cluster in multi region, we have leader in
Hi,
We have a zookeeper cluster in multi region, we have leader in US EAST and
observers in US WEST, our data size is 1.3GB,network latency between leader
and observers is around 250ms, upon observer restart it is taking like
close to 30m for observer to serve traffic. Not sure why it's taking so
