This is an automated email from the ASF dual-hosted git repository.
chenhang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/bookkeeper.git
The following commit(s) were added to refs/heads/master by this push:
new d189c20ba0 split performance in two parts and add sticky reads part.
(#4131)
d189c20ba0 is described below
commit d189c20ba0a5a937c2a0e883db277aff00c31933
Author: kannar <[email protected]>
AuthorDate: Tue Jan 2 03:10:15 2024 +0100
split performance in two parts and add sticky reads part. (#4131)
Descriptions of the changes in this PR:
### Motivation
After the issue on disabled sticky reads, I'm adding this to improve
documentation about performance on reading.
### Changes
Master Issue: #4130
---
site3/website/docs/admin/bookies.md | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/site3/website/docs/admin/bookies.md
b/site3/website/docs/admin/bookies.md
index 2971a444c4..d289022d1a 100644
--- a/site3/website/docs/admin/bookies.md
+++ b/site3/website/docs/admin/bookies.md
@@ -18,8 +18,14 @@ There is no upper limit on the number of bookies that you
can run in a single en
### Performance
+#### Disks
+
To achieve optimal performance, BookKeeper requires each server to have at
least two disks. It's possible to run a bookie with a single disk but
performance will be significantly degraded.
+#### Sticky reads
+
+BookKeeper sticky reads enables bookie node to read entries efficiently. The
sticky reads are only available when ensemble (E) size is equal to quorum write
(Qw).
+
### ZooKeeper
There is no constraint on the number of ZooKeeper nodes you can run with
BookKeeper. A single machine running ZooKeeper in [standalone
mode](https://zookeeper.apache.org/doc/current/zookeeperStarted.html#sc_InstallingSingleMode)
is sufficient for BookKeeper, although for the sake of higher resilience we
recommend running ZooKeeper in [quorum
mode](https://zookeeper.apache.org/doc/current/zookeeperStarted.html#sc_RunningReplicatedZooKeeper)
with multiple servers.
