lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SOLR-8881) test & document (and improve as possible) behavior of TolerantUpdateProcessor while shard splitting is in progress
Date Mon, 21 Mar 2016 23:26:25 GMT
Hoss Man created SOLR-8881:
------------------------------

             Summary: test & document (and improve as possible) behavior of TolerantUpdateProcessor
while shard splitting is in progress
                 Key: SOLR-8881
                 URL: https://issues.apache.org/jira/browse/SOLR-8881
             Project: Solr
          Issue Type: Improvement
            Reporter: Hoss Man


TolerantUpdateProcessor is being added in SOLR-445 but it's not entirely obvious what the
behavior should be when using something like this is used in conjunction with Shard Splitting.

In particular what should / shouldn't happen if an update error occurs on a subShardLeader
(while the shard is actively being split) after the update already succeded on the original
shard leader.  when TUP is not used, this error is propogated back to the client -- but if
TUP is being used, then should the subShardLeader' error be propogated back as a tolerated
error, or a hard failure?




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message