Hi,
Is there anyway that we can run Solr as a service, and allow it to start
automatically during the startup of the system?
I have tried to set up the service by using nssm, but it only works for
ZooKeeper and not Solr.
I am using Solr 8.2.0.
Regards,
Edwin
Brett, it’s probably because you hit the 5g default segment size limit on
Solr and in order to merge segments a huge number of the docs within the
segment must be marked as deleted. So even if large amounts of docs are
deleted docs within the segment, the segment is still there, happily taking
up s
Turns out this is due to a job that indexes logs. We were able to clear some
with another job. We are working through the value of these indexed logs.
Thanks for all your help!
Brett Moyer
Manager, Sr. Technical Lead | TFS Technology
Public Production Support
Digital Search & Discovery
8625
You configure CDCR by _collection_, so this question really makes no sense.
You’d never mention collection.configName. So what I suspect is that you’re
misreading the docs.
${targetZkHost1},${targetZkHost2},${targetZkHost3}
sourceCollection_on_local_cluster
targetCollection_on_targetZkHost1 2 a
Hi,
Is there a way to turn off the CDCR for only selected target clusters.
Say, I have a configuration like following. I have 3 target clusters
targetZkHost1, targetZkHost2 and targetZkHost3. Is it possible to turn off
the CDCR for targetZkHost2 and targetZkHost3 but keep it on for
targetZkHost1?
Here’s some sample SolrJ code using TIka outside of Solr’s Extracting Request
Handler, along with some info about why loading Solr with the job of extracting
text is not optimal speed wise:
https://lucidworks.com/post/indexing-with-solrj/
> On Aug 13, 2019, at 12:15 PM, Jan Høydahl wrote:
>
>
You May want to review
https://cwiki.apache.org/confluence/display/SOLR/SolrPerformanceProblems#SolrPerformanceProblems-SlowIndexing
for some hints.
Make sure to index with multiple parallel threads. Also remember that using
/extract on the solr side is resource intensive and may make your clus
On 8/13/2019 9:28 AM, Kojo wrote:
Here are the last two gc logs:
https://send.firefox.com/download/6cc902670aa6f7dd/#Ee568G9vUtyK5zr-nAJoMQ
Thank you for that.
Analyzing the 20MB gc log actually looks like a pretty healthy system.
That log covers 58 hours of runtime, and everything looks ver
Shawn,
Here are the last two gc logs:
https://send.firefox.com/download/6cc902670aa6f7dd/#Ee568G9vUtyK5zr-nAJoMQ
Thank you,
Koji
Em ter, 13 de ago de 2019 às 09:33, Shawn Heisey
escreveu:
> On 8/13/2019 6:19 AM, Kojo wrote:
> > --
> > tail -f node1/logs/solr_oom_killer-8983-2019
Hi,
We are having some issue on scaling solr indexing. Looking for suggestion.
Setup : We have two solr cloud (7.4) instances running in separate cloud
VMs with an external zookeeper ensemble.
We are sending async / non-blocking http request to index documents in solr.
2
cloud VMs ( 4 core * 3
On Fri, Aug 09, 2019 at 03:45:21PM -0600, Shawn Heisey wrote:
> On 8/9/2019 3:07 PM, Mark H. Wood wrote:
> > Did I miss something, or is there no way, using SolrJ, to enumerate
> > loaded cores, as:
> >
> >curl 'http://solr.example.com:8983/solr/admin/cores?action=STATUS'
> >
> > does?
>
> T
Hi all,
we updated Solr from version 7.3.1 to version 8.1.1 and detected a problem
requesting suggesters via multi-collection alias. It also exists in version
8.2.0. I think it is a bug but maybe someone can verify this?
I created an alias called „WORLD“ pointing to six collections. If I send a
On 8/13/2019 6:19 AM, Kojo wrote:
--
tail -f node1/logs/solr_oom_killer-8983-2019-08-11_22_57_56.log
Running OOM killer script for process 38788 for Solr on port 8983
Killed process 38788
--
Based on what I can see, a 6GB heap is not big enough for the setup
you've got
Erick and Shawn,
thank you very much for the very usefull information.
When I start to move from sigle Solr to cloud, I was planning to use the
cluster for very large collections.
But the collection that I said, will not grow that much, so I will downsize
shards.
Thanks for the information abou
Thank you Jan for the reply.
I will try it out.
Best,
Mark.
On Mon, Aug 12, 2019 at 6:29 PM Jan Høydahl wrote:
> I have never used such settings, but you could check out
> https://lucene.apache.org/solr/guide/8_1/common-query-parameters.html#segmentterminateearly-parameter
> which will allow yo
For lingo3g, they have replaced commons-lang with commons-lang3 in version
1.16, which should be in line with what Solr has done.
Just that our lingo3g licence does not allow us to upgrade to the new
version 1.16, and if we stick to the older version 1.15.1, it requires the
use of commons-lang.
R
16 matches
Mail list logo