[
https://issues.apache.org/jira/browse/SOLR-10484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966157#comment-15966157
]
Christine Poerschke commented on SOLR-10484:
--------------------------------------------
bq. ... Wouldn't using SOLR-8332 require that the collection be brought up and
down while solrconfig was changed? ...
I'm thinking that _<some property>_ be known to Solr as the property that
identifies replicas to be avoided, it could be "property.inactive" as you
suggested and/or something configurable. Once configured (or present
out-of-the-box) then ReplicaListTransformer would basically not only re-order
the replica list but it would also filter out anything that needs to be
filtered out according to the _<some property>_ property.
bq. Another use-case is expanding capacity when a cluster is running hot. ...
people might want to temporarily disable a replica while "something" was done
to it without affecting the rest of the collection at all.
Yes, I can certainly see a use case for that too.
----
Could the idea of disabling a replica be even taken from temporary situation to
permanent feature?
* temporary situation: annotate a replica as not-to-be-used whilst something is
being done to it
* permanent situation: optionally annotate replicas and in request handlers
optionally configure annotations so that certain request handlers use (or not
use) replicas with certain annotations. This would for example allow within the
same collection the partitioning of traffic e.g. 'simple' search requests go to
one set of machines and more 'complex' search requests use a different request
handler and get routed to a different set of machines, but in terms of indexing
and monitoring etc. you are still dealing with just one collection essentially.
> Create a new replica property that keeps a replica from becoming active.
> ------------------------------------------------------------------------
>
> Key: SOLR-10484
> URL: https://issues.apache.org/jira/browse/SOLR-10484
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Erick Erickson
>
> See the user's list thread "Stopping a node from receiving any requests
> temporarily." for one example, but there are others. I can imagine operations
> people wanting to take a replica out of action for some time without
> affecting other replicas on that host.
> What do people think about having a property you could use with ADDREPLICA
> like "property.inactive" or something that kept the replica from coming up at
> all until the property was removed?
> DELETEREPLICAPROP could be used to remove it when operations was ready to
> have it become active.
> ADDREPLICAPROP could be used to add it to an active replica and should take
> that replica out of service.
> Whether we can piggy-back off of the core admin UNLOAD here I'm unclear on.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
