[
https://issues.apache.org/jira/browse/SOLR-8129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14971917#comment-14971917
]
Yonik Seeley commented on SOLR-8129:
------------------------------------
Thanks for clarifying Tim, it had me wondering what I was missing.
bq. maybe HttpSolrCall can return an error immediately if container has been
shutdown?
Yeah, I think there are a lot of places we could check if the container has
been shut down... not sure yet what is the best place. I think *new* calls
would be rejected already... it's really existing streaming calls that are the
issue I think.
I'm still first trying to find out why one update was rejected and then updates
that happened after that were still processed though. This particular failure
would not have happened without that piece as well.
> HdfsChaosMonkeyNothingIsSafeTest failures
> -----------------------------------------
>
> Key: SOLR-8129
> URL: https://issues.apache.org/jira/browse/SOLR-8129
> Project: Solr
> Issue Type: Bug
> Reporter: Yonik Seeley
> Attachments: fail.151005_064958, fail.151005_080319
>
>
> New HDFS chaos test in SOLR-8123 hits a number of types of failures,
> including shard inconsistency.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
