[
https://issues.apache.org/jira/browse/ARTEMIS-2414?focusedWorklogId=277041&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-277041
]
ASF GitHub Bot logged work on ARTEMIS-2414:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 15/Jul/19 22:54
Start Date: 15/Jul/19 22:54
Worklog Time Spent: 10m
Work Description: asfgit commented on pull request #2740: ARTEMIS-2414
Sync before closing file in case data loss
URL: https://github.com/apache/activemq-artemis/pull/2740
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 277041)
Time Spent: 0.5h (was: 20m)
> Sync before closing file in case data loss
> ------------------------------------------
>
> Key: ARTEMIS-2414
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2414
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.9.0
> Reporter: yangwei
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When we open a new page, the page sync timer might sync the current page,
> i.e. the new page and after it responses are sent back to client. And the old
> page is closed(not synced), we may lose messages if server crashes before
> dirty page cache written back into disk.
> When we switch journal file to the new file, TimedBuffer::flushBatch will be
> called in the old file. Then the file would be synced except in the case user
> sets "journalDatasync" to false. For safety we'd better sync journal file
> before closing it.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
