[
https://issues.apache.org/jira/browse/SOLR-17650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933686#comment-17933686
]
ASF subversion and git services commented on SOLR-17650:
--------------------------------------------------------
Commit 0a50edab23350947157731ab973a1f07ec7cf69a in solr's branch
refs/heads/deprecations from Houston Putman
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=0a50edab233 ]
SOLR-17650: Fix tests for unordered buffered updates (#3197)
> Determine executor for UpdateLog reading
> ----------------------------------------
>
> Key: SOLR-17650
> URL: https://issues.apache.org/jira/browse/SOLR-17650
> Project: Solr
> Issue Type: Improvement
> Reporter: Houston Putman
> Assignee: Houston Putman
> Priority: Major
> Labels: pull-request-available
> Fix For: 9.9
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Currently most operations that read from the updateLog use the
> OrderedExecutor that is setup for that purpose. However, TLOG replicas, when
> taking leadership, read from the updateLog without the executor (using the
> inSortedOrder = true parameter).
> SOLR-17391 changed the default executor for updateLog reading to use a fixed
> coreSize thread pool, which seems like started to enable parallel reading of
> the updateLog (which was supposed to be true beforehand, but it looks like
> our understanding of the executor was wrong).
> This ticket's purpose is to:
> # Investigate the correct way of reading the updateLog using an executor
> # Determine if there needs to actually be multiple ways
> (inSortedOrder=true/false)
> # Make sure the tests pass with whatever we decide.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
