Hi community,
I found that SolrCloud won't check the IO status if the SolrCloud process is
alive.
E.g. If I delete the SolrCloud data directory, there are no errors report, and
I can still log in to the SolrCloud Admin UI to create/query collections.
Is this reasonable?
Can someone explain why
Thanks, Shawn and Erick.
We are step by step trying out the changes suggested in your post.
Will get back once we have some numbers.
--
Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Depends. *nix systems have delete-on-close semantics, that is as
long as there’s a single file handle open, the file will be still be
available to the process using it. Only when the last file handle is
closed will the file actually be deleted.
Solr (Lucene actually) has file handle open to every
Recently we had modified `noCFSRatio` parameter of merge policy.
8
5
50.0
4000
0.0
This is our current merge policy. Earlier `noCFSRatio` was set to `0.1`.
generally to reflect any changes of solrconfig we reload the collection. But
we stop do
>
> start (without option : bin/solr start)
Solr SQL/JDBC requires Solr Cloud (running w/ Zookeeper) since streaming
expressions (which backs the Solr SQL) requires it.
You should be able to start Solr this way to get Solr in cloud mode.
bin/solr start -c
If you use the above to start Solr, th
Thank you Kevin, I can now connect (I test with DbVisualiser) with -c
option.
Vincent
Le lun. 9 nov. 2020 à 16:30, Kevin Risden a écrit :
> >
> > start (without option : bin/solr start)
>
>
> Solr SQL/JDBC requires Solr Cloud (running w/ Zookeeper) since streaming
> expressions (which backs the
He Scott,
We have also recently migrated to solr 8.5.2. And facing similar issue.
Are you able to resolve this
--
Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
For example the streaming expression significantTerms:
https://lucene.apache.org/solr/guide/8_4/stream-source-reference.html#significantterms
significantTerms(collection1,
q="body:Solr",
field="author",
limit="50",
minDocFreq="1
We are in the process of upgrading from Solr7.4.0 to Solr8.5.2, and we are
experiencing intermittent problem with log rotation
Our log4j2.xml file (both for Solr7.4.0 and for Solr8.5.2) includes the
following:
%d{-MM-dd HH:mm:ss.SSS} %-5p (%t) [%X{collection}
On 11/9/2020 5:44 AM, raj.yadav wrote:
*Question:*
Since reload is not done, none of the replica (including leader) will have
updated solrconfig. And if we restart replica and if it trys to sync up with
leader will it reflect the latest changes of solrconfig or it will be the
same as leader.
FYI an updated Docker image was just published a few hours ago:
https://hub.docker.com/_/solr
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Wed, Nov 4, 2020 at 9:06 AM Atri Sharma wrote:
> 3/11/2020, Apache Solr™ 8.7 available
>
> The Lucene PMC
11 matches
Mail list logo