On Dec 12, 2012, at 12:52 PM, Mike Schultz wrote:
> Ok, that makes sense and it's probably workable, but, it's still more awkward
> than having code and configuration deployed together to individual machines.
>
> For example, for a deploy of new software/config we need to 1) first upload
> co
Ok, that makes sense and it's probably workable, but, it's still more awkward
than having code and configuration deployed together to individual machines.
For example, for a deploy of new software/config we need to 1) first upload
config to zK. then 2) deploy new software to the nodes.
What ab
Doing this with SolrCloud is not much different than doing it with old style
Solr.
ZooKeeper supports rolling restarts, and AFAIK, so does Solr generally.
While the configs live in zk, they work the same way as if they were local.
A SolrCore won't try and read them until you reload it. I think
