This is an automated email from the ASF dual-hosted git repository.
urfree pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
The following commit(s) were added to refs/heads/main by this push:
new d29c0de1d8b Docs sync done from apache/pulsar(#116495c)
d29c0de1d8b is described below
commit d29c0de1d8b233c5522e60ecf34152bdad2a6f08
Author: Pulsar Site Updater <[email protected]>
AuthorDate: Mon May 23 18:05:47 2022 +0000
Docs sync done from apache/pulsar(#116495c)
---
site2/website-next/docs/concepts-architecture-overview.md | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/site2/website-next/docs/concepts-architecture-overview.md
b/site2/website-next/docs/concepts-architecture-overview.md
index 0d96b59f8ae..0bc2bb62875 100644
--- a/site2/website-next/docs/concepts-architecture-overview.md
+++ b/site2/website-next/docs/concepts-architecture-overview.md
@@ -8,13 +8,13 @@ At the highest level, a Pulsar instance is composed of one or
more Pulsar cluste
In a Pulsar cluster:
-* One or more brokers handles and load balances incoming messages from
producers, dispatches messages to consumers, communicates with the Pulsar
configuration store to handle various coordination tasks, stores messages in
BookKeeper instances (aka bookies), relies on a cluster-specific ZooKeeper
cluster for certain tasks, and more.
+* One or more brokers handles and [load
balances](administration-load-balance.md#load-balance-across-pulsar-brokers)
incoming messages from producers, dispatches messages to consumers,
communicates with the Pulsar configuration store to handle various coordination
tasks, stores messages in BookKeeper instances (aka bookies), relies on a
cluster-specific ZooKeeper cluster for certain tasks, and more.
* A BookKeeper cluster consisting of one or more bookies handles [persistent
storage](#persistent-storage) of messages.
* A ZooKeeper cluster specific to that cluster handles coordination tasks
between Pulsar clusters.
The diagram below provides an illustration of a Pulsar cluster:
-
+
At the broader instance level, an instance-wide ZooKeeper cluster called the
configuration store handles coordination tasks involving multiple clusters, for
example [geo-replication](concepts-replication).
@@ -91,7 +91,7 @@ persistent://my-tenant/my-namespace/my-topic
You can see an illustration of how brokers and bookies interact in the diagram
below:
-
+
### Ledgers
@@ -117,7 +117,7 @@ Internally, a single managed ledger uses multiple
BookKeeper ledgers to store th
### Journal storage
-In BookKeeper, *journal* files contain BookKeeper transaction logs. Before
making an update to a [ledger](#ledgers), a bookie needs to ensure that a
transaction describing the update is written to persistent (non-volatile)
storage. A new journal file is created once the bookie starts or the older
journal file reaches the journal file size threshold (configured using the
[`journalMaxSizeMB`](reference-configuration.md#bookkeeper-journalMaxSizeMB)
parameter).
+In BookKeeper, *journal* files contain BookKeeper transaction logs. Before
making an update to a [ledger](#ledgers), a bookie needs to ensure that a
transaction describing the update is written to persistent (non-volatile)
storage. A new journal file is created once the bookie starts or the older
journal file reaches the journal file size threshold (configured using the
[`journalMaxSizeMB`](reference-configuration.md#bookkeeper) parameter).
## Pulsar proxy
@@ -149,13 +149,13 @@ Some important things to know about the Pulsar proxy:
## Service discovery
-[Clients](getting-started-clients) connecting to Pulsar brokers need to be
able to communicate with an entire Pulsar instance using a single URL.
+[Clients](concepts-clients.md) connecting to Pulsar brokers need to be able to
communicate with an entire Pulsar instance using a single URL.
You can use your own service discovery system if you'd like. If you use your
own system, there is just one requirement: when a client performs an HTTP
request to an endpoint, such as `http://pulsar.us-west.example.com:8080`, the
client needs to be redirected to *some* active broker in the desired cluster,
whether via DNS, an HTTP or IP redirect, or some other means.
The diagram below illustrates Pulsar service discovery:
-
+
In this diagram, the Pulsar cluster is addressable via a single DNS name:
`pulsar-cluster.acme.com`. A [Python client](client-libraries-python), for
example, could access this Pulsar cluster like this:
