Does anybody have any experience with "rolling deployments" and SolrCloud?
We have a production environment where we deploy new software and config simultaneously to individual servers in a rolling manner. At any point during the deployment, there may be N boxes with old software/config and M boxes with new software/config. Eventually N=0 (no more old software/config) and M=100% (all boxes have new software/config). This is very convenient because one knows that the config that the new software requires is present, but it is not present for old software on other boxes. We can maintain 100% uptime for the service using this technique. If I'm understanding the role that Zk plays in SolrCloud, this no longer works. If config lives in Zk, then it's all or nothing, all old or all new config. If this is true, it presents a bunch of new challenges for deploying software. So to ask a concrete question, is it possible to not use zk for config distribution, i.e. keep the config local to each shard? Mike Schultz -- View this message in context: http://lucene.472066.n3.nabble.com/Rolling-Deploys-and-SolrCloud-tp4026212.html Sent from the Solr - User mailing list archive at Nabble.com.
