Hi, I did not manipulating the data dir. What I did was:
1. Downloaded solr-6.5.1.zip 2. ensured no solr process is running 3. unzipped solr-6.5.1.zip to ~/solr_new2/solr-6.5.1 3. started an external zookeeper 4. copied a conf directory from a working non-cloudsolr (6.5.1) to ~/solr_new2/solr-6.5.1 so that I have ~/solr_new2/solr-6.5.1/conf (see http://randspringer.de/solrcloud_test/my.zip for content) 5. postd the conf to zookeeper with: bin/solr zk upconfig -n heise -d ./conf -z localhost:2181 6. started solr in cloud mode with bin/solr -c -z localhost:2181 7. tried to create a acollection with bin/solr create -c heise -shards 2 -->failed with: Connecting to ZooKeeper at localhost:2181 ... INFO - 2017-05-17 07:06:38.249; org.apache.solr.client.solrj.impl.ZkClientClusterStateProvider; Cluster at localhost:2181 ready Re-using existing configuration directory heise Creating new collection 'heise' using command: http://localhost:8983/solr/admin/collections?action=CREATE&name=heise&numShards=2&replicationFactor=1&maxShardsPerNode=2&collection.configName=heise ERROR: Failed to create collection 'heise' due to: {127.0.1.1:8983_solr=org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException:Error from server at http://127.0.1.1:8983/solr: Error CREATEing SolrCore 'heise_shard2_replica1': Unable to create core [heise_shard2_replica1] Caused by: Lock held by this virtual machine: /home/pberg/solr_new2/solr-6.5.1/server/data/index/write.lock} 8. Tried with 1 shard, worked --> pberg@porschberg:~/solr_new2/solr-6.5.1$ bin/solr create -c heise -shards 1 Connecting to ZooKeeper at localhost:2181 ... INFO - 2017-05-17 07:21:01.632; org.apache.solr.client.solrj.impl.ZkClientClusterStateProvider; Cluster at localhost:2181 ready Re-using existing configuration directory heise Creating new collection 'heise' using command: http://localhost:8983/solr/admin/collections?action=CREATE&name=heise&numShards=1&replicationFactor=1&maxShardsPerNode=1&collection.configName=heise { "responseHeader":{ "status":0, "QTime":2577}, "success":{"127.0.1.1:8983_solr":{ "responseHeader":{ "status":0, "QTime":1441}, "core":"heise_shard1_replica1"}}} What did I wrong? I want to use multiple shards on ONE node. Best regards Thomas > Shawn Heisey <apa...@elyograg.org> hat am 16. Mai 2017 um 16:30 geschrieben: > > > On 5/12/2017 8:49 AM, Thomas Porschberg wrote: > > ERROR: Failed to create collection 'cat' due to: > > {127.0.1.1:8983_solr=org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException:Error > > from server at http://127.0.1.1:8983/solr: Error CREATEing SolrCore > > 'cat_shard1_replica1': Unable to create core [cat_shard1_replica1] Caused > > by: Lock held by this virtual machine: > > /home/pberg/solr_new2/solr-6.5.1/server/data/bestand/index/write.lock} > > The same Solr instance is already holding the lock on the index at > /home/pberg/solr_new2/solr-6.5.1/server/data/bestand/index. This means > that Solr already has a core using that index directory. > > If the write.lock were present but wasn't being held by the same > instance, then the message would have said it was held by another program. > > This sounds like you are manually manipulating settings like dataDir. > When you start the server from an extracted download (not as a service) > and haven't messed with any configurations, the index directory for a > single-shard single-replica "cat" collection should be something like > the following, and should not be overridden unless you understand > *EXACTLY* how SolrCloud functions and have a REALLY good reason for > changing it: > > /home/pberg/solr_new2/solr-6.5.1/server/solr/cat_shard1_replica1/data/index > > On the "Sorry, no dataimport-handler defined!" problem, this is > happening because the solrconfig.xml file being used by the collection > does not have any configuration for the dataimport handler. It's not > enough to add a DIH config file, solrconfig.xml must have a dataimport > handler defined that references the DIH config file. > > Thanks, > Shawn >
