janhoy commented on PR #2391:
URL: https://github.com/apache/solr/pull/2391#issuecomment-3811895025

   > Thanks for taking a look at this @janhoy I think I've stalled a bit on 
this... It feels "so close' yet not sure how to get it over the hump.
   
   Yep, I got it up to speed with main, hardened the qourum test, and try to 
add test for stopping a quorum node and resume operation.
   
   I think we need to focus on the startup modes / params to have a clear story 
for the three modes as you mentioned
   * `--user-managed`
   * `-c` (implicit) with one embedded ZK
   * `-z external:2181` for existing external zk cluster
   * Managed embedded quorum
   
   For the managed embedded quorum, I believe we have proved that setting the 
node role explicitly and passing `-z` to all nodes pointing to those quorum 
nodes will do the trick. That is probably good enough for a first release?
   
   ## Phase 1:
   Ship a experimental version with a working zk node-role, that starts a 
quorum that is somewhat stable.
   
   ## Phase 2:
   Make it easier to setup for a small test cluster with some convenience flags 
(see above). integrate into solr operator.
   Enable ZK ACL stuff by default.
   
   ## Phase 3:
   Good support for SSL between solr and embedded zk quorum. Either 
self-provided certs, or self-signed certs during startup. Note, we can have 
non-ssl Solr API while still having SSL between solr and zookeeper.
   
   ## Phase 4:
   Support dynamic reconfiguration. I don't know how important that really is. 
In k8s service-names are stable and you don't need to reconfigure zk really, 
except when changing the size of your quorum. But in self managed 
infrastructure, you may want to retire some servers and move zk over to another 
set of nodes by reconfiguring in two phases.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to