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
