[
https://issues.apache.org/jira/browse/SOLR-13245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16767228#comment-16767228
]
Joel Bernstein edited comment on SOLR-13245 at 2/13/19 2:14 PM:
----------------------------------------------------------------
One thing to add, this bug only occurs if there are two replicas from the same
collection on that Solr instance that the daemon is sent to.
So another work around or possibly we can call it a best practice is to create
a worker collection specifically to run daemons which does not have multiple
replicas collocated on the same Solr instance.
was (Author: joel.bernstein):
One thing to add, this bug only occurs if there a two replicas from the same
collection on that Solr instance that the daemon is sent to.
So another work around or possibly we can call it a best practice is to create
a worker collection specifically to run daemons which does not have multiple
replicas collocated on the same Solr instance.
> Status checking of streaming "daemon"-s is buggy and misleading
> ---------------------------------------------------------------
>
> Key: SOLR-13245
> URL: https://issues.apache.org/jira/browse/SOLR-13245
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: streaming expressions
> Affects Versions: 7.7, 8.0, master (9.0)
> Reporter: Andrzej Bialecki
> Priority: Major
>
> When a {{daemon}} is started Solr randomly picks a replica to process that
> request and then it executes in the context of that particular replica. The
> response from the request mentions this specifically:
> {code:java}
> {
> "result-set":{
> "docs":[{
> "DaemonOp":"Deamon:testD1 started on
> gettingstarted_shard2_replica_n6"}
> ,{
> "EOF":true}]}}
> {code}
> Subsequent requests to {{/solr/gettingstarted/stream?action=list}} only
> sometimes return the status of this daemon, specifically only when the
> request is randomly routed to the actual replica that the daemon is running
> on - in other cases the response doesn't show the running daemon.
> This is very easy to reproduce using the {{cloud}} example with 2 (local)
> nodes and a source collection with multiple shards and multiple replicas.
> Currently the only workaround is to request the status using a non-cloud core
> URL - in this case a request to
> {{/solr/gettingstarted_shard2_replica_n6/stream?action=list}} always returns
> correct status.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
