[ 
https://issues.apache.org/jira/browse/SOLR-7130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333036#comment-14333036
 ] 

Noble Paul commented on SOLR-7130:
----------------------------------

When the node is capable of serving the requests locally, We can add the 
missing details into the payload. But, when we are proxying the requests to a 
remote server, we can't afford to unmarshal the response and add the extra 
information. So , for such requests, out options are 
# Send an exception as it does today
# Send the information in the response headers. I'm not sure about using HTTP 
headers because if we move to a different transport mechanism in the future it 
is bad

Another point we need to keep in mind is backward compatibility . Should we 
start sending the version number of SolrJ along with the request? So, based on 
that request parameter we can choose to throw an exception or send the 
information in the payload itself. This will also help us avoiding breaking 
backcompat in javabin format

> 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
>
>
> 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]

Reply via email to