Andrzej Bialecki created SOLR-13245:
----------------------------------------
Summary: 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
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
