[
https://issues.apache.org/jira/browse/SOLR-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16851956#comment-16851956
]
Shawn Heisey commented on SOLR-8346:
------------------------------------
bq. Is there a way to do authenticated/encrypted access to 4lw?
This part I don't know, but I would imagine that if you require those things
for ZK in general, it would apply for 4lw as well. Something to ask the ZK
project.
bq. Will new solr be allowed to run with ZK 3.4.x or do we plan to have dual
support?
The way I read the general ZK guarantees tells me that any version should work
properly with the previous minor release and the next minor release. So if we
release Solr with the 3.5.x client, it should work with ZK servers running
anything from 3.4.0 through 3.6.X, unless there's a bug that breaks
compatibility. If they skip 3.6 and release 4.0 instead, then I think that
only the last 3.5.x version can be guaranteed to work with the new major
version ... but slow moving APIs could have a reality that's better than the
guarantee.
Here's their published information about version compatibility - I got this
from their mailing list:
https://cwiki.apache.org/confluence/display/ZOOKEEPER/ReleaseManagement
> Upgrade Zookeeper to version 3.5.5
> ----------------------------------
>
> Key: SOLR-8346
> URL: https://issues.apache.org/jira/browse/SOLR-8346
> Project: Solr
> Issue Type: Task
> Components: SolrCloud
> Reporter: Jan Høydahl
> Assignee: Erick Erickson
> Priority: Major
> Labels: security, zookeeper
> Attachments: SOLR-8346.patch, SOLR-8346.patch, SOLR-8346.patch,
> SOLR_8346.patch
>
>
> Investigate upgrading ZooKeeper to 3.5.x, once released. Primary motivation
> for this is SSL support. --Currently a 3.5.4-beta is released (2018-05-17).--
> Version 3.5.5 was released 2019-05-20
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
