[
https://issues.apache.org/jira/browse/SOLR-8575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109686#comment-15109686
]
Mark Miller commented on SOLR-8575:
-----------------------------------
bq. Using an internally stored length is probably better anyway, though.
The problem is that our internal size does not correlate with what we can
actually read, even after an hflush.
bq. updated size from the file then you have to use hsync with the length
update flag[1] using an HdfsOutputStream
Ah, interesting, I'll poke around that a bit to see if we want to do anything
different.
> 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
>
>
> [[email protected]] noticed some funny transaction log replay status
> logging a while back:
> active=true starting pos=444978 current pos=2855956 current size=16262 %
> read=17562
> active=true starting pos=444978 current pos=5748869 current size=16262 %
> read=35352
> 17562% read? Current size does not change as expected in this case?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
