Hi all,
TL;DR
Does anyone know what's the responsibility of
DistributedUpdateProcessorFactory?
This is what I found in the source code:
// NOT mt-safe... create a new processor for each add thread
// TODO: we really should not wait for distrib after local? unless a
certain replication factor is
Those 3 are part of default chain. So if you stop using schemaless one,
you get them anyway.
https://solr.apache.org/guide/solr/latest/configuration-guide/update-request-processors.html#default-update-request-processor-chain
If you define a different custom chain, I think you need to add them
ma
Hi!
In Solr 8.6, I used the autoscaling configuration to set it up so that we
had 2 `nodeTypes`, one for indexing, the other for querying.
And our collections were set up to be TLOG + PULL replicas only, and we'd
use the autoscaling to place the TLOG on the indexing nodeTypes, and the
PULL on the
Thanks again Dave, helpful information! Yes, we have one slave as primary
- serving queries, and the other for failover... We are in a slow process
of moving to SolrCloud Solr 8/9, but still a lot of work is given to
maintaining our Solr 6 deployment. So learning more about this type of
replica
Hi,
I am running Apache Solr 8.11.2 on CentOS Linux release 7.9.2009 (Core)
trying to modify /opt/solr/server/etc/jetty.xml to set the Attribute
*maxFormContentSize* as per the below path
[root@etc]# ls -l
total 76
-rw-r--r-- 1 root root 1950 May 13 03:21 jetty-gzip.xml
-rw-r--r-- 1 root root 3
On 10/12/22 05:54, Vincenzo D'Amore wrote:
Does anyone know what's the responsibility of
DistributedUpdateProcessorFactory?
That update processor takes care of atomic update functionality and
farming out update requests to other Solr nodes, in particular for
SolrCloud. It probably has some o
