Not just our CI ... same failure here:
https://jenkins.thetaphi.de/job/Lucene-Solr-8.x-MacOSX/2184/
On Thu, Aug 12, 2021 at 2:03 PM Timothy Potter wrote:
>
> I'm seeing the following failure on branch_8x which looks like new
> code added to the test in commit:
> https://github.com/apache/lucene-s
I'm seeing the following failure on branch_8x which looks like new
code added to the test in commit:
https://github.com/apache/lucene-solr/commit/d99980516bd3470e9e120428914d1270d5ddf91b
It passes locally in my IDE but fails in an internal Jenkins server
running JDK 11 & 15:
java.lang.AssertionEr
Where I work we currently run most of production on Solr standalone
(cluster managed by custom code) on a slightly modified Solr fork.
This cluster scales orders of magnitude more than SolrCloud (try having
multiple hundreds thousand collections on a 16 nodes SolrCloud cluster,
even if you allow yo
If using the embedded for three nodes (for example) solr you will get one
of two things out of the box:
- Start zk on every one of 3 nodes, get 3 independent clusters that know
nothing of each other
- Start zk on one "key" node, point the other two nodes at the key node,
get one cluste
Just to conclude:
In addition I have also one crazy singleton customer that index and analyze
their stuff with plain Lucene Core and copy their final and highly optimized
indexes into their Solr server! … But nevermind, they managed to also do this
into Solr cloud with manual sharding using
Hey,
yes you are right. Nevertheless, I’d like to mention some “painpoints” or
common setups I have seen very often, especially by high-security or
public/governmental typical
beefy-high-secure-datacenter-deep-below-earth-no-cloud-at-all infrastructures.
Those also prefer Solr in contrast t
There are a few additional improvements to embedded ZK available in 3.7 and
further in 3.7.1/2 that would make it much easier and safer for us as well.
I plan to pick those up when I’m done with the cache work I’m doing.
On Thu, Aug 12, 2021 at 7:31 AM David Smiley wrote:
> I think Uwe is basica
I think Uwe is basically agreeing with my point -- we should not scare
people away from embedded ZK. We needn't wait for ZK v3.7; this is a
matter of documentation and maybe warnings we emit. Done.
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Th
For leader/follower, would SOLR_VAR_HOME be adequate? It would mean that,
at a minimum, core.properties moves to this data volume as well. If there
is a configset, it would either be there directly or better, could be
referenced from SOLR_HOME/configsets via referencing a named configset. If
suc
I am fully happy with something that works out of box.
The main problems I see with many customers is not only the complexity of
setup, but also that you need to install a separate Zookeeper ensemble. When
you tell them: Come on, use the one provided by a solr node and you are fine:
“no this
Here is the fix for the forbiddenapis complaints:
https://github.com/apache/solr/pull/261
(I also cleaned up the build logic)
-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de
From: Uwe Schindler
Sent: Thursday, August 12, 2021 12:5
The SOLR_DATA_HOME was primarily designed for leader/follower mode, letting the
user mount a /mnt/my/data/volume into the machines to store indices, but still
keep all config locally in a different folder structure.
I'm not attached to SOLR_DATA_HOME, it has caused quite some confusion in
SolrCl
12 matches
Mail list logo
