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 b28ef19a7fe Docs sync done from apache/pulsar(#22e8cb2)
b28ef19a7fe is described below
commit b28ef19a7fe185549c048c3bca1f2d82d93b5882
Author: Pulsar Site Updater <[email protected]>
AuthorDate: Mon Jul 25 06:01:39 2022 +0000
Docs sync done from apache/pulsar(#22e8cb2)
---
site2/website-next/docs/reference-configuration.md | 8 ++++++++
site2/website-next/docs/reference-metrics.md | 1 +
.../versioned_docs/version-2.3.0/reference-configuration.md | 9 +--------
3 files changed, 10 insertions(+), 8 deletions(-)
diff --git a/site2/website-next/docs/reference-configuration.md
b/site2/website-next/docs/reference-configuration.md
index e42ace8acf2..705c512dd7d 100644
--- a/site2/website-next/docs/reference-configuration.md
+++ b/site2/website-next/docs/reference-configuration.md
@@ -732,6 +732,14 @@ You can set the log level and configuration in the
[log4j2.yaml](https://github
|transactionBufferClientOperationTimeoutInMills| The transaction buffer
client's operation timeout in milliseconds.|3000|
|transactionBufferSnapshotMaxTransactionCount| Transaction buffer takes a
snapshot after the number of transaction operations reaches this value.|1000|
|transactionBufferSnapshotMinTimeInMillis| The interval between two snapshots
that the transaction buffer takes (in milliseconds).|5000|
+|transactionLogBatchedWriteEnabled| Provide a mechanism allowing the
Transaction Log Store to aggregate multiple records into a batched record and
persist into a single BK entry. This will make Pulsar transactions work more
efficiently, aka batched log. see:
https://github.com/apache/pulsar/issues/15370 |false|
+|transactionLogBatchedWriteMaxRecords| If enabled the feature that transaction
log batch, this attribute means maximum log records count in a batch |512|
+|transactionLogBatchedWriteMaxSize| If enabled the feature that transaction
log batch, this attribute means bytes size in a batch. |4m|
+|transactionLogBatchedWriteMaxDelayInMillis| If enabled the feature that
transaction log batch, this attribute means maximum wait time(in millis) for
the first record in a batch |1|
+|transactionPendingAckBatchedWriteEnabled| Provide a mechanism allowing the
Pending Ack Store to aggregate multiple records into a batched record and
persist into a single BK entry. This will make Pulsar transactions work more
efficiently, aka batched log. see:
https://github.com/apache/pulsar/issues/15370 |false|
+|transactionPendingAckBatchedWriteMaxRecords| If enabled the feature that
transaction pending ack log batch, this attribute means maximum log records
count in a batch. |512|
+|transactionPendingAckBatchedWriteMaxSize| If enabled the feature that
transaction pending ack log batch, this attribute means bytes size in a batch.
|4m|
+|transactionPendingAckBatchedWriteMaxDelayInMillis| If enabled the feature
that transaction pending ack log batch, this attribute means maximum wait
time(in millis) for the first record in a batch |1|
|defaultRetentionTimeInMinutes| |0|
|defaultRetentionSizeInMB| |0|
|keepAliveIntervalSeconds| |30|
diff --git a/site2/website-next/docs/reference-metrics.md
b/site2/website-next/docs/reference-metrics.md
index 0b7c98f2dc3..8e6078375c3 100644
--- a/site2/website-next/docs/reference-metrics.md
+++ b/site2/website-next/docs/reference-metrics.md
@@ -455,6 +455,7 @@ All the consumer metrics are labelled with the following
labels:
| pulsar_consumer_unacked_messages | Gauge | The total number of
unacknowledged messages of a consumer (messages). |
| pulsar_consumer_blocked_on_unacked_messages | Gauge | Indicate whether a
consumer is blocked on unacknowledged messages or not. <br /> <ul><li>1 means
the consumer is blocked on waiting unacknowledged messages to be
acked.</li><li>0 means the consumer is not blocked on waiting unacknowledged
messages to be acked.</li></ul> |
| pulsar_consumer_msg_rate_out | Gauge | The total message dispatch rate for a
consumer (message per second). |
+| pulsar_consumer_msg_ack_rate | Gauge | The total rate of message ack
(message per second). |
| pulsar_consumer_msg_throughput_out | Gauge | The total message dispatch
throughput for a consumer (byte per second). |
| pulsar_consumer_available_permits | Gauge | The available permits for for a
consumer. |
diff --git
a/site2/website-next/versioned_docs/version-2.3.0/reference-configuration.md
b/site2/website-next/versioned_docs/version-2.3.0/reference-configuration.md
index 2b91bd79cc8..c5e18166a94 100644
--- a/site2/website-next/versioned_docs/version-2.3.0/reference-configuration.md
+++ b/site2/website-next/versioned_docs/version-2.3.0/reference-configuration.md
@@ -215,14 +215,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|s3ManagedLedgerOffloadServiceEndpoint| For Amazon S3 ledger offload,
Alternative endpoint to connect to (useful for testing) ||
|s3ManagedLedgerOffloadMaxBlockSizeInBytes| For Amazon S3 ledger offload, Max
block size in bytes. (64MB by default, 5MB minimum) |67108864|
|s3ManagedLedgerOffloadReadBufferSizeInBytes| For Amazon S3 ledger offload,
Read buffer size in bytes (1MB by default) |1048576|
-|transactionLogBatchedWriteEnabled| Provide a mechanism allowing the
Transaction Log Store to aggregate multiple records into a batched record and
persist into a single BK entry. This will make Pulsar transactions work more
efficiently, aka batched log. see:
https://github.com/apache/pulsar/issues/15370 |false|
-|transactionLogBatchedWriteMaxRecords| If enabled the feature that transaction
log batch, this attribute means maximum log records count in a batch |512|
-|transactionLogBatchedWriteMaxSize| If enabled the feature that transaction
log batch, this attribute means bytes size in a batch. |4m|
-|transactionLogBatchedWriteMaxDelayInMillis| If enabled the feature that
transaction log batch, this attribute means maximum wait time(in millis) for
the first record in a batch |1|
-|transactionPendingAckBatchedWriteEnabled| Provide a mechanism allowing the
Pending Ack Store to aggregate multiple records into a batched record and
persist into a single BK entry. This will make Pulsar transactions work more
efficiently, aka batched log. see:
https://github.com/apache/pulsar/issues/15370 |false|
-|transactionPendingAckBatchedWriteMaxRecords| If enabled the feature that
transaction pending ack log batch, this attribute means maximum log records
count in a batch. |512|
-|transactionPendingAckBatchedWriteMaxSize| If enabled the feature that
transaction pending ack log batch, this attribute means bytes size in a batch.
|4m|
-|transactionPendingAckBatchedWriteMaxDelayInMillis| If enabled the feature
that transaction pending ack log batch, this attribute means maximum wait
time(in millis) for the first record in a batch |1|
+
