[
https://issues.apache.org/jira/browse/SOLR-10484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966120#comment-15966120
]
Erick Erickson commented on SOLR-10484:
---------------------------------------
Interesting, I'd never have thought of that. I'm thinking of a temporary state
that wouldn't affect any other replicas in the collection. Wouldn't using
SOLR-8332 require that the collection be brought up and down while solrconfig
was changed? If that's the case it would be a problem. I admit I know little
about SOLR-8332 so maybe I'm way off base.
Another use-case is expanding capacity when a cluster is running hot. There is
SOLR-6086 where a replica becomes active when it's added before autowarming is
complete which got me to thinking about situations where operations people
might want to temporarily disable a replica while "something" was done to it
without affecting the rest of the collection at all.
I admit largely speculating here. When I thought of it my reaction was "this
seems so useful I wonder why we haven't done it". Which then lead to "Well, if
we haven't done this yet maybe it's not that usefull" so I opened this JIRA to
see what others had to say.
> 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]
