Ah, understood. It always looks better to be able to say “I’ve tried it and this is what I found” than “Uh, I’ll have to get back to you on that” ;)
I’ve occasionally been able to assuage clients like that by pointing out that often, especially with Open Source, announcing end of support is often more about relieving the burden on programmers of maintaining multiple versions than anything being horribly wrong. Best, Erick > On Apr 9, 2020, at 10:03 AM, Bram Van Dam <bram.van...@intix.eu> wrote: > > Thanks, Erick. I'll give it a go this weekend and see how it behaves. > I'll report back so there's a record of my attempts in case anyone else > ends up asking the same question. > > Some of our customers get a bit nervous when software goes out of > support, even if it works fine, so I try to be prepared ;-) > > On 09/04/2020 13:50, Erick Erickson wrote: >> All it means is that there won’t be upgrades/improvements to >> ZK, 3.4 will still run. So there’s no need to move to 3.5 independent >> of upgrading Solr just because that version of ZK is unsupported >> going forward. >> >> I haven’t personally tried to run 3.5 against an earlier version, but >> one thing you’ll probably want to do if you try it is whitelist >> “ruok”, “mntr”, and “conf” in your Zookeeper config, see the >> Zookeeper documentation. NOTE: that is only necessary if you >> want to see the Zookeeper status in the admin UI, those >> commands aren’t used by anything else in Solr. >> >> The JIRA (SOLR-8346) contains a _ton_ of changes, but the mostly >> fall in two categories: Using a file rather than strings in tests and >> trying to handle the whitelist programmatically, neither of which >> are relevant to just dropping a newer version of ZK in.
