[
https://issues.apache.org/jira/browse/BOOKKEEPER-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924564#comment-13924564
]
Sijie Guo commented on BOOKKEEPER-716:
--------------------------------------
we haven't encountered this issue yet. barries is used by filesystem to prevent
this for its metadata block and data block. but I don't think you could rely on
this from application perspective, since filesystem doesn't know what your data
means, although modern COW or transactional filesystem would handle this. so
from bookie perspective, it would be good to try the best to prevent this. And
aligning with block size is also a good practice, BOOKKEEPER-715 somehow is due
to flush entries isn't aligned to a block size.
> padding writes for bookie journal
> ---------------------------------
>
> Key: BOOKKEEPER-716
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-716
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-server
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Fix For: 4.3.0
>
> Attachments: BOOKKEEPER-716.diff, BOOKKEEPER-716_715.diff
>
>
> it would be better to pad journal writes to align sector size, which to avoid
> second syncing corrupt an already synced sector/page.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
