Noticed that whenever large amount of data is being indexed it stops.
Configuration is -
*My jetty.xml file is* -
https
<$
I've had some success. Firstly, Shawn I did find update-java-alternatives
with my googling and what an eye-opener that was! I thought it would surely
solve the problem, but it unfortunately didn't.
So today, I tried again. Because I hadn't noticed anything in the solr logs
before, I decided to wip
On Wed, Dec 13, 2023 at 1:35 PM Anuj Bhargava wrote:
> Noticed that whenever large amount of data is being indexed it stops.
>
>
What is the error it spits out?
> Configuration is -
>
> driver="com.mysql.jdbc.Driver"
> batchSize="-1"
> autoReconnect="true"
>
So, just as a follow up, I'm going to post my BEFORE and AFTER solr.in.sh
configs in case I've removed anything vital. Any comments welcome, as they
don't really mean much to me.
=== BEFORE
SOLR_HEAP="8000m"
GC_LOG_OPTS="-verbose:gc -XX:+PrintHeapAtGC -XX:+PrintGCDetails \
-XX:+PrintGCDateSta
12/13/2023, 11:04:12 AM ERROR false x:gt128_dga UpdateLog
java.io.EOFException
12/13/2023, 11:04:13 AM WARN false x:gt128_dga UpdateLog Log replay
finished. recoveryInfo=RecoveryInfo{adds=82717 deletes=0 deleteByQuery=0
errors=0 positionOfStart=0}
On Wed, 13 Dec 2023 at 13:38, Deepak Goel wrote:
On Wed, Dec 13, 2023 at 1:51 PM Anuj Bhargava wrote:
> 12/13/2023, 11:04:12 AM ERROR false x:gt128_dga UpdateLog
> java.io.EOFException
>
You are trying to update a file which does not exist. We need more details
about the file which you are trying to update.
> 12/13/2023, 11:04:13 AM WARN fal
Last Modified:about 7 hours ago
Num Docs:803749
Max Doc:803749
Heap Memory Usage:271668
Deleted Docs:0
Version:3789
Segment Count:25
Current:
Instance
CWD:/opt/solr-8.11.2/server
Instance:/var/solr/data/gt128_dga
Data:/var/solr/data/gt128_dga/data
Index:/var/solr/data/gt128_dga/data/index
Impl:org
Hi All,
We are facing the below error in our PROD environment.
Could you please let me know what are all the causes for this issue? and
how to troubleshoot it.
We have 10 solr nodes.
Heap Memory: 30GB
Total VM Memory:60 GB
Solr Version: 8.11.1
*CmdDistributor java.io.IOException: Request proces
Hi All,
We are seeing below errors in our solr logs. Could you please suggest me
what are all the causes for this issue and how to deal with it?
*ERROR:*
Caused by: java.util.concurrent.*TimeoutException: Idle timeout expired*:
12/12 ms
at
org.eclipse.jetty.io.IdleTimeout.checkIdl
Hi All,
My team and I are trying to match documents against a set of queries. Both need
to be updated in real-time (at least on the order of seconds) and the system
needs to scale to potentially millions of queries. Although lucene monitor
greatly optimizes this kind of alerting logic, as far a
Hi Luke,
We built Luwak, the basis of Solcolator, at my previous company Flax,
and donated it to Lucene. I've sent you a separate private email. I
don't know who built Solcolator sadly, it would indeed be awesome to get
this feature properly integrated into Solr.
Best
Charlie
On 13/12/2023
Hey Charlie,
Thanks for your private message. I am replying here as well for posterity .. I
think these links you shared may be helpful for future searchers:
hackathon feature branch luwak-server
https://github.com/flaxsearch/luwak/tree/luwak-server
Scott's blog post on the matter
https://open
Which of the following is correct or is there a better way?
curl -q
http://user:passw...@xxx.xxx.xx.xxx:8983/solr/korea/dataimport?command=full-import&clean=true&commit=true
>/dev/null 2>&1
curl -qsS -u user:password "
http://xxx.xxx.xx.xxx:8983/solr/korea/dataimport?command=full-import&clean=tr
The first one will sometimes fail when there are unusual characters in the
password. I'd either use
-u "user:password" (in quotes)
or
-H "Authorization: Basic 98sdfsasdfasdkjwere"
where you're providing the hash of user and password as a Header.
The end of the command just deals with any output.
>
There are some files in /var/solr/logs. For example -
solr_oom_killer-8983-2023-12-14_05_30_42.log
and this contains -
Running OOM killer script for process 2861377 for Solr on port 8983
Killed process 2861377
On Wed, 13 Dec 2023 at 17:36, Anuj Bhargava wrote:
> Last Modified:about 7 hours ag
On Thu, 14 Dec 2023, 10:11 Anuj Bhargava, wrote:
> There are some files in /var/solr/logs. For example -
> solr_oom_killer-8983-2023-12-14_05_30_42.log
>
> and this contains -
>
> Running OOM killer script for process 2861377 for Solr on port 8983
> Killed process 2861377
>
Looks like you are
solr.in.sh has the following entry -
SOLR_JAVA_MEM="-Xms15g -Xmx15g"
SOLR_OPTS="$SOLR_OPTS -Dsolr.disable.shardsWhitelist=true"
In which file should I define SOLR_HEAP and what should be the ideal value.
My server has 128GB Ram and 2TB SSD
Regards,
Anuj
On Thu, 14 Dec 2023 at 10:56, Deepak Goel
On Thu, Dec 14, 2023 at 11:40 AM Anuj Bhargava wrote:
> solr.in.sh has the following entry -
> SOLR_JAVA_MEM="-Xms15g -Xmx15g"
> SOLR_OPTS="$SOLR_OPTS -Dsolr.disable.shardsWhitelist=true"
>
There could be a possible memory leak in your application. You need to
profile your application (possibly
18 matches
Mail list logo
