hi,
thanks for explanation!
YAMAMOTO Takashi
> Hi,
>
> It's intentional. Originally the code only used nodeid, but there was a
> problem with ownership change so we fixed it by adding the timestamp.
>
> The issue we found goes like this, if nodeA is originally in the preflistt,
> after a few
Hi,
It's intentional. Originally the code only used nodeid, but there was a
problem with ownership change so we fixed it by adding the timestamp.
The issue we found goes like this, if nodeA is originally in the preflistt,
after a few updates you would have a vclock of Vclock1=[{nodea,3}].
Owners
hi,
vnodeid is composed from nodeid and timestamp.
because of the second-precision of the timestamp, many of vnodes in
a physical node can share the same vnodeid. is this an intentional
behaviour or a bug? i wonder if it doesn't affect the vclock algorithm.
YAMAMOTO Takashi
___
