This has been working for a few years already, but there is a lack of
documentation, see https://issues.apache.org/jira/browse/SOLR-7889 and
children. We are very happy for contributions to the documentation, in
particular https://issues.apache.org/jira/browse/SOLR-7893 !
Jan
> 25. mar. 2022
On 2022-03-25 03:43 +, Sam Lee wrote:
> The solution is to add the appropriate ZooKeeper Java properties. Notice
> that these are exactly the same properties needed by standalone
> ZooKeeper's 'zkServer.sh' and 'zkCli.sh' to connect to ZooKeeper via
> SSL [1] [2]. Add the following to bin/solr.
I have a core which ceased responding either to select or to admin/core:
restarting the Solr instance resolved the problem, but I am wondering whether
there is some configuration which may need to be tweaked. Below is a portion of
solr.log from the time when the problem began. Please note that t
Is there an OOM anywhere in that log? I've definitely seen java lose track
of things during a slow-moving oom.
Also definitely check dmesg for anything in that same timeframe if you
still have the logs.
On Fri, Mar 25, 2022 at 10:58 AM Oakley, Craig (NIH/NLM/NCBI) [C]
wrote:
> I have a core wh
Thanks for the quick reply
grep -i -c OutOfMemory solr.log.20220* shows zero
Nothing new in /var/log/dmesg since reboot of the host a couple weeks ago
Let me know if you have any other suggestions
Thanks again
-Original Message-
From: matthew sporleder
Sent: Friday, March 25, 2022 11
Hello,
I'm trying to create a new core with SolrJ's CoreAdminRequest.createCore.
The idea is to use
"/opt/solr/server/solr/configsets/jcg_example_configs/solrconfig.xml" as
config file and
"/opt/solr/server/solr/configsets/jcg_example_configs/managed-schema" as
schema file, (or later somethi
On 3/25/22 10:08, Armin Mueller wrote:
I'm trying to create a new core with SolrJ's CoreAdminRequest.createCore.
CoreAdmin cannot create the directory/files for a new core. They must
already exist before the create is called. If you want Solr to create
cores without touching the filesystem
Hello Solr World,
I'm a firefighter, brought in to help nurse a Solr Cloud system back
to life until it can be replaced. It's running Solr 6.5, and a data
item (key) field exceeded what will fit in a signed 32-bit collection
field a while ago.
I've been able to make a new collection with 64-bit
On 3/25/2022 12:04 PM, Phil Budne wrote:
BUT, the alias definition does not persist between restarts. I
haven't spotted any newly written (aliases.json?) file(s) created on
any of the shards, or the zookeper system (all of the shards and
zookeeper are running in Docker containers).
All that sh
Shawn,
Thanks for your reply!
> All that should be in zookeeper, not on the filesystem.
Where should zookeeper stash the data?
> Don't go by what the admin UI shows you. Try accessing
> http://server:port/solr//select?q=*:* ... substituting the correct
> server, port, and alias name.
Bot
On 3/25/2022 5:04 PM, Phil Budne wrote:
All that should be in zookeeper, not on the filesystem.
Where should zookeeper stash the data?
The aliases.json file is at the root of the zookeeper tree.
https://www.dropbox.com/s/fc5clxz211ydesh/Screenshot%202022-03-25%2017.40.17.png?dl=0
I tried 6.6
Thanks for the pictures. I think I may have it figured out.
The Dockerfile for zookeeper runs upconf and linkconf for each
collection, and then saves a copy of /var/lib/zookeeper duing
construction of the image, and doesn't persist any changes made while
running. I found this comment:
# Mov
12 matches
Mail list logo
