[
https://issues.apache.org/jira/browse/SOLR-12338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16479675#comment-16479675
]
Yonik Seeley commented on SOLR-12338:
-------------------------------------
I haven't been following this issue, but the need to order things caught my
eye, primarily because we have a bunch of logic already that handles reordered
updates. I guess the issue is that buffered updates may not have a version (if
they haven't been through a leader?) If that's the case, perhaps an easier
path would be to assign a version and then let the existing reorder logic do
it's thing. I don't have the full picture here, so it's just some input to
consider.
> 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]
