[
https://issues.apache.org/jira/browse/SOLR-7130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14338981#comment-14338981
]
Noble Paul commented on SOLR-7130:
----------------------------------
tests failing
{noformat}
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/11887/
Java: 64bit/jdk1.8.0_40-ea-b22 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC
1 tests failed.
FAILED: org.apache.solr.cloud.BasicDistributedZk2Test.test
Error Message:
._stateVer_:{collection1=16}!=null
Stack Trace:
junit.framework.AssertionFailedError: ._stateVer_:{collection1=16}!=null
at
__randomizedtesting.SeedInfo.seed([827245A9BAAE634A:A267A7314520EB2]:0)
at junit.framework.Assert.fail(Assert.java:50)
at
org.apache.solr.BaseDistributedSearchTestCase.compareSolrResponses(BaseDistributedSearchTestCase.java:873)
at
org.apache.solr.BaseDistributedSearchTestCase.compareResponses(BaseDistributedSearchTestCase.java:892)
at
org.apache.solr.BaseDistributedSearchTestCase.query(BaseDistributedSearchTestCase.java:593)
at
org.apache.solr.BaseDistributedSearchTestCase.query(BaseDistributedSearchTestCase.java:573)
at
org.apache.solr.BaseDistributedSearchTestCase.query(BaseDistributedSearchTestCase.java:552)
at
org.apache.solr.cloud.BasicDistributedZk2Test.brindDownShardIndexSomeDocsAndRecover(BasicDistributedZk2Test.java:280)
{noformat}
> Make stale state notification work without failing the requests
> ---------------------------------------------------------------
>
> Key: SOLR-7130
> URL: https://issues.apache.org/jira/browse/SOLR-7130
> Project: Solr
> Issue Type: Improvement
> Components: clients - java, SolrCloud, SolrJ
> Reporter: Shalin Shekhar Mangar
> Assignee: Noble Paul
> Fix For: Trunk, 5.1
>
> Attachments: SOLR-7130.patch, SOLR-7130.patch
>
>
> I wasn't sure whether to label this a bug or an improvement.
> For collections with stateFormat=2, we now fail requests (because of stale
> state) which we didn't previously. The client having stale cached cluster
> state is not a sufficient reason to fail and retry the entire request because
> in most of such cases, the node receiving the request is still perfectly
> capable of returning a valid response (either from local replicas or remote
> ones).
> We should find a better way to notify clients that they have stale state.
> Perhaps we can modify the response and add a "routing" section instead of
> outright exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
