On Wed, Sep 26, 2012 at 10:42 AM, Eugene Koontz <[email protected]> wrote: > On 9/26/12 9:56 AM, Andrew Purtell wrote: >> >> Hi Pat, >> >> We didn't take up the changes from ZOOKEEPER-1497 yet and I believe we are >> still checking the existence of a system property to determine if SASL is >> configured. Eugene could confirm. Anyhow we have been testing with Oracle >> JRE 7 (u4 I believe was the most recent) so it seems we've had no exposure >> to ZOOKEEPER-1550 and tests have all been good. >> >> Before ZOOKEEPER-1437 went in, when starting secure HBase regionservers up >> on EC2 test clusters, at one point most of the time they would lose the >> race, fail to authenticate, and abort. This was different from results on >> earlier versions (of HBase and from 3.4 branch), but because that timing >> problem was latent only then. > > > Hi Pat and Andy and all ZK devs, > Andy is right; we had a lot of problems with test failures after merging > ZOOKEEPER-1497, so we removed this fix (ZOOKEEPER-1497) from our branch. So > we still reply on checking the system property to determine whether SASL is > configured. I'll be looking at all of these problems in 3.4.4 today. > -Eugene >
I didn't notice any feedback to the list on these issues, perhaps I missed it? 1437 definitely has some issue though - I just noticed this on jenkins: https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk-jdk7/ Seems the build started failing when 1437 was introduced (sep10). 1497 went in earlier (aug 29th) w/o any issues in terms of jdk7 unit tests. https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk-jdk7/changes Perhaps we're missing some tests on 1497 that trigger the issue you saw? Would be great to add a test for that. Thanks Eugene/Andrew! Patrick
