*1.empty Zookeeper*
*2.empty index directories for solr*
*3.empty solr.xml*
<?xml version="1.0" encoding="UTF-8" ?>
<solr persistent="true">
<cores adminPath="/admin/cores"
zkClientTimeout="${zkClientTimeout:15000}" hostPort="${jetty.port:}"
hostContext="solr"> </cores>
</solr>
*
3.1 upload / link cfg in zookeeper for test collection*
*4*.* start 4 solr servers on different machines*
*5. Access server* : i see
<There are no SolrCores running — for the current functionality we require
at least one SolrCore, sorry :)> that's ok
*6. CREATE collection*
http://hostname:15000/solr/admin/collections?action=CREATE&name=test&numShards=1&replicationFactor=4
this creates one core on each server with one shard named
- test_shard1_replica1
- test_shard1_replica2
- test_shard1_replica3
- test_shard1_replica4
and persists it in solr.xml on each server.
---
REPEAT steps 3-6 to create new collections. We use this a lot with 4.1
Note: each collect needs a different solrHOME dir with its own solr.xml
On Thu, Feb 28, 2013 at 10:25 AM, Mark Miller <markrmil...@gmail.com> wrote:
>
> On Feb 28, 2013, at 9:41 AM, Shankar Sundararaju <shan...@ebrary.com>
> wrote:
>
> > did having the config name same as collection name allow you to
> > create collections without having to link the corresponding config
> names? I
> > did not try this myself.
>
> It should work that way or there is a bug.
>
> - Mark
>
>
--
Anirudha P. Jadhav
