[
https://issues.apache.org/jira/browse/OAK-6653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162898#comment-16162898
]
Francesco Mari commented on OAK-6653:
-------------------------------------
I think the best option is to expose the persisted head as a new method from
{{Revisions}}, and use that method in {{DefaultStandbyHeadReader}} to read the
{{RecordId}} of the head state.
> Standby server must always send the persisted head to clients
> -------------------------------------------------------------
>
> Key: OAK-6653
> URL: https://issues.apache.org/jira/browse/OAK-6653
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar, tarmk-standby
> Affects Versions: 1.7.7
> Reporter: Andrei Dulceanu
> Assignee: Andrei Dulceanu
> Labels: cold-standby
> Fix For: 1.7.8
>
>
> Currently the standby server sends an un-persisted head record to clients.
> Under normal circumstances, the TarMK flush thread is able to persist it and
> its corresponding segment at a 5 seconds interval.
> However, there are cases (uploading a very large blob > 10 GB) in which the
> flush thread writes the segment too late, and the 20s allowed by
> {{FileStoreUtil#readSegmentWithRetry}} are not enough. Therefore the server
> can't read the segment containing the head record and a timeout occurs on the
> client.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
