[
https://issues.apache.org/jira/browse/SOLR-12338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16480078#comment-16480078
]
Cao Manh Dat commented on SOLR-12338:
-------------------------------------
[[email protected]] The need to order things come from how we currently handle
reordered in-place updates. Currently, if a replica receives in-place update u2
which point to in-place update u1 which does not arrive yet, the replica will
fetch the full document from the leader. This is a very costly/risky logic to
handle reordered updates (ie: what if there are no leader to ask for the full
document). Luckily for us that reorder is not a common case right now, but if
we replay updates in a parallel and non-order way, above case can happen much
more frequently. Therefore In my opinion, it should be avoided.
> Replay buffering tlog in parallel
> ---------------------------------
>
> Key: SOLR-12338
> URL: https://issues.apache.org/jira/browse/SOLR-12338
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Cao Manh Dat
> Assignee: Cao Manh Dat
> Priority: Major
> Attachments: SOLR-12338.patch, SOLR-12338.patch, SOLR-12338.patch
>
>
> Since updates with different id are independent, therefore it is safe to
> replay them in parallel. This will significantly reduce recovering time of
> replicas in high load indexing environment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
