[
https://issues.apache.org/jira/browse/SOLR-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Per Steffensen closed SOLR-3004.
--------------------------------
Resolution: Not A Problem
> All Solr(Cloud) information in ZK in a dedicated Znode
> ------------------------------------------------------
>
> Key: SOLR-3004
> URL: https://issues.apache.org/jira/browse/SOLR-3004
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 4.0
> Reporter: Per Steffensen
> Fix For: 4.0
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> SolrCloud is using ZK for shared information. At the moment is distributes
> its information over more than one root-Znode (e.g. "collections", "configs"
> and "live-nodes"). It is not good style to act this way in ZK - pretending
> that you are the only one using ZK. Suggest we put it all inside one single
> root-Znode called "solr" or "solrcloud", so that we will have
> /solr/collections, /solr/configs and /solr/live-nodes in ZK instead. Believe
> it is important to do this change before the first "real" release including
> SolrCloud, because it is much easier to do before than after. If we do it
> after we will probably have to think about upgrade-code to move stuff from
> the old place to the new place in order to have systems build on the first
> release without this improvement go nicely to the next release with this
> improvement.
> E.g. I am using Lily and HBase and they nicely put all their information in
> ZK in designated root-Znodes ("hbase" and "lily").
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
