[jira] [Reopened] (SOLR-12727) Upgrade ZooKeeper dependency to 3.4.13
[
https://issues.apache.org/jira/browse/SOLR-12727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man reopened SOLR-12727:
-
There's a big uptick in SaslZkACLProviderTest failures from [~thetaphi]'s
jenkins server (that i can't reproduce locally) lately that i think is caused
by this ZK upgrade?
Here's an example of what a "good" run looks like on my laptop (hostname
"tray")...
{noformat}
[junit4] Started J0 PID(995@tray).
[junit4] Suite: org.apache.solr.cloud.SaslZkACLProviderTest
[junit4] 2> Creating dataDir:
/home/hossman/lucene/alt_dev/solr/build/solr-core/test/J0/temp/solr.cloud.SaslZkACLProviderTest_B413507B747C128B-001/init-core-data-001
[junit4] 2> 1846 INFO
(SUITE-SaslZkACLProviderTest-seed#[B413507B747C128B]-worker) []
o.a.s.SolrTestCaseJ4 Using PointFields (NUMERIC_POINTS_SYSPROP=true)
w/NUMERIC_DOCVALUES_SYSPROP=true
[junit4] 2> 1896 INFO
(SUITE-SaslZkACLProviderTest-seed#[B413507B747C128B]-worker) [] o.e.j.u.log
Logging initialized @1929ms to org.eclipse.jetty.util.log.Slf4jLog
[junit4] 2> 1904 INFO
(SUITE-SaslZkACLProviderTest-seed#[B413507B747C128B]-worker) []
o.a.s.SolrTestCaseJ4 Randomized ssl (false) and clientAuth (true) via:
@org.apache.solr.util.RandomizeSSL(reason=, ssl=NaN, value=NaN, clientAuth=NaN)
[junit4] 2> 1912 INFO
(SUITE-SaslZkACLProviderTest-seed#[B413507B747C128B]-worker) []
o.a.s.SolrTestCaseJ4 SecureRandom sanity checks:
test.solr.allowed.securerandom=null & java.security.egd=file:/dev/./urandom
[junit4] 2> 1930 INFO
(TEST-SaslZkACLProviderTest.testSaslZkACLProvider-seed#[B413507B747C128B]) [
] o.a.s.SolrTestCaseJ4 ###Starting testSaslZkACLProvider
[junit4] 2> 1931 INFO
(TEST-SaslZkACLProviderTest.testSaslZkACLProvider-seed#[B413507B747C128B]) [
] o.a.s.c.SaslZkACLProviderTest SETUP_START testSaslZkACLProvider
[junit4] 2> 1931 INFO
(TEST-SaslZkACLProviderTest.testSaslZkACLProvider-seed#[B413507B747C128B]) [
] o.a.s.c.SaslZkACLProviderTest ZooKeeper
dataDir:/home/hossman/lucene/alt_dev/solr/build/solr-core/test/J0/temp/solr.cloud.SaslZkACLProviderTest_B413507B747C128B-001/tempDir-002/zookeeper/server1/data
[junit4] 2> 7348 WARN
(TEST-SaslZkACLProviderTest.testSaslZkACLProvider-seed#[B413507B747C128B]) [
] o.a.d.s.c.DefaultDirectoryService You didn't change the admin password of
directory service instance 'DefaultKrbServer'. Please update the admin
password as soon as possible to prevent a possible security breach.
[junit4] 2> 7953 INFO
(TEST-SaslZkACLProviderTest.testSaslZkACLProvider-seed#[B413507B747C128B]) [
] o.a.s.c.ZkTestServer STARTING ZK TEST SERVER
[junit4] 2> 7956 INFO (ZkTestServer Run Thread) []
o.a.s.c.ZkTestServer client port:0.0.0.0/0.0.0.0:0
[junit4] 2> 7956 INFO (ZkTestServer Run Thread) []
o.a.s.c.ZkTestServer Starting server
[junit4] 2> 8457 INFO
(TEST-SaslZkACLProviderTest.testSaslZkACLProvider-seed#[B413507B747C128B]) [
] o.a.s.c.ZkTestServer start zk server on port:59021
[junit4] 2> 8462 INFO
(TEST-SaslZkACLProviderTest.testSaslZkACLProvider-seed#[B413507B747C128B]) [
] o.a.s.c.ZkTestServer parse host and port list: 127.0.0.1:59021
[junit4] 2> 8463 INFO
(TEST-SaslZkACLProviderTest.testSaslZkACLProvider-seed#[B413507B747C128B]) [
] o.a.s.c.ZkTestServer connecting to 127.0.0.1 59021
[junit4] 2> 8682 INFO (zkConnectionManagerCallback-3-thread-1) []
o.a.s.c.c.ConnectionManager zkClient has connected
[junit4] 2> 8703 INFO (zkConnectionManagerCallback-5-thread-1) []
o.a.s.c.c.ConnectionManager zkClient has connected
[junit4] 2> 8717 INFO (zkConnectionManagerCallback-7-thread-1) []
o.a.s.c.c.ConnectionManager zkClient has connected
[junit4] 2> 8840 INFO (zkConnectionManagerCallback-9-thread-1) []
o.a.s.c.c.ConnectionManager zkClient has connected
[junit4] 2> 8855 INFO (zkConnectionManagerCallback-11-thread-1) []
o.a.s.c.c.ConnectionManager zkClient has connected
[junit4] 2> 8865 INFO
(TEST-SaslZkACLProviderTest.testSaslZkACLProvider-seed#[B413507B747C128B]) [
] o.a.s.c.SaslZkACLProviderTest SETUP_END testSaslZkACLProvider
[junit4] 2> 8870 INFO (zkConnectionManagerCallback-13-thread-1) []
o.a.s.c.c.ConnectionManager zkClient has connected
[junit4] 2> 8943 INFO (zkConnectionManagerCallback-15-thread-1) []
o.a.s.c.c.ConnectionManager zkClient has connected
[junit4] 2> 8963 INFO (zkConnectionManagerCallback-17-thread-1) []
o.a.s.c.c.ConnectionManager zkClient has connected
[junit4] 2> 8974 INFO (zkConnectionManagerCallback-19-thread-1) []
o.a.s.c.c.ConnectionManager zkClient has connected
[junit4] 2> 8998 INFO
(TEST-SaslZkACLProviderTest.testSaslZkACLProvider-seed#[B413507B747C128B]) [
] o.a.s.c.ZkTestServer Shutting down ZkTestServer.
[junit4] 2> 9002 WARN (Thread-2) [] o.a.z.Login
[jira] [Reopened] (SOLR-12727) Upgrade ZooKeeper dependency to 3.4.13
[ https://issues.apache.org/jira/browse/SOLR-12727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Erickson reopened SOLR-12727: --- The presence of this entry in /etc/hosts appears to make lots of tests fail: fe80::1%lo0 localhost There are a couple of _very_ old ZK JIRAs mentioning this: https://issues.apache.org/jira/browse/ZOOKEEPER-676 https://issues.apache.org/jira/browse/ZOOKEEPER-1476 There are some hints on a quick Google search that this may be mac-specific. Also, it's unclear why this entry is in the /etc/hosts file in the first place, it _might_ have been something put in by Parallels or some such. Or is this just bogus and will be handled by the ::1 localhost entry? Reopening so we have a record of the resolution, even if it's "you should remove that entry and rely on '::1 localhost' instead" > Upgrade ZooKeeper dependency to 3.4.13 > -- > > Key: SOLR-12727 > URL: https://issues.apache.org/jira/browse/SOLR-12727 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: SolrCloud >Affects Versions: 7.4 >Reporter: Shawn Heisey >Assignee: Erick Erickson >Priority: Major > Fix For: master (8.0), 7.7 > > Attachments: SOLR-12727.patch, SOLR-12727.patch, SOLR-12727.patch, > SOLR-12727.patch, SOLR-12727.patch, SOLR-12727.patch > > > Upgrade ZK dependency to 3.4.13. This fixes ZOOKEEPER-2184 which will make > the ZK client re-resolve the server hostnames when a connection fails. This > will fix issues where a failed ZK container is replaced with a new one that > has a different IP address and DNS gets updated with the new address. > Typically these upgrades do not require code changes, but that should be > verified. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
