Re: [VOTE] Release ZooKeeper 3.3.1 (candidate 0)
With 6 +1's (3 PMC) and no -1's the vote passes. I'm working to publish the release and will send announcements as soon as that's done. Patrick On 05/13/2010 10:51 PM, Stack wrote: +1 I installed it under hbase cluster as a 5-node ensemble. Looks like it works like 3.3.0. Did some messing sending nc commands. No prob. St.Ack On Thu, May 13, 2010 at 4:52 PM, Mahadev Konar wrote: +1. Ran ant tests and some manual testing to bring up a cluster and run manual commands on the zookeeper cluster of 1,3, 5 nodes. Thanks Mahadev On 5/11/10 10:32 PM, "Patrick Hunt" wrote: +1, tests pass for me, also verified that nc/zktop worked properly on a real cluster (4letter word fix). Patrick On 05/07/2010 11:25 AM, Patrick Hunt wrote: I've created a candidate build for ZooKeeper 3.3.1. This is a bug fix release addressing seventeen issues (one critical) -- see the release notes for details. *** Please download, test and VOTE before the *** vote closes 11am pacific time, Wednesday, May 12.*** http://people.apache.org/~phunt/zookeeper-3.3.1-candidate-0/ Should we release this? Patrick
Re: [VOTE] Release ZooKeeper 3.3.1 (candidate 0)
+1 I installed it under hbase cluster as a 5-node ensemble. Looks like it works like 3.3.0. Did some messing sending nc commands. No prob. St.Ack On Thu, May 13, 2010 at 4:52 PM, Mahadev Konar wrote: > +1. > > Ran ant tests and some manual testing to bring up a cluster and run manual > commands on the zookeeper cluster of 1,3, 5 nodes. > > Thanks > Mahadev > > On 5/11/10 10:32 PM, "Patrick Hunt" wrote: > >> +1, tests pass for me, also verified that nc/zktop worked properly on a >> real cluster (4letter word fix). >> >> Patrick >> >> On 05/07/2010 11:25 AM, Patrick Hunt wrote: >>> I've created a candidate build for ZooKeeper 3.3.1. This is a bug fix >>> release addressing seventeen issues (one critical) -- see the release >>> notes for details. >>> >>> *** Please download, test and VOTE before the >>> *** vote closes 11am pacific time, Wednesday, May 12.*** >>> >>> http://people.apache.org/~phunt/zookeeper-3.3.1-candidate-0/ >>> >>> Should we release this? >>> >>> Patrick >>> >>> >>> >>> >>> > >
Re: [VOTE] Release ZooKeeper 3.3.1 (candidate 0)
+1. Ran ant tests and some manual testing to bring up a cluster and run manual commands on the zookeeper cluster of 1,3, 5 nodes. Thanks Mahadev On 5/11/10 10:32 PM, "Patrick Hunt" wrote: > +1, tests pass for me, also verified that nc/zktop worked properly on a > real cluster (4letter word fix). > > Patrick > > On 05/07/2010 11:25 AM, Patrick Hunt wrote: >> I've created a candidate build for ZooKeeper 3.3.1. This is a bug fix >> release addressing seventeen issues (one critical) -- see the release >> notes for details. >> >> *** Please download, test and VOTE before the >> *** vote closes 11am pacific time, Wednesday, May 12.*** >> >> http://people.apache.org/~phunt/zookeeper-3.3.1-candidate-0/ >> >> Should we release this? >> >> Patrick >> >> >> >> >>
Re: [VOTE] Release ZooKeeper 3.3.1 (candidate 0)
Looks like some diff in the errno reported in 10.4 (I'm on karmic and it passes): void testInvalidAddressString2() { const string INVALID_HOST("host1:+host:123"); zh=zookeeper_init(INVALID_HOST.c_str(),0,0,0,0,0); CPPUNIT_ASSERT(zh==0); ***CPPUNIT_ASSERT_EQUAL(ENOENT,errno); } 22 is EINVAL So this is fine for 3.3.1, but enter a JIRA to address it in the next release(s). Thanks! Patrick On 05/13/2010 08:19 AM, Andrei Savu wrote: All the Junit tests work as expected but I've got a failing test on the C client. I have attached the log messages. Is this an expected (accepted) error? I'm now running the tests on zookeeper 3.3.0. I'm testing on: Ubuntu 10.4 LTS Server Edition (64 bit) running inside VMWare Workstation on Windows7 $ java -version java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode) $ gcc -v Using built-in specs. Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.4.3-4ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-plugin --enable-objc-gc --disable-werror --with-arch-32=i486 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) On Wed, May 12, 2010 at 10:01 PM, Flavio Junqueira wrote: +1, works for me as well. -Flavio On May 12, 2010, at 7:58 PM, Benjamin Reed wrote: +1, things check out for me too. ben On 05/11/2010 11:19 PM, Henry Robinson wrote: +1, Java tests pass for me, as do Python ones. Henry On 11 May 2010 22:32, Patrick Huntwrote: +1, tests pass for me, also verified that nc/zktop worked properly on a real cluster (4letter word fix). Patrick On 05/07/2010 11:25 AM, Patrick Hunt wrote: I've created a candidate build for ZooKeeper 3.3.1. This is a bug fix release addressing seventeen issues (one critical) -- see the release notes for details. *** Please download, test and VOTE before the *** vote closes 11am pacific time, Wednesday, May 12.*** http://people.apache.org/~phunt/zookeeper-3.3.1-candidate-0/ Should we release this? Patrick
Re: [VOTE] Release ZooKeeper 3.3.1 (candidate 0)
All the Junit tests work as expected but I've got a failing test on the C client. I have attached the log messages. Is this an expected (accepted) error? I'm now running the tests on zookeeper 3.3.0. I'm testing on: Ubuntu 10.4 LTS Server Edition (64 bit) running inside VMWare Workstation on Windows7 $ java -version java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode) $ gcc -v Using built-in specs. Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.4.3-4ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-plugin --enable-objc-gc --disable-werror --with-arch-32=i486 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) On Wed, May 12, 2010 at 10:01 PM, Flavio Junqueira wrote: > +1, works for me as well. > > -Flavio > > On May 12, 2010, at 7:58 PM, Benjamin Reed wrote: > >> +1, things check out for me too. >> >> ben >> >> On 05/11/2010 11:19 PM, Henry Robinson wrote: >>> >>> +1, Java tests pass for me, as do Python ones. >>> >>> Henry >>> >>> On 11 May 2010 22:32, Patrick Hunt wrote: >>> >>> +1, tests pass for me, also verified that nc/zktop worked properly on a real cluster (4letter word fix). Patrick On 05/07/2010 11:25 AM, Patrick Hunt wrote: > I've created a candidate build for ZooKeeper 3.3.1. This is a bug fix > release addressing seventeen issues (one critical) -- see the release > notes for details. > > *** Please download, test and VOTE before the > *** vote closes 11am pacific time, Wednesday, May 12.*** > > http://people.apache.org/~phunt/zookeeper-3.3.1-candidate-0/ > > Should we release this? > > Patrick > > > > > > > >>> >>> >> > > -- Savu Andrei Website: http://www.andreisavu.ro/ [exec] make[1]: Leaving directory `/home/andrei/release/zookeeper-3.3.1/build/test/test-cppunit' [exec] ./zktest-st [exec] ZooKeeper server startedRunning [exec] Zookeeper_operations::testPing : elapsed 2 : OK [exec] Zookeeper_operations::testTimeoutCausedByWatches1 : elapsed 0 : OK [exec] Zookeeper_operations::testTimeoutCausedByWatches2 : elapsed 0 : OK [exec] Zookeeper_operations::testOperationsAndDisconnectConcurrently1 : elapsed 0 : OK [exec] Zookeeper_operations::testOperationsAndDisconnectConcurrently2 : elapsed 0 : OK [exec] Zookeeper_operations::testConcurrentOperations1 : elapsed 202 : OK [exec] Zookeeper_init::testBasic : elapsed 0 : OK [exec] Zookeeper_init::testAddressResolution : elapsed 0 : OK [exec] Zookeeper_init::testMultipleAddressResolution : elapsed 0 : OK [exec] Zookeeper_init::testNullAddressString : elapsed 0 : OK [exec] Zookeeper_init::testEmptyAddressString : elapsed 0 : OK [exec] Zookeeper_init::testOneSpaceAddressString : elapsed 0 : OK [exec] Zookeeper_init::testTwoSpacesAddressString : elapsed 0 : OK [exec] Zookeeper_init::testInvalidAddressString1 : elapsed 0 : OK [exec] Zookeeper_init::testInvalidAddressString2 : assertion : elapsed 10012 [exec] Zookeeper_init::testNonexistentHost : elapsed 57 : OK [exec] Zookeeper_init::testOutOfMemory_init : elapsed 0 : OK [exec] Zookeeper_init::testOutOfMemory_getaddrs1 : elapsed 0 : OK [exec] Zookeeper_init::testOutOfMemory_getaddrs2 : elapsed 0 : OK [exec] Zookeeper_init::testPermuteAddrsList : elapsed 0 : OK [exec] Zookeeper_close::testCloseUnconnected : elapsed 0 : OK [exec] Zookeeper_close::testCloseUnconnected1 : elapsed 0 : OK [exec] Zookeeper_close::testCloseConnected1 : elapsed 0 : OK [exec] Zookeeper_close::testCloseFromWatcher1 : elapsed 0 : OK [exec] Zookeeper_simpleSystem::testAsyncWatcherAutoReset ZooKeeper server started : elapsed 15025 : OK [exec] Zookeeper_simpleSystem::testDeserializeString : elapsed 0 : OK [exec] Zookeeper_watchers::testDefaultSessionWatcher1 : elapsed 0 : OK [exec] Zookeeper_watchers::testDefaultSessionWatcher2 : elapsed 0 : OK [exec] Zookeeper_watchers::testObjectSessionWatcher1 : elapsed 0 : OK [exec] Zookeeper_watchers::testObjectSessionWatcher2 : elapsed 202 : OK [exec] Zookeeper_watchers::testNodeWatcher1 : elapsed 407 : OK [exec] Zookeeper_watchers::testChildWatcher1 : elapsed 302 : OK [exec] Zookeeper_watchers::testChildWatcher2 : elapsed 303 : OK [exec] /home/andrei/release/zookeeper-3.
Re: [VOTE] Release ZooKeeper 3.3.1 (candidate 0)
+1, works for me as well. -Flavio On May 12, 2010, at 7:58 PM, Benjamin Reed wrote: +1, things check out for me too. ben On 05/11/2010 11:19 PM, Henry Robinson wrote: +1, Java tests pass for me, as do Python ones. Henry On 11 May 2010 22:32, Patrick Hunt wrote: +1, tests pass for me, also verified that nc/zktop worked properly on a real cluster (4letter word fix). Patrick On 05/07/2010 11:25 AM, Patrick Hunt wrote: I've created a candidate build for ZooKeeper 3.3.1. This is a bug fix release addressing seventeen issues (one critical) -- see the release notes for details. *** Please download, test and VOTE before the *** vote closes 11am pacific time, Wednesday, May 12.*** http://people.apache.org/~phunt/zookeeper-3.3.1-candidate-0/ Should we release this? Patrick
Re: [VOTE] Release ZooKeeper 3.3.1 (candidate 0)
+1, things check out for me too. ben On 05/11/2010 11:19 PM, Henry Robinson wrote: +1, Java tests pass for me, as do Python ones. Henry On 11 May 2010 22:32, Patrick Hunt wrote: +1, tests pass for me, also verified that nc/zktop worked properly on a real cluster (4letter word fix). Patrick On 05/07/2010 11:25 AM, Patrick Hunt wrote: I've created a candidate build for ZooKeeper 3.3.1. This is a bug fix release addressing seventeen issues (one critical) -- see the release notes for details. *** Please download, test and VOTE before the *** vote closes 11am pacific time, Wednesday, May 12.*** http://people.apache.org/~phunt/zookeeper-3.3.1-candidate-0/ Should we release this? Patrick
Re: [VOTE] Release ZooKeeper 3.3.1 (candidate 0)
+1, Java tests pass for me, as do Python ones. Henry On 11 May 2010 22:32, Patrick Hunt wrote: > +1, tests pass for me, also verified that nc/zktop worked properly on a > real cluster (4letter word fix). > > Patrick > > > On 05/07/2010 11:25 AM, Patrick Hunt wrote: > >> I've created a candidate build for ZooKeeper 3.3.1. This is a bug fix >> release addressing seventeen issues (one critical) -- see the release >> notes for details. >> >> *** Please download, test and VOTE before the >> *** vote closes 11am pacific time, Wednesday, May 12.*** >> >> http://people.apache.org/~phunt/zookeeper-3.3.1-candidate-0/ >> >> Should we release this? >> >> Patrick >> >> >> >> >> >> -- Henry Robinson Software Engineer Cloudera 415-994-6679
Re: [VOTE] Release ZooKeeper 3.3.1 (candidate 0)
+1, tests pass for me, also verified that nc/zktop worked properly on a real cluster (4letter word fix). Patrick On 05/07/2010 11:25 AM, Patrick Hunt wrote: I've created a candidate build for ZooKeeper 3.3.1. This is a bug fix release addressing seventeen issues (one critical) -- see the release notes for details. *** Please download, test and VOTE before the *** vote closes 11am pacific time, Wednesday, May 12.*** http://people.apache.org/~phunt/zookeeper-3.3.1-candidate-0/ Should we release this? Patrick
[VOTE] Release ZooKeeper 3.3.1 (candidate 0)
I've created a candidate build for ZooKeeper 3.3.1. This is a bug fix release addressing seventeen issues (one critical) -- see the release notes for details. *** Please download, test and VOTE before the *** vote closes 11am pacific time, Wednesday, May 12.*** http://people.apache.org/~phunt/zookeeper-3.3.1-candidate-0/ Should we release this? Patrick