Re: [3.4.12] Missing OVERSEER doc. solr-user@lucene....

k failures > across all three nodes. > > > > > > I **have the logs** from each of the Zookeepers. > > We are running 3.4.12. > > > > >

[3.4.12] Missing OVERSEER doc. solr-user@lucene....

instances of network failures across all three nodes. I *have the logs* from each of the Zookeepers. We are running 3.4.12.

zookeeper 3.4.12 c client doesnot work on solaris 11 machine

Hi team, I compiled zookeeper 3.4.12 c client on solaris 11 machine and trying to test it through cli.sh. Here is the sample code that I changed in cli.c. Whenever I run the ./cli_mt file it always throws below error 2018-08-08 09:49:44,437:18000(0x2):ZOO_ERROR@handle_socket_error_msg@1670

[ANNOUNCE] Apache ZooKeeper 3.4.12

The Apache ZooKeeper team is proud to announce Apache ZooKeeper version 3.4.12. ZooKeeper is a high-performance coordination service for distributed applications. It exposes common services - such as naming, configuration management, synchronization, and group services - in a simple interface

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

.@apache.org> wrote: > > > >> +1. sig/xsum verified, RAT ran OK. I tested a few operational scenarios > >> which seemed fine. Ran the tests and they passed. LGTM. > >> > >> Patrick > >> > >> On Mon, Mar 26, 2018 at 10:05 PM, Abraham F

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

; wrote: > >> +1. sig/xsum verified, RAT ran OK. I tested a few operational scenarios >> which seemed fine. Ran the tests and they passed. LGTM. >> >> Patrick >> >> On Mon, Mar 26, 2018 at 10:05 PM, Abraham Fine <af...@apache.org> wrote: >> >&

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

additional vote on the release. When that is > done > > it will be available. > > > > On Wed, Apr 18, 2018, at 12:38, Ted Yu wrote: > > > I don't see 3.4.12 artifact under > > > https://mvnrepository.com/artifact/org.apache.zookeeper/zookeeper > > > > > > Abr

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

onal vote on the release. When that is done > it will be available. > > On Wed, Apr 18, 2018, at 12:38, Ted Yu wrote: > > I don't see 3.4.12 artifact under > > https://mvnrepository.com/artifact/org.apache.zookeeper/zookeeper > > > > Abraham: > > Can you clarify ? > &

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

I'm waiting for one more additional vote on the release. When that is done it will be available. On Wed, Apr 18, 2018, at 12:38, Ted Yu wrote: > I don't see 3.4.12 artifact under > https://mvnrepository.com/artifact/org.apache.zookeeper/zookeeper > > Abraham: > Can you clarif

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

I don't see 3.4.12 artifact under https://mvnrepository.com/artifact/org.apache.zookeeper/zookeeper Abraham: Can you clarify ? Thanks On Mon, Apr 16, 2018 at 9:35 AM, Ted Yu <yuzhih...@gmail.com> wrote: > Hi, > If I understand correctly, zookeeper users can expect maven artifacts

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

Hi, If I understand correctly, zookeeper users can expect maven artifacts for 3.4.12 to be posted soon. Thanks

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

gt; well underway, has sufficient votes/time to finalize, this >> is not a>> regression in 3.4.12 and it's not yet committed I would think we >> finalize/push 3.4.12 then quickly followup with a 3.4.13 that >> addresses>> this. Alex could be the RM given his interest

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

at 2:26 PM, Patrick Hunt <ph...@apache.org> wrote: > Hey folks. I've been on vacation. My 0.02 - given the release candidate is > well underway, has sufficient votes/time to finalize, this is not a > regression in 3.4.12 and it's not yet committed I would think we > finalize/push 3

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

Hey folks. I've been on vacation. My 0.02 - given the release candidate is well underway, has sufficient votes/time to finalize, this is not a regression in 3.4.12 and it's not yet committed I would think we finalize/push 3.4.12 then quickly followup with a 3.4.13 that addresses this. Alex could

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

ssages > > reach > > > >>> the > > > >>> > > leader before participant's messages do. > > > >>> > > Whether its rare depends on the number of observers and > > > >>> participants. For > > > >>> > > example with very few participan

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

articipants and many observers > > >>> > > your chance of hitting this are quite high. > > >>> > > > > >>> > > Alex > > >>> > > > > >>> > > On Thu, Apr 5, 2018 at 11:44 AM, Andor Molnar < > an...@clou

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

our chance of hitting this are quite high. > >>> > > > >>> > > Alex > >>> > > > >>> > > On Thu, Apr 5, 2018 at 11:44 AM, Andor Molnar <an...@cloudera.com> > >>> > wrote: > >>> > > > >>> >

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

Hi, The PR for ZK-2959 already has +1. Can the PR be merged ? Thanks

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

> >>> > > > Maybe I'm missing something here, but this looks like a rare edge >>> case >>> > to >>> > > > me. Participants must finish the leader election successfully and >>> right >>> > > > after enou

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

il to send epoch to the leader, so >> > > > observers can take it over. >> > > > >> > > > Is that description accurate? >> > > > >> > > > Andor >> > > > >> > > > >> > > > On Thu, Apr 5, 2018

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

> > > > > > Is that description accurate? > > > > > > > > Andor > > > > > > > > > > > > On Thu, Apr 5, 2018 at 7:35 PM, Alexander Shraer <shra...@gmail.com> > > > > wrote: > > > > > > &

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 0

>> >> On Thu, Mar 22, 2018 at 1:05 PM, Abraham Fine <af...@apache.org> wrote: >> >>> This is a bugfix release candidate for 3.4.12. It fixes 22 issues, >>> including issues that >>> affect incorrect handling of the dataDir and the dataLogDir. >>> &g

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

hra...@gmail.com> > > > wrote: > > > > > > > To clarify - in a deployment with observers this bug can potentially > > > cause > > > > data loss. A server could be elected leader based just on the support > > of > > > > observers, even if this

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

gt; data loss. A server could be elected leader based just on the support > of > > > observers, even if this servers data is stale wrt other followers. > > > > > > It is certainly a blocker, just not sure if for 3.4.11 or 3.4.12. > > > > > > > > > Alex >

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

e > > data loss. A server could be elected leader based just on the support of > > observers, even if this servers data is stale wrt other followers. > > > > It is certainly a blocker, just not sure if for 3.4.11 or 3.4.12. > > > > > > Alex > > On Thu, Apr 5, 2018

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

> It is certainly a blocker, just not sure if for 3.4.11 or 3.4.12. > > > Alex > On Thu, Apr 5, 2018 at 10:29 AM Andor Molnar <an...@cloudera.com> wrote: > > > I don't think it's a blocker. > > The jira and PR has been open since last December and 3.4.11 has rele

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

To clarify - in a deployment with observers this bug can potentially cause data loss. A server could be elected leader based just on the support of observers, even if this servers data is stale wrt other followers. It is certainly a blocker, just not sure if for 3.4.11 or 3.4.12. Alex On Thu

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

I don't think it's a blocker. The jira and PR has been open since last December and 3.4.11 has released without it. Although this bug is also important to fix, I believe it's more important to release a fix for the regression we've found in 3.4.11 asap. Abe, any thoughts? Regards, Andor On

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

Sorry for coming in at the last moment. I'm not sure when the next 3.4 release is scheduled, so just wanted to mention this bug, which I believe is a blocker for either this or next release: https://issues.apache.org/jira/browse/ZOOKEEPER-2959 Best, Alex On Thu, Apr 5, 2018 at 9:09 AM, Ted Yu

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

Can the vote be closed ? It seems we have enough +1's Thanks

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

fied, RAT ran OK. I tested a few operational scenarios > which seemed fine. Ran the tests and they passed. LGTM. > > Patrick > > On Mon, Mar 26, 2018 at 10:05 PM, Abraham Fine <af...@apache.org> wrote: > > > This is a bugfix release candidate for 3.4.12. I

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

org> wrote: > +1. sig/xsum verified, RAT ran OK. I tested a few operational scenarios > which seemed fine. Ran the tests and they passed. LGTM. > > Patrick > > On Mon, Mar 26, 2018 at 10:05 PM, Abraham Fine <af...@apache.org> wrote: > > > This is a bugfix release c

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

+1. sig/xsum verified, RAT ran OK. I tested a few operational scenarios which seemed fine. Ran the tests and they passed. LGTM. Patrick On Mon, Mar 26, 2018 at 10:05 PM, Abraham Fine <af...@apache.org> wrote: > This is a bugfix release candidate for 3.4.12. It fixes 22 issues, &g

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

+1 checked signatures unit tests passed on Linux

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 1

+1 for candidate 1 - verified signatures - unit test passed on Mac and Ubuntu 16.04 (including c++) - verified 3 node cluster Andor On Tue, Mar 27, 2018 at 7:05 AM, Abraham Fine <af...@apache.org> wrote: > This is a bugfix release candidate for 3.4.12. It fixes 22 issues, > incl

[VOTE] Apache ZooKeeper release 3.4.12 candidate 1

This is a bugfix release candidate for 3.4.12. It fixes 22 issues, including issues that affect incorrect handling of the dataDir and the dataLogDir. This candidate fixes an issue in the release notes of candidate 0. The full release notes are available at: https://issues.apache.org/jira

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 0

2018 at 1:05 PM, Abraham Fine <af...@apache.org> wrote: > > > This is a bugfix release candidate for 3.4.12. It fixes 22 issues, > > including issues that > > affect incorrect handling of the dataDir and the dataLogDir. > > > > The full release notes

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 0

, 2018 at 1:05 PM, Abraham Fine <af...@apache.org> wrote: > This is a bugfix release candidate for 3.4.12. It fixes 22 issues, > including issues that > affect incorrect handling of the dataDir and the dataLogDir. > > The full release notes is available at: > > https://is

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 0

Hi Abe, Thanks for putting this important release together. +1 I've run the following tests: - verified signatures, - all unit tests passed on Mac (java only) and Ubuntu 16.04 (java & c++ successful), - tested standalone and 3-node cluster, - verified the fix & validation of datadir/logdir

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 0

-1 because release note is not correct. ZOOKEEPER-2948 and ZOOKEEPER-2806 should be included in release notes and corresponding JIRA needs update. Other than this, rc0 looks good. - verified xsum/sig - go through release notes. - verified cluster with different sizes. - verified with few 4lw

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 0

I just ran the test suite again - there was no test failure. So +1 from my side. On Fri, Mar 23, 2018 at 9:54 AM, Abraham Fine wrote: > Do they always fail when run with the rest of the test suite or is it > inconsistent? > > The reason I ask is that the failure you are

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 0

Do they always fail when run with the rest of the test suite or is it inconsistent? The reason I ask is that the failure you are reporting is a ConnectionLoss and testSessionTimeout has a history of being flaky (generally on ZooKeeper 3.5 though). On Fri, Mar 23, 2018, at 09:45, Ted Yu

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 0

Here is OS: Linux h.com 3.10.0-327.28.3.el7.x86_64 #1 SMP Thu Aug 18 19:05:49 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux java version "1.8.0_161" Java(TM) SE Runtime Environment (build 1.8.0_161-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode) The tests don't fail when run

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 0

Hi Ted- Thanks for running the test cases on the RC. I am not able to reproduce the failures. Would you mind telling us a little bit more about the environment you are running the tests in (operating system, jvm)? In addition, to the failures occur every time you run the tests or just

Re: [VOTE] Apache ZooKeeper release 3.4.12 candidate 0

Hi, I ran test suite for the RC. Testcase: testSessionTimeout took 22.686 sec Caused an ERROR KeeperErrorCode = ConnectionLoss for /stest org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /stest at

[VOTE] Apache ZooKeeper release 3.4.12 candidate 0

This is a bugfix release candidate for 3.4.12. It fixes 22 issues, including issues that affect incorrect handling of the dataDir and the dataLogDir. The full release notes is available at: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801=12342040 *** Please

Re: 3.4.12

+1 for cutting a 3.4.12 RC. Thanks for volunteering, Abe. -Flavio > On 8 Mar 2018, at 18:53, Rakesh Radhakrishnan <rake...@apache.org> wrote: > > Appreciate Abe for the initiative and efforts! > > +1, for "3.4.12" releasing. > > Please feel free to p

Re: 3.4.12

Appreciate Abe for the initiative and efforts! +1, for "3.4.12" releasing. Please feel free to ping me if any help needed when making this release. Regards, Rakesh On Sat, Mar 3, 2018 at 4:19 AM, Abraham Fine <af...@apache.org> wrote: > I am very much interested in taking a

Re: 3.4.12

1, 2018 at 4:38 PM, Andor Molnar <an...@cloudera.com> wrote: > > > > > > > Hi dev, > > > > > > > > User has recently run into the regression of 3.4.11 (ZOOKEEPER-2960 > > > > <https://issues.apache.org/jira/browse/ZOOKEEPER-2960>) (again?) > > > > Are we good to cut 3.4.12 soon or still waiting for something to be > > > > committed? > > > > > > > > Andor > > > > > >

Re: 3.4.12

; Patrick > > > > On Thu, Mar 1, 2018 at 4:38 PM, Andor Molnar <an...@cloudera.com> wrote: > > > > > Hi dev, > > > > > > User has recently run into the regression of 3.4.11 (ZOOKEEPER-2960 > > > <https://issues.apache.org/jira/browse/ZOOKEEPER-2960>) (again?) > > > Are we good to cut 3.4.12 soon or still waiting for something to be > > > committed? > > > > > > Andor > > > >

Re: 3.4.12

ER-2960 > > <https://issues.apache.org/jira/browse/ZOOKEEPER-2960>) (again?) > > Are we good to cut 3.4.12 soon or still waiting for something to be > > committed? > > > > Andor > >

Re: 3.4.12

as RM? Patrick On Thu, Mar 1, 2018 at 4:38 PM, Andor Molnar <an...@cloudera.com> wrote: > Hi dev, > > User has recently run into the regression of 3.4.11 (ZOOKEEPER-2960 > <https://issues.apache.org/jira/browse/ZOOKEEPER-2960>) (again?) > Are we good to cut 3.4.12 soon or

3.4.12

Hi dev, User has recently run into the regression of 3.4.11 (ZOOKEEPER-2960 <https://issues.apache.org/jira/browse/ZOOKEEPER-2960>) (again?) Are we good to cut 3.4.12 soon or still waiting for something to be committed? Andor