Solr enabled kerberos and create collection failed

2019-10-19 Thread Lvyankui
SolrCloud mode, Solr and Zookeeper enabled kerberos, create collection failed with following command curl --negotiate -u : 'http:// noder27:8983/solr/admin/collections?action=CREATE&name=test01&numShards=1&replicationFactor=1&collection.configName=_default&wt=json' The error is: { "responseHead

Re: Solr enabled kerberos and create collection failed

2019-10-19 Thread Jörn Franke
You need to obtain / renew your Kerberos ticket using kinit > Am 19.10.2019 um 12:31 schrieb Lvyankui : > > SolrCloud mode, Solr and Zookeeper enabled kerberos, create collection > failed with following command > curl --negotiate -u : 'http:// > noder27:8983/solr/admin/collections?action=CREAT

Re: Document Update performances Improvement

2019-10-19 Thread Nicolas Paris
Hi community, Any advice to speed-up updates ? Is there any advice on commit, memory, docvalues, stored or any tips to faster things ? Thanks On Wed, Oct 16, 2019 at 12:47:47AM +0200, Nicolas Paris wrote: > Hi > > I am looking for a way to faster the update of documents. > > In my context, th

Re: Document Update performances Improvement

2019-10-19 Thread Jörn Franke
Maybe you need to give more details. I recommend always to try and test yourself as you know your own solution best. Depending on your spark process atomic updates could be faster. With Spark-Solr additional complexity comes. You could have too many executors for your Solr instance(s), ie a to

Re: Document Update performances Improvement

2019-10-19 Thread Nicolas Paris
> Maybe you need to give more details. I recommend always to try and > test yourself as you know your own solution best. What performance do > your use car needs and what is your current performance? I have 10 collections on 4 shards (no replications). The collections are quite large ranging from