[
https://issues.apache.org/jira/browse/SOLR-12338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470098#comment-16470098
]
Cao Manh Dat edited comment on SOLR-12338 at 5/10/18 8:58 AM:
--------------------------------------------------------------
Hi [~ichattopadhyaya] yeah I think this is a good idea to do that. It may not
solve the case when a {{dbq1}} already re-ordered to ahead of {{add2}} or
{{add3}} in the tlog. But It won't make things worse than today.
was (Author: caomanhdat):
Hi [~ichattopadhyaya] yeah I think this is a good idea to do that. It may not
solve the case when a {{dbq1}} already re-ordered to ahead of {{add2}} or
{{add3}}. But It won't make things worse than today.
> 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
>
>
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
