This is an automated email from the ASF dual-hosted git repository.
wave pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new e4092498cc0 [fix][doc] Fix wording in Tiered Storage (#16579)
e4092498cc0 is described below
commit e4092498cc01473a8a67441b082b9d86ed06890d
Author: Alexander Preuß <[email protected]>
AuthorDate: Wed Jul 13 21:49:41 2022 +0200
[fix][doc] Fix wording in Tiered Storage (#16579)
---
site2/docs/concepts-tiered-storage.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/site2/docs/concepts-tiered-storage.md
b/site2/docs/concepts-tiered-storage.md
index db0920aa478..d6b1a6df81d 100644
--- a/site2/docs/concepts-tiered-storage.md
+++ b/site2/docs/concepts-tiered-storage.md
@@ -12,6 +12,6 @@ One way to alleviate this cost is to use Tiered Storage. With
tiered storage, ol
> Data written to BookKeeper is replicated to 3 physical machines by default.
> However, once a segment is sealed in BookKeeper it becomes immutable and can
> be copied to long term storage. Long term storage can achieve cost savings
> by using mechanisms such as [Reed-Solomon error
> correction](https://en.wikipedia.org/wiki/Reed%E2%80%93Solomon_error_correction)
> to require fewer physical copies of data.
-Pulsar currently supports S3, Google Cloud Storage (GCS), and filesystem for
[long term store](cookbooks-tiered-storage.md). Offloading to long term storage
triggered via a Rest API or command line interface. The user passes in the
amount of topic data they wish to retain on BookKeeper, and the broker will
copy the backlog data to long term storage. The original data will then be
deleted from BookKeeper after a configured delay (4 hours by default).
+Pulsar currently supports S3, Google Cloud Storage (GCS), and filesystem for
[long term storage](cookbooks-tiered-storage.md). Offloading to long term
storage is triggered via a Rest API or command line interface. The user passes
in the amount of topic data they wish to retain on BookKeeper, and the broker
will copy the backlog data to long term storage. The original data will then be
deleted from BookKeeper after a configured delay (4 hours by default).
> For a guide for setting up tiered storage, see the [Tiered storage
> cookbook](cookbooks-tiered-storage.md).
