You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@zookeeper.apache.org by Kevin Verhoeven <ke...@amperity.com> on 2018/11/16 19:32:32 UTC
ZooKeeper 3.6.0 Release (fix for a large number of watches)
I am running Accumulo with a large number of tables (> 10k). Each table
sets up a number of watches in ZooKeeper, and we have many (> 50 million
watches). We are running 5 ZooKeeper servers and the watches are spread
evenly across the servers. We see Accumulo performance degrade sharply when
we add more than 6k tables and it appears this is related to the number of
watches in ZooKeeper. However, there seems to be a performance fix for a
large number of watches, in issue # 1177[1], that was resolved Aug 2018 and
merged into master with PR # 590 in release 3.6.0.
My question is how can I get the ZooKeeper 3.6.0 release? I'd like to
download a copy of the 3.6.0 jar and test with this version. If all goes
well, this will resolve my performance issue with Accumulo watches.
A second question would be: is there a way to tune ZooKeeper for better
performance with a large number of watches? This does not seem to be a
optimal running state for ZooKeeper, but we are constrained by Accumulo and
their use of watches.
[1] https://issues.apache.org/jira/browse/ZOOKEEPER-1177
[2] https://github.com/apache/zookeeper/pull/590
Regards,
Kevin
Re: ZooKeeper 3.6.0 Release (fix for a large number of watches)
Posted by Norbert Kalmar <nk...@cloudera.com.INVALID>.
Hi Kevin,
Unfortunately, 3.4 and 3.5 is in a feature freeze. You could ask the
community to backport this feature (vote on it), but personally I don't
think it will go through, sorry. It could be backported to first 3.5
release after stable (3.5.5 think). But were still talking months here,
possibly 3.5.5 would be ready at the same time 3.6 is.
The plan is to push 3.5 stable out ASAP, and do a 3.6 release very quick
after (6 months?).
Regards,
Norbert
On Fri, Nov 16, 2018 at 9:24 PM Kevin Verhoeven <ke...@amperity.com> wrote:
> Thanks Enrico,
>
> Would it be possible to backport the fix (PR # 590) into a previous
> version? For example, 3.4.x or 3.5.x? This could potentially release an
> important fix quicker.
>
> Kevin
>
> On Fri, Nov 16, 2018 at 12:52 PM Enrico Olivelli <eo...@gmail.com>
> wrote:
>
> > Kevin,
> > I guess there is no 3.6.0 very soon.
> > The community is working hard in order to release a 'stable' 3.5.x, then
> we
> > will go for 3.6.0.
> > I think any help I very appreciated to speed up the process.
> >
> > The others (like Facebook friends) on this list can talk about uses of
> > 3.6.0 in production.
> >
> > Just my 2c
> >
> > Enrico
> >
> > Il ven 16 nov 2018, 20:32 Kevin Verhoeven <ke...@amperity.com> ha
> scritto:
> >
> > > I am running Accumulo with a large number of tables (> 10k). Each table
> > > sets up a number of watches in ZooKeeper, and we have many (> 50
> million
> > > watches). We are running 5 ZooKeeper servers and the watches are spread
> > > evenly across the servers. We see Accumulo performance degrade sharply
> > when
> > > we add more than 6k tables and it appears this is related to the number
> > of
> > > watches in ZooKeeper. However, there seems to be a performance fix for
> a
> > > large number of watches, in issue # 1177[1], that was resolved Aug 2018
> > and
> > > merged into master with PR # 590 in release 3.6.0.
> > >
> > > My question is how can I get the ZooKeeper 3.6.0 release? I'd like to
> > > download a copy of the 3.6.0 jar and test with this version. If all
> goes
> > > well, this will resolve my performance issue with Accumulo watches.
> > >
> > > A second question would be: is there a way to tune ZooKeeper for better
> > > performance with a large number of watches? This does not seem to be a
> > > optimal running state for ZooKeeper, but we are constrained by Accumulo
> > and
> > > their use of watches.
> > >
> > > [1] https://issues.apache.org/jira/browse/ZOOKEEPER-1177
> > > [2] https://github.com/apache/zookeeper/pull/590
> > >
> > > Regards,
> > > Kevin
> > >
> > --
> >
> >
> > -- Enrico Olivelli
> >
>
Re: ZooKeeper 3.6.0 Release (fix for a large number of watches)
Posted by Kevin Verhoeven <ke...@amperity.com>.
Thanks Enrico,
Would it be possible to backport the fix (PR # 590) into a previous
version? For example, 3.4.x or 3.5.x? This could potentially release an
important fix quicker.
Kevin
On Fri, Nov 16, 2018 at 12:52 PM Enrico Olivelli <eo...@gmail.com>
wrote:
> Kevin,
> I guess there is no 3.6.0 very soon.
> The community is working hard in order to release a 'stable' 3.5.x, then we
> will go for 3.6.0.
> I think any help I very appreciated to speed up the process.
>
> The others (like Facebook friends) on this list can talk about uses of
> 3.6.0 in production.
>
> Just my 2c
>
> Enrico
>
> Il ven 16 nov 2018, 20:32 Kevin Verhoeven <ke...@amperity.com> ha scritto:
>
> > I am running Accumulo with a large number of tables (> 10k). Each table
> > sets up a number of watches in ZooKeeper, and we have many (> 50 million
> > watches). We are running 5 ZooKeeper servers and the watches are spread
> > evenly across the servers. We see Accumulo performance degrade sharply
> when
> > we add more than 6k tables and it appears this is related to the number
> of
> > watches in ZooKeeper. However, there seems to be a performance fix for a
> > large number of watches, in issue # 1177[1], that was resolved Aug 2018
> and
> > merged into master with PR # 590 in release 3.6.0.
> >
> > My question is how can I get the ZooKeeper 3.6.0 release? I'd like to
> > download a copy of the 3.6.0 jar and test with this version. If all goes
> > well, this will resolve my performance issue with Accumulo watches.
> >
> > A second question would be: is there a way to tune ZooKeeper for better
> > performance with a large number of watches? This does not seem to be a
> > optimal running state for ZooKeeper, but we are constrained by Accumulo
> and
> > their use of watches.
> >
> > [1] https://issues.apache.org/jira/browse/ZOOKEEPER-1177
> > [2] https://github.com/apache/zookeeper/pull/590
> >
> > Regards,
> > Kevin
> >
> --
>
>
> -- Enrico Olivelli
>
Re: ZooKeeper 3.6.0 Release (fix for a large number of watches)
Posted by Enrico Olivelli <eo...@gmail.com>.
Kevin,
I guess there is no 3.6.0 very soon.
The community is working hard in order to release a 'stable' 3.5.x, then we
will go for 3.6.0.
I think any help I very appreciated to speed up the process.
The others (like Facebook friends) on this list can talk about uses of
3.6.0 in production.
Just my 2c
Enrico
Il ven 16 nov 2018, 20:32 Kevin Verhoeven <ke...@amperity.com> ha scritto:
> I am running Accumulo with a large number of tables (> 10k). Each table
> sets up a number of watches in ZooKeeper, and we have many (> 50 million
> watches). We are running 5 ZooKeeper servers and the watches are spread
> evenly across the servers. We see Accumulo performance degrade sharply when
> we add more than 6k tables and it appears this is related to the number of
> watches in ZooKeeper. However, there seems to be a performance fix for a
> large number of watches, in issue # 1177[1], that was resolved Aug 2018 and
> merged into master with PR # 590 in release 3.6.0.
>
> My question is how can I get the ZooKeeper 3.6.0 release? I'd like to
> download a copy of the 3.6.0 jar and test with this version. If all goes
> well, this will resolve my performance issue with Accumulo watches.
>
> A second question would be: is there a way to tune ZooKeeper for better
> performance with a large number of watches? This does not seem to be a
> optimal running state for ZooKeeper, but we are constrained by Accumulo and
> their use of watches.
>
> [1] https://issues.apache.org/jira/browse/ZOOKEEPER-1177
> [2] https://github.com/apache/zookeeper/pull/590
>
> Regards,
> Kevin
>
--
-- Enrico Olivelli