Anonymitaet commented on a change in pull request #7244:
URL: https://github.com/apache/pulsar/pull/7244#discussion_r440863412
##########
File path: site2/docs/reference-configuration.md
##########
@@ -372,21 +382,86 @@ The
[`pulsar-client`](reference-cli-tools.md#pulsar-client) CLI tool can be used
|ttlDurationDefaultInSeconds| The default ttl for namespaces if ttl is not
configured at namespace policies. |0|
|brokerDeleteInactiveTopicsEnabled| Enable the deletion of inactive topics.
|true|
|brokerDeleteInactiveTopicsFrequencySeconds| How often to check for inactive
topics, in seconds. |60|
+| maxPendingPublishdRequestsPerConnection | Maximum pending publish requests
per connection to avoid keeping large number of pending requests in memory |
1000|
|messageExpiryCheckIntervalInMinutes| How often to proactively check and
purged expired messages. |5|
|activeConsumerFailoverDelayTimeMillis| How long to delay rewinding cursor and
dispatching messages when active consumer is changed. |1000|
+| subscriptionExpirationTimeMinutes | How long to delete inactive
subscriptions from last consuming. When it is set to 0, inactive subscriptions
are not deleted automatically | 0 |
+| subscriptionRedeliveryTrackerEnabled | Enable subscription message
redelivery tracker to send redelivery count to consumer. | true |
+| subscriptionKeySharedUseConsistentHashing | In the Key_Shared subscription
mode, with default AUTO_SPLIT mode, use splitting ranges or consistent hashing
to reassign keys to new consumers. | false |
+| subscriptionKeySharedConsistentHashingReplicaPoints | In the Key_Shared
subscription mode, number of points in the consistent-hashing ring. The greater
the number, the more equal the assignment of keys to consumers. | 100 |
+| subscriptionExpiryCheckIntervalInMinutes | How frequently to proactively
check and purge expired subscription |5 |
+| brokerDeduplicationEnabled | Set the default behavior for message
deduplication in the broker. This can be overridden per-namespace. If it is
enabled, the broker rejects messages that are already stored in the topic. |
false |
+| brokerDeduplicationMaxNumberOfProducers | Maximum number of producer
information that it's going to be persisted for deduplication purposes | 10000 |
+| brokerDeduplicationEntriesInterval | Number of entries after which a
deduplication information snapshot is taken. A greater interval leads to less
snapshots being taken though it would increase the topic recovery time, when
the entries published after the snapshot need to be replayed. | 1000 |
+| brokerDeduplicationProducerInactivityTimeoutMinutes | The time of inactivity
(in minutes) after which the broker discards deduplication information related
to a disconnected producer. | 360 |
+| defaultNumberOfNamespaceBundles | When a namespace is created without
specifying the number of bundle, this value is used as the default setting.| 4 |
|clientLibraryVersionCheckEnabled| Enable checks for minimum allowed client
library version. |false|
|clientLibraryVersionCheckAllowUnversioned| Allow client libraries with no
version information |true|
|statusFilePath| The path for the file used to determine the rotation status
for the broker when responding to service discovery health checks
|/usr/local/apache/htdocs|
|maxUnackedMessagesPerConsumer| The maximum number of unacknowledged messages
allowed to be received by consumers on a shared subscription. The broker will
stop sending messages to a consumer once this limit is reached or until the
consumer begins acknowledging messages. A value of 0 disables the unacked
message limit check and thus allows consumers to receive messages without any
restrictions. |50000|
|maxUnackedMessagesPerSubscription| The same as above, except per subscription
rather than per consumer. |200000|
+| maxUnackedMessagesPerBroker | Maximum number of unacknowledged messages
allowed per broker. Once this limit reaches, the broker stops dispatching
messages to all shared subscription which has higher number of unacknowledged
messages until subscriptions start acknowledging messages back and
unacknowledged messages count reaches to limit/2. When the value is set to 0,
unacknowledged message limit check is disabled and broker does not block
dispatchers. | 0 |
+| maxUnackedMessagesPerSubscriptionOnBrokerBlocked | Once the broker reaches
maxUnackedMessagesPerBroker limit, it blocks subscriptions which has higher
unacknowledged messages than this percentage limit and subscription does not
receive any new messages until that subscription acknowledges messages back. |
0.16 |
|maxNumPartitionsPerPartitionedTopic|Max number of partitions per partitioned
topic. Use 0 or negative number to disable the check|0|
+| topicPublisherThrottlingTickTimeMillis | Tick time to schedule task that
checks topic publish rate limiting across all topics. A lower value can give
more accuracy while throttling publish but it uses more CPU to perform frequent
check. When the value is set to 0, publish throttling is disabled. | 2|
+| brokerPublisherThrottlingTickTimeMillis | Tick time to schedule task that
checks broker publish rate limiting across all topics. A lower value can give
more accuracy while throttling publish but it uses more CPU to perform frequent
check. When the value is set to 0, publish throttling is disabled. |50 |
+| brokerPublisherThrottlingMaxMessageRate | Maximum rate (in 1 seconds) of
messages allowed to publish for a broker if the message rate limiting is
enabled. When the value is set to 0, message rate limiting is disabled. | 0|
+| brokerPublisherThrottlingMaxByteRate | Maximum rate (in 1 seconds) of bytes
allowed to publish for a broker if the byte rate limiting is enabled. When the
value is set to 0, byte rate limiting is disabled. | 0 |
Review comment:
```suggestion
| brokerPublisherThrottlingMaxByteRate | Maximum rate (in 1 second) of bytes
allowed to publish for a broker if the byte rate limiting is enabled. When the
value is set to 0, the byte rate limiting is disabled. | 0 |
```
##########
File path: site2/docs/reference-configuration.md
##########
@@ -372,21 +382,86 @@ The
[`pulsar-client`](reference-cli-tools.md#pulsar-client) CLI tool can be used
|ttlDurationDefaultInSeconds| The default ttl for namespaces if ttl is not
configured at namespace policies. |0|
|brokerDeleteInactiveTopicsEnabled| Enable the deletion of inactive topics.
|true|
|brokerDeleteInactiveTopicsFrequencySeconds| How often to check for inactive
topics, in seconds. |60|
+| maxPendingPublishdRequestsPerConnection | Maximum pending publish requests
per connection to avoid keeping large number of pending requests in memory |
1000|
|messageExpiryCheckIntervalInMinutes| How often to proactively check and
purged expired messages. |5|
|activeConsumerFailoverDelayTimeMillis| How long to delay rewinding cursor and
dispatching messages when active consumer is changed. |1000|
+| subscriptionExpirationTimeMinutes | How long to delete inactive
subscriptions from last consuming. When it is set to 0, inactive subscriptions
are not deleted automatically | 0 |
+| subscriptionRedeliveryTrackerEnabled | Enable subscription message
redelivery tracker to send redelivery count to consumer. | true |
+| subscriptionKeySharedUseConsistentHashing | In the Key_Shared subscription
mode, with default AUTO_SPLIT mode, use splitting ranges or consistent hashing
to reassign keys to new consumers. | false |
+| subscriptionKeySharedConsistentHashingReplicaPoints | In the Key_Shared
subscription mode, number of points in the consistent-hashing ring. The greater
the number, the more equal the assignment of keys to consumers. | 100 |
+| subscriptionExpiryCheckIntervalInMinutes | How frequently to proactively
check and purge expired subscription |5 |
+| brokerDeduplicationEnabled | Set the default behavior for message
deduplication in the broker. This can be overridden per-namespace. If it is
enabled, the broker rejects messages that are already stored in the topic. |
false |
+| brokerDeduplicationMaxNumberOfProducers | Maximum number of producer
information that it's going to be persisted for deduplication purposes | 10000 |
+| brokerDeduplicationEntriesInterval | Number of entries after which a
deduplication information snapshot is taken. A greater interval leads to less
snapshots being taken though it would increase the topic recovery time, when
the entries published after the snapshot need to be replayed. | 1000 |
+| brokerDeduplicationProducerInactivityTimeoutMinutes | The time of inactivity
(in minutes) after which the broker discards deduplication information related
to a disconnected producer. | 360 |
+| defaultNumberOfNamespaceBundles | When a namespace is created without
specifying the number of bundle, this value is used as the default setting.| 4 |
|clientLibraryVersionCheckEnabled| Enable checks for minimum allowed client
library version. |false|
|clientLibraryVersionCheckAllowUnversioned| Allow client libraries with no
version information |true|
|statusFilePath| The path for the file used to determine the rotation status
for the broker when responding to service discovery health checks
|/usr/local/apache/htdocs|
|maxUnackedMessagesPerConsumer| The maximum number of unacknowledged messages
allowed to be received by consumers on a shared subscription. The broker will
stop sending messages to a consumer once this limit is reached or until the
consumer begins acknowledging messages. A value of 0 disables the unacked
message limit check and thus allows consumers to receive messages without any
restrictions. |50000|
|maxUnackedMessagesPerSubscription| The same as above, except per subscription
rather than per consumer. |200000|
+| maxUnackedMessagesPerBroker | Maximum number of unacknowledged messages
allowed per broker. Once this limit reaches, the broker stops dispatching
messages to all shared subscription which has higher number of unacknowledged
messages until subscriptions start acknowledging messages back and
unacknowledged messages count reaches to limit/2. When the value is set to 0,
unacknowledged message limit check is disabled and broker does not block
dispatchers. | 0 |
+| maxUnackedMessagesPerSubscriptionOnBrokerBlocked | Once the broker reaches
maxUnackedMessagesPerBroker limit, it blocks subscriptions which has higher
unacknowledged messages than this percentage limit and subscription does not
receive any new messages until that subscription acknowledges messages back. |
0.16 |
|maxNumPartitionsPerPartitionedTopic|Max number of partitions per partitioned
topic. Use 0 or negative number to disable the check|0|
+| topicPublisherThrottlingTickTimeMillis | Tick time to schedule task that
checks topic publish rate limiting across all topics. A lower value can give
more accuracy while throttling publish but it uses more CPU to perform frequent
check. When the value is set to 0, publish throttling is disabled. | 2|
+| brokerPublisherThrottlingTickTimeMillis | Tick time to schedule task that
checks broker publish rate limiting across all topics. A lower value can give
more accuracy while throttling publish but it uses more CPU to perform frequent
check. When the value is set to 0, publish throttling is disabled. |50 |
+| brokerPublisherThrottlingMaxMessageRate | Maximum rate (in 1 seconds) of
messages allowed to publish for a broker if the message rate limiting is
enabled. When the value is set to 0, message rate limiting is disabled. | 0|
Review comment:
```suggestion
| brokerPublisherThrottlingMaxMessageRate | Maximum rate (in 1 second) of
messages allowed to publish for a broker if the message rate limiting is
enabled. When the value is set to 0, message rate limiting is disabled. | 0|
```
##########
File path: site2/docs/reference-configuration.md
##########
@@ -372,21 +382,86 @@ The
[`pulsar-client`](reference-cli-tools.md#pulsar-client) CLI tool can be used
|ttlDurationDefaultInSeconds| The default ttl for namespaces if ttl is not
configured at namespace policies. |0|
|brokerDeleteInactiveTopicsEnabled| Enable the deletion of inactive topics.
|true|
|brokerDeleteInactiveTopicsFrequencySeconds| How often to check for inactive
topics, in seconds. |60|
+| maxPendingPublishdRequestsPerConnection | Maximum pending publish requests
per connection to avoid keeping large number of pending requests in memory |
1000|
|messageExpiryCheckIntervalInMinutes| How often to proactively check and
purged expired messages. |5|
|activeConsumerFailoverDelayTimeMillis| How long to delay rewinding cursor and
dispatching messages when active consumer is changed. |1000|
+| subscriptionExpirationTimeMinutes | How long to delete inactive
subscriptions from last consuming. When it is set to 0, inactive subscriptions
are not deleted automatically | 0 |
+| subscriptionRedeliveryTrackerEnabled | Enable subscription message
redelivery tracker to send redelivery count to consumer. | true |
+| subscriptionKeySharedUseConsistentHashing | In the Key_Shared subscription
mode, with default AUTO_SPLIT mode, use splitting ranges or consistent hashing
to reassign keys to new consumers. | false |
+| subscriptionKeySharedConsistentHashingReplicaPoints | In the Key_Shared
subscription mode, number of points in the consistent-hashing ring. The greater
the number, the more equal the assignment of keys to consumers. | 100 |
+| subscriptionExpiryCheckIntervalInMinutes | How frequently to proactively
check and purge expired subscription |5 |
+| brokerDeduplicationEnabled | Set the default behavior for message
deduplication in the broker. This can be overridden per-namespace. If it is
enabled, the broker rejects messages that are already stored in the topic. |
false |
+| brokerDeduplicationMaxNumberOfProducers | Maximum number of producer
information that it's going to be persisted for deduplication purposes | 10000 |
+| brokerDeduplicationEntriesInterval | Number of entries after which a
deduplication information snapshot is taken. A greater interval leads to less
snapshots being taken though it would increase the topic recovery time, when
the entries published after the snapshot need to be replayed. | 1000 |
+| brokerDeduplicationProducerInactivityTimeoutMinutes | The time of inactivity
(in minutes) after which the broker discards deduplication information related
to a disconnected producer. | 360 |
+| defaultNumberOfNamespaceBundles | When a namespace is created without
specifying the number of bundle, this value is used as the default setting.| 4 |
Review comment:
```suggestion
| defaultNumberOfNamespaceBundles | When a namespace is created without
specifying the number of bundles, this value is used as the default setting.| 4
|
```
##########
File path: site2/docs/reference-configuration.md
##########
@@ -372,21 +382,86 @@ The
[`pulsar-client`](reference-cli-tools.md#pulsar-client) CLI tool can be used
|ttlDurationDefaultInSeconds| The default ttl for namespaces if ttl is not
configured at namespace policies. |0|
|brokerDeleteInactiveTopicsEnabled| Enable the deletion of inactive topics.
|true|
|brokerDeleteInactiveTopicsFrequencySeconds| How often to check for inactive
topics, in seconds. |60|
+| maxPendingPublishdRequestsPerConnection | Maximum pending publish requests
per connection to avoid keeping large number of pending requests in memory |
1000|
|messageExpiryCheckIntervalInMinutes| How often to proactively check and
purged expired messages. |5|
|activeConsumerFailoverDelayTimeMillis| How long to delay rewinding cursor and
dispatching messages when active consumer is changed. |1000|
+| subscriptionExpirationTimeMinutes | How long to delete inactive
subscriptions from last consuming. When it is set to 0, inactive subscriptions
are not deleted automatically | 0 |
Review comment:
```suggestion
| subscriptionExpirationTimeMinutes | How long to delete inactive
subscriptions from last consumption. When it is set to 0, inactive
subscriptions are not deleted automatically | 0 |
```
##########
File path: site2/docs/reference-configuration.md
##########
@@ -372,21 +382,86 @@ The
[`pulsar-client`](reference-cli-tools.md#pulsar-client) CLI tool can be used
|ttlDurationDefaultInSeconds| The default ttl for namespaces if ttl is not
configured at namespace policies. |0|
|brokerDeleteInactiveTopicsEnabled| Enable the deletion of inactive topics.
|true|
|brokerDeleteInactiveTopicsFrequencySeconds| How often to check for inactive
topics, in seconds. |60|
+| maxPendingPublishdRequestsPerConnection | Maximum pending publish requests
per connection to avoid keeping large number of pending requests in memory |
1000|
|messageExpiryCheckIntervalInMinutes| How often to proactively check and
purged expired messages. |5|
|activeConsumerFailoverDelayTimeMillis| How long to delay rewinding cursor and
dispatching messages when active consumer is changed. |1000|
+| subscriptionExpirationTimeMinutes | How long to delete inactive
subscriptions from last consuming. When it is set to 0, inactive subscriptions
are not deleted automatically | 0 |
+| subscriptionRedeliveryTrackerEnabled | Enable subscription message
redelivery tracker to send redelivery count to consumer. | true |
+| subscriptionKeySharedUseConsistentHashing | In the Key_Shared subscription
mode, with default AUTO_SPLIT mode, use splitting ranges or consistent hashing
to reassign keys to new consumers. | false |
+| subscriptionKeySharedConsistentHashingReplicaPoints | In the Key_Shared
subscription mode, number of points in the consistent-hashing ring. The greater
the number, the more equal the assignment of keys to consumers. | 100 |
+| subscriptionExpiryCheckIntervalInMinutes | How frequently to proactively
check and purge expired subscription |5 |
+| brokerDeduplicationEnabled | Set the default behavior for message
deduplication in the broker. This can be overridden per-namespace. If it is
enabled, the broker rejects messages that are already stored in the topic. |
false |
+| brokerDeduplicationMaxNumberOfProducers | Maximum number of producer
information that it's going to be persisted for deduplication purposes | 10000 |
+| brokerDeduplicationEntriesInterval | Number of entries after which a
deduplication information snapshot is taken. A greater interval leads to less
snapshots being taken though it would increase the topic recovery time, when
the entries published after the snapshot need to be replayed. | 1000 |
+| brokerDeduplicationProducerInactivityTimeoutMinutes | The time of inactivity
(in minutes) after which the broker discards deduplication information related
to a disconnected producer. | 360 |
+| defaultNumberOfNamespaceBundles | When a namespace is created without
specifying the number of bundle, this value is used as the default setting.| 4 |
|clientLibraryVersionCheckEnabled| Enable checks for minimum allowed client
library version. |false|
|clientLibraryVersionCheckAllowUnversioned| Allow client libraries with no
version information |true|
|statusFilePath| The path for the file used to determine the rotation status
for the broker when responding to service discovery health checks
|/usr/local/apache/htdocs|
|maxUnackedMessagesPerConsumer| The maximum number of unacknowledged messages
allowed to be received by consumers on a shared subscription. The broker will
stop sending messages to a consumer once this limit is reached or until the
consumer begins acknowledging messages. A value of 0 disables the unacked
message limit check and thus allows consumers to receive messages without any
restrictions. |50000|
|maxUnackedMessagesPerSubscription| The same as above, except per subscription
rather than per consumer. |200000|
+| maxUnackedMessagesPerBroker | Maximum number of unacknowledged messages
allowed per broker. Once this limit reaches, the broker stops dispatching
messages to all shared subscription which has higher number of unacknowledged
messages until subscriptions start acknowledging messages back and
unacknowledged messages count reaches to limit/2. When the value is set to 0,
unacknowledged message limit check is disabled and broker does not block
dispatchers. | 0 |
Review comment:
```suggestion
| maxUnackedMessagesPerBroker | Maximum number of unacknowledged messages
allowed per broker. Once this limit reaches, the broker stops dispatching
messages to all shared subscriptions which has a higher number of
unacknowledged messages until subscriptions start acknowledging messages back
and unacknowledged messages count reaches to limit/2. When the value is set to
0, unacknowledged message limit check is disabled and broker does not block
dispatchers. | 0 |
```
##########
File path: site2/docs/reference-configuration.md
##########
@@ -372,21 +382,86 @@ The
[`pulsar-client`](reference-cli-tools.md#pulsar-client) CLI tool can be used
|ttlDurationDefaultInSeconds| The default ttl for namespaces if ttl is not
configured at namespace policies. |0|
|brokerDeleteInactiveTopicsEnabled| Enable the deletion of inactive topics.
|true|
|brokerDeleteInactiveTopicsFrequencySeconds| How often to check for inactive
topics, in seconds. |60|
+| maxPendingPublishdRequestsPerConnection | Maximum pending publish requests
per connection to avoid keeping large number of pending requests in memory |
1000|
|messageExpiryCheckIntervalInMinutes| How often to proactively check and
purged expired messages. |5|
|activeConsumerFailoverDelayTimeMillis| How long to delay rewinding cursor and
dispatching messages when active consumer is changed. |1000|
+| subscriptionExpirationTimeMinutes | How long to delete inactive
subscriptions from last consuming. When it is set to 0, inactive subscriptions
are not deleted automatically | 0 |
+| subscriptionRedeliveryTrackerEnabled | Enable subscription message
redelivery tracker to send redelivery count to consumer. | true |
+| subscriptionKeySharedUseConsistentHashing | In the Key_Shared subscription
mode, with default AUTO_SPLIT mode, use splitting ranges or consistent hashing
to reassign keys to new consumers. | false |
+| subscriptionKeySharedConsistentHashingReplicaPoints | In the Key_Shared
subscription mode, number of points in the consistent-hashing ring. The greater
the number, the more equal the assignment of keys to consumers. | 100 |
Review comment:
```suggestion
| subscriptionKeySharedConsistentHashingReplicaPoints | In the Key_Shared
subscription mode, the number of points in the consistent-hashing ring. The
greater the number, the more equal the assignment of keys to consumers. | 100 |
```
##########
File path: site2/docs/reference-configuration.md
##########
@@ -372,21 +382,86 @@ The
[`pulsar-client`](reference-cli-tools.md#pulsar-client) CLI tool can be used
|ttlDurationDefaultInSeconds| The default ttl for namespaces if ttl is not
configured at namespace policies. |0|
|brokerDeleteInactiveTopicsEnabled| Enable the deletion of inactive topics.
|true|
|brokerDeleteInactiveTopicsFrequencySeconds| How often to check for inactive
topics, in seconds. |60|
+| maxPendingPublishdRequestsPerConnection | Maximum pending publish requests
per connection to avoid keeping large number of pending requests in memory |
1000|
|messageExpiryCheckIntervalInMinutes| How often to proactively check and
purged expired messages. |5|
|activeConsumerFailoverDelayTimeMillis| How long to delay rewinding cursor and
dispatching messages when active consumer is changed. |1000|
+| subscriptionExpirationTimeMinutes | How long to delete inactive
subscriptions from last consuming. When it is set to 0, inactive subscriptions
are not deleted automatically | 0 |
+| subscriptionRedeliveryTrackerEnabled | Enable subscription message
redelivery tracker to send redelivery count to consumer. | true |
+| subscriptionKeySharedUseConsistentHashing | In the Key_Shared subscription
mode, with default AUTO_SPLIT mode, use splitting ranges or consistent hashing
to reassign keys to new consumers. | false |
+| subscriptionKeySharedConsistentHashingReplicaPoints | In the Key_Shared
subscription mode, number of points in the consistent-hashing ring. The greater
the number, the more equal the assignment of keys to consumers. | 100 |
+| subscriptionExpiryCheckIntervalInMinutes | How frequently to proactively
check and purge expired subscription |5 |
+| brokerDeduplicationEnabled | Set the default behavior for message
deduplication in the broker. This can be overridden per-namespace. If it is
enabled, the broker rejects messages that are already stored in the topic. |
false |
+| brokerDeduplicationMaxNumberOfProducers | Maximum number of producer
information that it's going to be persisted for deduplication purposes | 10000 |
+| brokerDeduplicationEntriesInterval | Number of entries after which a
deduplication information snapshot is taken. A greater interval leads to less
snapshots being taken though it would increase the topic recovery time, when
the entries published after the snapshot need to be replayed. | 1000 |
+| brokerDeduplicationProducerInactivityTimeoutMinutes | The time of inactivity
(in minutes) after which the broker discards deduplication information related
to a disconnected producer. | 360 |
+| defaultNumberOfNamespaceBundles | When a namespace is created without
specifying the number of bundle, this value is used as the default setting.| 4 |
|clientLibraryVersionCheckEnabled| Enable checks for minimum allowed client
library version. |false|
|clientLibraryVersionCheckAllowUnversioned| Allow client libraries with no
version information |true|
|statusFilePath| The path for the file used to determine the rotation status
for the broker when responding to service discovery health checks
|/usr/local/apache/htdocs|
|maxUnackedMessagesPerConsumer| The maximum number of unacknowledged messages
allowed to be received by consumers on a shared subscription. The broker will
stop sending messages to a consumer once this limit is reached or until the
consumer begins acknowledging messages. A value of 0 disables the unacked
message limit check and thus allows consumers to receive messages without any
restrictions. |50000|
|maxUnackedMessagesPerSubscription| The same as above, except per subscription
rather than per consumer. |200000|
+| maxUnackedMessagesPerBroker | Maximum number of unacknowledged messages
allowed per broker. Once this limit reaches, the broker stops dispatching
messages to all shared subscription which has higher number of unacknowledged
messages until subscriptions start acknowledging messages back and
unacknowledged messages count reaches to limit/2. When the value is set to 0,
unacknowledged message limit check is disabled and broker does not block
dispatchers. | 0 |
+| maxUnackedMessagesPerSubscriptionOnBrokerBlocked | Once the broker reaches
maxUnackedMessagesPerBroker limit, it blocks subscriptions which has higher
unacknowledged messages than this percentage limit and subscription does not
receive any new messages until that subscription acknowledges messages back. |
0.16 |
Review comment:
```suggestion
| maxUnackedMessagesPerSubscriptionOnBrokerBlocked | Once the broker reaches
maxUnackedMessagesPerBroker limit, it blocks subscriptions which have higher
unacknowledged messages than this percentage limit and subscription does not
receive any new messages until that subscription acknowledges messages back. |
0.16 |
```
##########
File path: site2/docs/reference-configuration.md
##########
@@ -403,9 +478,23 @@ The
[`pulsar-client`](reference-cli-tools.md#pulsar-client) CLI tool can be used
|bookkeeperClientIsolationGroups|||
|bookkeeperClientSecondaryIsolationGroups| Enable bookie secondary-isolation
group if bookkeeperClientIsolationGroups doesn't have enough bookie available.
||
|bookkeeperClientMinAvailableBookiesInIsolationGroups| Minimum bookies that
should be available as part of bookkeeperClientIsolationGroups else broker will
include bookkeeperClientSecondaryIsolationGroups bookies in isolated list. ||
+| bookkeeperTLSProviderFactoryClass | Set the client security provider factory
class name. | org.apache.bookkeeper.tls.TLSContextFactory |
+| bookkeeperTLSClientAuthentication | Enable TLS authentication with bookie. |
false |
+| bookkeeperTLSKeyFileType | Supported type: PEM, JKS, PKCS12. | PEM |
+| bookkeeperTLSTrustCertTypes | Supported type: PEM, JKS, PKCS12. | PEM |
+| bookkeeperTLSKeyStorePasswordPath | Path to file containing keystore
password, if the client keystore is password protected. | |
bookkeeperTLSTrustStorePasswordPath | Path to file containing truststore
password, if the client truststore is password protected. | |
+| bookkeeperTLSKeyFilePath | Path for the TLS private key file. | |
+| bookkeeperTLSCertificateFilePath | Path for the TLS certificate file. | |
+| bookkeeperTLSTrustCertsFilePath | Path for the trusted TLS certificate file.
| |
+| bookkeeperDiskWeightBasedPlacementEnabled | Enable/Disable disk weight based
placement. | false |
+| bookkeeperExplicitLacIntervalInMills | Set the interval to check the need
for sending an explicit LAC. When the value is set to 0, no explicit LAC is
sent. | 0 |
+| bookkeeperClientExposeStatsToPrometheus | Expose BookKeeper client managed
ledger stats to prometheus. | false |
Review comment:
```suggestion
| bookkeeperClientExposeStatsToPrometheus | Expose BookKeeper client managed
ledger stats to Prometheus. | false |
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
