wrong?
Michael Han 于2018年6月18日周一 下午12:28写道：
> Data synchronization is already done if the execution hits the zk.startup
> (note the previous while loop will only break if learner receives leaders
> up to date message).
>
> On Wed, Jun 13, 2018 at 10:51 PM, yuzhou li wrote:
>
&g
tted) {
fzk.logRequest(p.hdr, p.rec);
}
for(Long zxid: packetsCommitted) {
fzk.commit(zxid);
}
}
yuzhou li 于2018年6月14日周四 下午1:47写道：
>
> Hi,everyone.
>I git pull the tag release-3.5.4 from github. Before I read the
> 3.4.6 version code, I found 3.5.4 has so
Hi,everyone.
I git pull the tag release-3.5.4 from github. Before I read the
3.4.6 version code, I found 3.5.4 has some changes when the learner
synchronzied with leader.
If using DIFF way to synchronize histories, the follower or observer
will put the data in a queue, then start zkServer, then
tinguish tried epoch during election (acceptedEpoch) versus stable epoch
> (currentEpoch) after leader election to solve what's reported in ZK-335.
>
> On Sun, Jun 10, 2018 at 1:18 AM, yuzhou li wrote:
>
> > Hi everyone.I am a zk source code learner I have some confusion whe
Hi everyone.I am a zk source code learner I have some confusion when I
read the source code of zk leader failover phase.This phase has two epoch
acceptedEpoch and currentEpoch. But I don't understand why acceptEpoch is
needed instead of using currentEpoch directly?
