Understood! I really appreciate your explanation.
Yan, Zheng 于2020年4月17日周五 下午3:11写道：
>
> On Fri, Apr 17, 2020 at 10:23 AM Xinying Song
> wrote:
> >
> > Hi, Yan:
> > I agree with the idea that log event can be used to reconstruct cache
> > when crash happens. But master can reconstruct its
Hi, Yan:
I agree with the idea that log event can be used to reconstruct cache
when crash happens. But master can reconstruct its cache by replaying
its EUpdate logevent. The ESlaveUpdate::OP_COMMIT log event seems to
have nothing to do with cache of master, it's on slave. Besides, that
log event
On Wed, Apr 15, 2020 at 9:40 AM Xinying Song wrote:
>
> Hi, Greg:
> Thanks for your reply!
> I think master can always know if a request has been finished or not
> no matter whether
> there is a Commit-logevent, because it has written a EUpdate logevent
> that records the
> unfinished request.
>
Hi, Greg:
Thanks for your reply!
I think master can always know if a request has been finished or not
no matter whether
there is a Commit-logevent, because it has written a EUpdate logevent
that records the
unfinished request.
Of course, we need to do commit, in which we clean up mdcache and
On Sun, Apr 12, 2020 at 5:19 AM Xinying Song wrote:
>
> Hi, cephers:
> What's the purpose of using LogEvent with empty metablob?
> For example in link/unlink operation cross two active mds,
> when slave receives OP_FINISH it will write an ESlaveUpdate::OP_COMMIT
> to the journal, then
> send
