Hello,
We are using Solr 6.1.0. We have 2 shards and each has one replica with 7
zookeepers in our live environment.
Our Solr URL is
http://solr2.xyz.com:8983/solr/actionscomments/select?q=+resource_id:(123)+and+entity_type:(4)++action_status:(0)++is_active:(true)+and+recipient_id:(5941841)&sort
Hello,
We are using Solr 6.1.0. We have 2 shards and each has one replica with 7
zookeepers in our live environment.
Our Solr URL is
http://solr2.xyz.com:8983/solr/actionscomments/select?q=+resource_id:(123)+and+entity_type:(4)++action_status:(0)++is_active:(true)+and+recipient_id:(5941841)&sort
We are using Solr 6.1.0. We have 2 shards and each has one replica with 7
zookeepers in our live environment.
Our Solr URL is
http://solr2.xyz.com:8983/solr/actionscomments/select?q=+resource_id:(123)+and+entity_type:(4)++action_status:(0)++is_active:(true)+and+recipient_id:(5941841)&sort=action_
On 3/19/2021 3:36 PM, gnandre wrote:
While performing atomic indexing, I run into an error which says 'unknown
field X' where X is not a field specified in the schema. It is a
discontinued field. After deleting that field from the schema, I have
restarted Solr but I have not re-indexed the conte
On 3/20/2021 1:04 AM, jay harkhani wrote:
Hello,
We are using Solr 6.1.0. We have 2 shards and each has one replica with 7
zookeepers in our live environment.
So you've got it running SolrCloud mode (with ZooKeeper)?
Our Solr URL is
http://solr2.xyz.com:8983/solr/actionscomments/select?q=+r
Hi,
I’m aware I can check the status of a reindx, if I know both the source and
destination cluster, or I can check the progress of the async request via the
async API.
However, if I know neither of these, and I just want to check if there are any
REINDEX’s running on the cluster at any given t
I think calling:
/solr/collectionReindexCommandIsSentTo/stream?action=list
Lists running daemon processes, which should contain running reindexing
operations. Be careful of https://issues.apache.org/jira/browse/SOLR-13245
though, if you have more than one replica on the same node. (Joel Bernste
Hi Guys
We have faced an issue where tlog size is increasing unnecessarily. We are
using a "heavy indexing, heavy query" approach. We enabled hard commit
also,
solr cloud: 6.6
zk: 3.4.10
shards: 2, replication factor= 2
solrconfig,
${solr.autoCommit.maxTime:15000}
1
It appears this setter needs to be
called: org.apache.solr.parser.SolrQueryParserBase#setFuzzyMinSim and it
could be done by edismax. PR welcome!
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Thu, Mar 18, 2021 at 12:28 PM Olivier Tavard
wrote:
Hi folks,
I've noticed the following warning in the aliases documentation:
"...Reindexing a document with a different route value for the same ID
produces two distinct documents with the same ID accessible via the
alias..."
When tested such case it seems that really only one doc is retrieved but
wh
Hi,
By heavy query, do you mean you have a high query rate and/or you need
index update be available fast after few seconds (NRT search) ?
Do you see the hard commits in logs ?
Can you try to increase autoSoftCommit to 30 seconds or more ?
Regards
Dominique
Le sam. 20 mars 2021 à 18:53, Ritvik
Hi Dominique
Heavy query means high query rate on solr.
Honestly for 2-3 days we have stopped the queries on solr only we are doing
indexing !!!
As you see we have enabled Hard commit also to decrease tlog log size or
more and the same is written on solr docs. Still the same behaviour is
occurri
12 matches
Mail list logo