... looking at this line, I am wondering if this is an issue because I am
using a Self-Signed Certificate:
Caused by: javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to fin
Thanks Shawn,
Here is what I get from the logs:
2018-04-20 18:03:57.805 WARN (indexFetcher-19-thread-1) [
x:XP1Prod_core_index_rebuild] o.a.s.h.IndexFetcher Master at:
https://mastercomputername:8983/solr/XP1Prod_core_index_rebuild is not
available. Index fetch failed by exception:
org.apache.
Thanks Shawn,
Here is what I get from the logs:
2018-04-20 18:03:57.805 WARN (indexFetcher-19-thread-1) [
x:XP1Prod_core_index_rebuild] o.a.s.h.IndexFetcher Master at:
https://mastercomputername:8983/solr/XP1Prod_core_index_rebuild is not
available. Index fetch failed by exception:
org.apache.
On 4/21/2018 10:24 AM, kway wrote:
However, I can't get replication to work when using SSL/HTTPS. It throws IO
Communication errors as it can’t resolve the https connection to a localhost
certificate on the Master. The error is as follows:
Master at: https://mastercomputername:8983/solr/core_ind
Yet, that is a task which the main application, Solr, could and
should undertake, rather than ask we human slaves to add sundry programs
to tend it from afar.
Similarly, it would be useful for there to be feedback from Solr
when adding material so that we don't overwhelm parts of the pip
Yeah, trying to have something that satisfies all use cases is a bear.
I know of one installation where the indexing rate was so huge that
they couldn't afford to have any merging (80B docs/day) so in that
situation any heuristics built into Solr would be wrong.
Here's an alternate approach to hav
A good find Erick, and one which brings into focus the real problem
at hand. That overload case would happen if there were an Optimise
button or if the curl equivalent command were issued, and is not a
reason to avoid either/both.
So, what could be done to avoid such awkward difficultie
Joe:
Serendipity strikes, The thread titled "JVM Heap Memory Increase (SOLR
CLOUD)" is a perfect example of why the optimize button is so
"fraught".
Best,
Erick
On Sat, Apr 21, 2018 at 9:43 AM, Erick Erickson wrote:
> Joe:
>
> Thanks for moving the conversation over here that we were having on
G1GC will not solve OOM problems, it just _may_ give better GC performance.
I'm assuming you're actively adding documents to this index, and
further assuming that you're replacing some existing documents.
If those assumptions are true, here's what I think is happening:
- You optimize, which creat
On 21/04/2018 17:25, Doug Turnbull wrote:
I haven’t tracked this change, but can you still optimize through the API?
Here’s an example using update XML
https://stackoverflow.com/questions/6954358/how-to-optimize-solr-index
There are so many cases hitting “optimize” causes a huge segment merge
Joe:
Thanks for moving the conversation over here that we were having on
the blog post. I think the wider audience will benefit from this going
forward.
bq: ...apparent inability to remove piles of deleted docs
do note that deleted docs are removed during normal indexing when
segments are merged
I haven’t tracked this change, but can you still optimize through the API?
Here’s an example using update XML
https://stackoverflow.com/questions/6954358/how-to-optimize-solr-index
There are so many cases hitting “optimize” causes a huge segment merge that
brings down a Solr cluster that I think
I need to use SSL in my Master/Slave Solr 6.6.2 environment. I had created a
localhost SSL Cert on the Master (works on the Master because it’s local),
but this won’t work for the Slave which has replication based on the IP of
the Master server. I then changed it to a self-signed cert that uses the
In Solr v7.3.0 the ability to removed "deleted" docs from a core by
use of what until then was the Optmise button on the admin GUI has been
changed in an ungood way. That is, in the V7.3.0 Changes list, item SOLR
7733 (quote remove "optmize from the UI, end quote). The result of that
is an
The solr.cmd starts Solr by running java -jar start.jar, which has the MANIFEST
file that tells the java command that it's main class is
org.eclipse.jetty.start.Main.
So, I would think your Java program should be able to start Solr (jetty, really)
by calling org.exlipse.jetty.start.Main.main(a
15 matches
Mail list logo
