leiless edited a comment on issue #10832:
URL: https://github.com/apache/pulsar/issues/10832#issuecomment-855166878
Instead of `fsync(2)` per message manner, I pursuing `fsync(2)` in batch(as
a whole).
Explicitly, `fsync(2)` for the last msg in a list.
Which enforces previous messages to be persisted in the disk?
(Roughly speaking, you can treat `fsync(2)` as ACK?)
```
Before:
+-------+-------+-------+-------+
| Msg N | ... | Msg 2 | Msg 1 | -> Head up
| fsync | fsync | fsync | fsync |
+-------+-------+-------+-------+
After:
+-------+-------+-------+-------+
| Msg N | ... | Msg 2 | Msg 1 | -> Head up
|*fsync*| | | |
+-------+-------+-------+-------+
```
The idea is somewhat like
[Consumer.acknowledgeCumulative(MessageId)](https://pulsar.apache.org/api/client/org/apache/pulsar/client/api/Consumer.html#acknowledgeCumulative-org.apache.pulsar.client.api.MessageId-)
but for Producer side.
--
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]
