[ https://issues.apache.org/jira/browse/SOLR-6734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503362#comment-16503362 ]
Jan Høydahl commented on SOLR-6734: ----------------------------------- I'm not convinced we should go down that path, adding a whole new level of code and network transport that needs its own discovery, protocols, failure handling, security, monitoring and what not. Kind of like the simplicity of Solr being a single process:) Questions: * How would the agent start the real Solr and monitor it? Native (child) process control is quite challenging and lacking in Java. Add to that service/daemon as a third process level. * Multicast is so 1990 :) and not supported at all in many environments, so you'd need to build separate discovery protocols to choose from (like ES) - and at the end of the day you'll probably end up with recommending stable hard-wired ZK_HOSTs for production. * If the agent is capable of reconfiguring and restarting a node, it needs to be secured. So all these new socket commands will need to be secured with TLS, authentication and authorization from day one, then the agent is not so slim anymore? Again, I think we try to reinvent what should perhaps instead be an effort to improve official ansible/puppet modules for Solr and ease production-grade container-based installs. We could ease part of the Zookeeper ensemble setup pain by shipping ZK with Solr as we already do, but also offer a start script, e.g. {{bin/zk start -z zoo1:2181,zoo2:2181,zoo3:2181}} to configure and start Zookeeper on a node. With zk 3.5 we'll get more dynamic reconfig options too, which will perhaps make it possible to go from 1 to 3 zk nodes by simply starting ZK on more nodes... > Standalone solr as *two* applications -- Solr and a controlling agent > --------------------------------------------------------------------- > > Key: SOLR-6734 > URL: https://issues.apache.org/jira/browse/SOLR-6734 > Project: Solr > Issue Type: Sub-task > Reporter: Shawn Heisey > Priority: Major > > In a message to the dev list outlining reasons to switch from a webapp to a > standalone app, Mark Miller included the idea of making Solr into two > applications, rather than just one. There would be Solr itself, and an agent > to control Solr. > http://mail-archives.apache.org/mod_mbox/lucene-dev/201305.mbox/%3C807476C6-E4C3-4E7E-9F67-2BECB63990DE%40gmail.com%3E -- 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