On 1/24/13 11:22 PM, Fadi Mohsen wrote:
Thanks Per, would the first approach involve restarting Solr?
Of course ZK need to run in order to load the config into ZK. Solr nodes
do not need to run. If they do I couldnt imagine that they need to be
restarted in order to take advantage of new conf
On Jan 24, 2013, at 5:22 PM, Fadi Mohsen wrote:
>
> The reason we would like to avoid Zookeeper are
> * due to lack of knowledge.
> * the amount of work/scripting for developers per module and release
> documentation.
> * the extra steps of patching ZK nodes for QA and operations.
>
> ZkCLI is
Thanks Per, would the first approach involve restarting Solr?
Thanks Mark, that's great, Ill try checkout and apply patches from ticket
to understand further.
The reason we would like to avoid Zookeeper are
* due to lack of knowledge.
* the amount of work/scripting for developers per module and
On Jan 24, 2013, at 10:02 AM, Fadi Mohsen wrote:
> Hi, We would like to use Solr to index statistics from any Java module in
> our production environment.
>
> Applications have to can create collections and index data on demand, so my
> initial thought is to use different HTTP methods to accomp
On 1/24/13 4:51 PM, Per Steffensen wrote:
2) or You can have an Solr node (server) load a "Solr config" into ZK
during startup by adding collection.configName and bootstrap_confdir
VM params - something like this
java -DzkHost=
-Dcollection.configName=
-Dbootstrap_confdir= -jar start.jar
We
Basically uploading a "Solr config" (including schema.xml,
solrconfig.xml etc.) is an operation different from creating
collections. When creating a collection (e.g. using the Collection API)
you reference the (already existing) "Solr config" it needs to use.
Collections can share "Solr config"
