[
https://issues.apache.org/jira/browse/SOLR-8575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-8575:
------------------------------
Attachment: SOLR-8575.patch
Patch that fixes a couple issues and adds an isolated test that tries to target
tlog replay while buffering during recovery.
When we recalculated the size of the tlog, it keeps coming back the same as the
first size call, even if the tlog has grown. I think this has something to do
with an open file with hdfs.
We were somewhat incorrectly using that size for tlog progress logging. We
should having been using our internally tracked size.
bq. the same as the first size call, even if the tlog has grown.
And that kept a large performance issue in. When we opened the tlog at first,
we could replay fairly fast, but if we buffer updates while replay, we were
reopening the reader every update due to the stale size issue.
> Fix HDFSLogReader replay status numbers and a performance bug where we can
> reopen FSDataInputStream too often.
> --------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-8575
> URL: https://issues.apache.org/jira/browse/SOLR-8575
> Project: Solr
> Issue Type: Bug
> Reporter: Mark Miller
> Assignee: Mark Miller
> Attachments: SOLR-8575.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
