bookkeeper
bookkeeper copied to clipboard
apache
Apache BookKeeper - a scalable, fault tolerant and low latency storage service optimized for append-only workloads
--- *Motivation* Generates the 4.15.1 docs and release note
Descriptions of the changes in this PR: ### Motivation fix #2220 ### Changes (Describe: what changes you have made) Master Issue: # > --- > In order to uphold a...
**BUG REPORT** ***Describe the bug*** Our Production pulsar cluster is multiple nodes with E-Qw-Qa(3-3-2), enabling auto-recovery by "./bin/bookkeeper shell autorecovery -enable", bookkeeper version is 4.14.1 . Now one bookie server...
Master Issue: #3338 ### Motivation As the Decommissioning bookie case， always change the bookie status to readonly firstly, and then wait some data expired, but always it has some ledgers...
fixed: https://github.com/apache/bookkeeper/issues/3322 ### Motivation We often find that the two write caches are full, causing write requests to block： The current write cache has only 2 blocks, which has the...
**Bookkeeper Version: 4.14.4** Our prod environment went wrong last week, all bookies were killed because of direct memory OOM, this happened after one bookie's disk was broken, we tried to...
**BUG REPORT** ***Describe the bug*** when I use pulsar script and run initialize-cluster-metadata, logs show an error that ipv6 ip is Invalid hostname. logs (I use x to replace some...
### Motivation SyncThread flush would invoke `checkpointSource.checkpointComplete` twice. it's unnecessary. ### Changes Change `org.apache.bookkeeper.bookie.LedgerStorage#flush` signature . add `doCheckpointComplete` parameter. default value is true, only set to false in `org.apache.bookkeeper.bookie.SyncThread#flush`
### Motivation We found one place where the bookie may lose data even though we turn on fsync for the journal. Condition: - One journal disk, and turn on fsync...
