Hi Edwin,
I think you should specify the absolute path when setting the environment
variables or remove the leading slash from the path.
Ciao,
Vincenzo
> On 11 Jun 2018, at 04:22, Zheng Lin Edwin Yeo wrote:
>
> I have found that we can't set it this way either, as we will get the below
> er
Hello everyone, solr solrhome can only configure a path, but our collection
is very large, there are 2 directories on the os, each directory space is
61TB, if we only start a solr node on a host, then only use 61TB of space
has caused half of the waste; if we start two nodes, we find that io
conten
I have found that we can't set it this way either, as we will get the below
error on "no valid keystore".
set SOLR_SSL_KEY_STORE=/etc/solr-ssl.keystore.jks
set SOLR_SSL_TRUST_STORE=/etc/solr-ssl.keystore.jks
Error:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAcc
On 6/8/2018 1:33 PM, root23 wrote:
> Can someone point to me what i am missing? i read the documentation but
> couldn't fully understand how to configure this ?
I think that this is the config you'll need:
transaction_type
lastfieldvalue
There are a couple of di
On 6/8/2018 8:59 AM, Markus Jelsma wrote:
> 2018-06-08 14:02:47.382 ERROR (qtp1458849419-1263) [ ] o.a.s.s.HttpSolrCall
> null:org.apache.solr.common.SolrException: Error trying to proxy request for
> url: http://idx2:8983/solr/
> search/admin/ping
> Caused by: org.eclipse.jetty.io.EofExceptio
On 6/7/2018 12:10 PM, Moenieb Davids wrote:
> Challenges:
> When performing full text searches without concurrently executing updates,
> solr seems to be doing well. Running updates also does okish given the
> nature of the transaction. However, when I run search and updates
> simultaneously, perfo
On 6/8/2018 12:13 PM, THADC wrote:
> I am having trouble getting a clear understanding of the relationship
> between my 3-node zookeeper cluster and how those 3 nodes relate to solr
> replicas (if at all). Since the replicas exist for failover purposes
> (correct?) as opposed to for load balancing
There's at least two ways of going about this:
1> when you create your collection, create it with the specil "EMPTY"
node set, then use ADDREPLICA to place each replica where you want it,
applying your knowledge of where the VMs are hosted.
2> use the replica placement rules, see:
https://lucene.
You have to cross check with live_nodes. This is especially true if
you stop Solr un-gracefully, i.e. "kill -9" or the like (which is
_not_ recommended).
During graceful shutdown, the Solr instance has a chance to change all
replica's states correctly. There's no chance to do that if you kill
Solr
hi all,
I am try to get the replica status from solrj,
but I found out that the status I get is not correct.
I still get the state of the replica as "active", although I have stop my
solr.
Is there any way I can get the correct replica state from solrj?
regards,
yy
Thanks Eric, that was helpful. But what if you want to proactively replicate
across multiple servers either at the VM or even physical server level. It
seems that we have control over the zookeeper locations and the solr server
locations since we explicitly define these when we configure the instan
Hi Shawn,
Thanks for the info.
Looking forward to having this functionality in Solr 7.4.0.
Regards,
Edwin
On 9 June 2018 at 23:02, Shawn Heisey wrote:
> On 6/9/2018 8:14 AM, Zheng Lin Edwin Yeo wrote:
>
>> Just to confirm my understanding, if I have 2 replicas, I should set both
>> of them to
12 matches
Mail list logo
