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 2020/05/08 03:31:32 UTC
[GitHub] [pulsar] hangc0276 opened a new pull request #6915: Suggest adjust bookkeekper.conf default FlushEntryLogBytes to 256MB to improve bookie io throughput
hangc0276 opened a new pull request #6915:
URL: https://github.com/apache/pulsar/pull/6915
### Motivation
When AddEntry to bookie, entries will be written to memtable first and then written to the journal log. If it blocked in memtable write, the total AddEntry operation will be blocked, and the 99th AddEntry latency will increase.
When memtable full or checkpoint scheduled by timer, memtable will be swapped with backup one. However, if the backup memtable has not been flushed to disk complete yet, the memtable swap will be blocked, and the `AddEntry` operation will be blocked. So in which situation the backup memtable will be blocked?
When pulsar doing `catch-up read`, large amount of data will be read from ledger disk, and ledger disk io util will increase. At the same time, backup memtable will flush data from PageCache to disk triggered by OS (default is 30s) or rolling file no matter for HDD or SSD. It is hard to control the flush frequency and batch size in each flush cycle. In most cases, the flush batch size of each flush cycle is from 500MB to 1GB, which will lead to the ledger disk io util to 100% from 1s to 10s+, especially when large amount of read from the ledger disk in the same time.
### Changes
In order to decrease ledger disk high io util duration, we can control the backup memtable flush batch size from pageCache to disk. In my practice, the flush batch set to 256MB may perform better for HDD disk.
So I suggest adjust the default configuration `FlushEntryLogBytes` to 256MB in bookkeeper.conf to increase bookie io throughput.
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [pulsar] hangc0276 commented on pull request #6915: Suggest adjust bookkeekper.conf default FlushEntryLogBytes to 256MB to improve bookie io throughput
Posted by GitBox <gi...@apache.org>.
hangc0276 commented on pull request #6915:
URL: https://github.com/apache/pulsar/pull/6915#issuecomment-626070836
/pulsarbot run-failure-checks
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [pulsar] sijie commented on pull request #6915: Suggest adjust bookkeekper.conf default FlushEntryLogBytes to 256MB to improve bookie io throughput
Posted by GitBox <gi...@apache.org>.
sijie commented on pull request #6915:
URL: https://github.com/apache/pulsar/pull/6915#issuecomment-625977438
/pulsarbot run-failure-checks
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [pulsar] hangc0276 commented on pull request #6915: Suggest adjust bookkeekper.conf default FlushEntryLogBytes to 256MB to improve bookie io throughput
Posted by GitBox <gi...@apache.org>.
hangc0276 commented on pull request #6915:
URL: https://github.com/apache/pulsar/pull/6915#issuecomment-625649367
/pulsarbot run-failure-checks
----------------------------------------------------------------
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:
users@infra.apache.org