[
https://issues.apache.org/jira/browse/SOLR-10484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15967148#comment-15967148
]
Erick Erickson commented on SOLR-10484:
---------------------------------------
bq: Could the idea of disabling a replica be even taken from temporary
situation to permanent feature?
Is this another role perhaps? I'm thinking here of a collection that serves,
say, both user-level requests and "heavy" analytics requests. That way I could
run very complex analytics against a subset of my nodes that were segregated
from those serving live traffic.
So is my original "property" idea really a role? A role of "analytics_replica"
or "under_construction". Hmmm, I think I like the idea of an
"analytics_replica" role. a "role" of something like "under_construction" seems
better suited to be a property but I don't particularly have strong feelings
about that.
So your idea has something like every solr replica has an "analytics" (to
continue my example) request handler. But only those nodes that also have the
"analytics" _role_ assigned would have requests routed to them? And having a
role like this (or property I suppose) would also imply that no _other_
requests get routed here?
> 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]
