You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2018/11/28 20:34:38 UTC
[GitHub] sijie commented on issue #1334: Experimental settings to achieve 5
ms latency
sijie commented on issue #1334: Experimental settings to achieve 5 ms latency
URL: https://github.com/apache/pulsar/issues/1334#issuecomment-442595034
> What's the order for Pulsar, when we disable forced fsync (and also when its on)?
pulsar's replication mechanism is handled by bookkeeper. bookkeeper is using a parallel replication scheme. with that being said, broker writes the data concurrently to a set of bookies and waiting for a majority (write-quorum-size) of responses coming back before acknowledging the publisher.
so the difference between fsync enabled and fsync disabled is that:
- fsync enabled: bookie sends responses back to brokers when it successfully writes data to filesystem and the data is fsynced to disks.
- fsync disabled: bookie sends responses back to brokers when it successfully writes data to filesystem.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services