+Unique+Naming
> > > > [4]: https://issues.apache.org/jira/browse/ZOOKEEPER-4332
> > > > [5]:
> > > >
> >
> https://bookkeeper.apache.org/docs/getting-started/concepts/#hierarchical-ledger-manager
> > > > [6]: https://issues.apache.org/jira/br
gt; > Kezhu Wang
> > >
> > >
> > > On Fri, Jun 16, 2023 at 11:33 AM Josef Roehrl
> > > wrote:
> > > >
> > > > I wanted to add 2 things.
> > > >
> > > >
> > > > 1. Increasing to a 64-bit counter certainly so
; >
> > > >
> > > > 1. Increasing to a 64-bit counter certainly solves the problem,
> but
> > > this might require conversion of zk data when the current counter is
> stored
> > > as 32-bit
> > > > 2. A client that relies on a
ient that relies on a unique version that it uses as a
> > reference outside of zk should verify that a version that it receives does
> > not already exist outside zk. This applies even if 1. is considered, should
> > a zk quorum be reset or lose its data.
> > >
> > >
https://fuseforward.com/?utm_source=Email%20Signature&utm_medium=email%20signature&utm_campaign=email%20signature>
> | Newsletter<
> https://fuseforward.com/subscribe-to-our-newsletter/?utm_source=Email%20Signature&utm_medium=Email%20Signature&utm_campaign=Email%20Signature&g
> |
> Newsletter<https://fuseforward.com/subscribe-to-our-newsletter/?utm_source=Email%20Signature&utm_medium=Email%20Signature&utm_campaign=Email%20Signature>
> | Twitter<https://twitter.com/fuseforward> |
> LinkedIn<https://www.linkedin.com/company/fuseforward/?ori
, 2023 6:53 PM
To: dev@zookeeper.apache.org
Subject: Re: Name of sequence node is not unique
The invariant is that the value should be increasing except in failure
modes. You found a somewhat surprising failure mode.
Please compute how long it would take for a 64-bit counter to overflow if
increment
The invariant is that the value should be increasing except in failure
modes. You found a somewhat surprising failure mode.
Please compute how long it would take for a 64-bit counter to overflow if
incremented a million times per second. (hint, half a million years).
Remember that zk only does thi
Thanks a lot for your inputs, Ted.
On Thu, Jun 15, 2023 at 2:52 PM Ted Dunning wrote:
> Breaking a semantic invariant is a dangerous solution here.
Totally agree. We should not break a semantic invariant if there is one.
What's the semantic invariant here and how ZK is supposed to behave in the
Breaking a semantic invariant is a dangerous solution here. It would be
better to use a longer integer.
On Thu, Jun 15, 2023, 13:35 Li Wang wrote:
> Thanks for the response, Enrico.
>
> Please see comments below.
>
> On Thu, Jun 15, 2023 at 5:47 AM Enrico Olivelli
> wrote:
>
> > Li,
> > thank
Thanks for the response, Enrico.
Please see comments below.
On Thu, Jun 15, 2023 at 5:47 AM Enrico Olivelli wrote:
> Li,
> thanks for reporting your problem.
>
> Most likely you have found a bug.
>
> I have one question, related to your use case,
> is the problem that the numbers are not "uniqu
Li,
thanks for reporting your problem.
Most likely you have found a bug.
I have one question, related to your use case,
is the problem that the numbers are not "unique" or that the number is
not monotonically increasing ?
Do you have 2147483647 concurrent sessions and you found that two
sessions
Hello,
We are running 3.7.1 in production and running into an "issue" that the
names of sequence nodes are not unique after the counter hits the max int
(i.e 2147483647) and overflows. I would like to start a thread to discuss
the following
1. Is this a bug or "expected" behavior?
2. Is ZK suppo
13 matches
Mail list logo
