[
https://issues.apache.org/jira/browse/SOLR-13661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934449#comment-16934449
]
Jan Høydahl commented on SOLR-13661:
------------------------------------
{quote}The reason why we built hot deployment was that Solr was unstable when
we end up restarting a 1000 node cluster
{quote}
Hot deployment was identified as a future improvement in my POC. And don't get
me wrong, I'm very impressed by all your hot jar deployment work, it solves
many use cases. It also makes deploy a bit more messy since Solr needs to be up
and running as part of the deploy process itself. That is not very cool when
writing Dockerfiles and ansible deploy scripts. Some kind of plugins could be
fundamental to even getting the cluster started and so I'd prefer if there was
an "offline/static" way to pull and install certain packages before needing to
fire up the cluster. That was the *only* way to install packages in my POC, but
perhaps we could handle both. I like the fact that a node can come up and then
consult another node to fetch its missing plugins, after asking ZK about what
plugins are needed. That should make for a possibility of pulling a bunch of
plugin packages (zip/jar) into say /var/solr/plugins on a cold node, then
declaring those somewhere in ZK and when the cluster bootstraps it will
self-distribute those plugins across the entire cluster.
> A package management system for Solr
> ------------------------------------
>
> Key: SOLR-13661
> URL: https://issues.apache.org/jira/browse/SOLR-13661
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Noble Paul
> Priority: Major
> Labels: package
>
> Solr needs a unified cohesive package management system so that users can
> deploy/redeploy plugins in a safe manner. This is an umbrella issue to
> eventually build that solution
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
