[
https://issues.apache.org/jira/browse/SOLR-8881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206744#comment-15206744
]
ASF subversion and git services commented on SOLR-8881:
-------------------------------------------------------
Commit c740e69622f3c0295498f02e76e42af6341ba333 in lucene-solr's branch
refs/heads/jira/SOLR-445 from [~hossman_luc...@fucit.org]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c740e69 ]
SOLR-8881: replace nocommits with doc note and link to jira
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
