This is an automated email from the ASF dual-hosted git repository.
liuyu 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 d3848e2 [Doc] Add a parameter to forcefully close fenced topics
(#14289)
d3848e2 is described below
commit d3848e29775fed16c666822b07da63f99d531361
Author: momo-jun <[email protected]>
AuthorDate: Thu Feb 17 15:42:13 2022 +0800
[Doc] Add a parameter to forcefully close fenced topics (#14289)
---
site2/docs/reference-configuration.md | 3 ++-
site2/website/versioned_docs/version-2.7.0/reference-configuration.md | 3 ++-
site2/website/versioned_docs/version-2.7.1/reference-configuration.md | 3 ++-
site2/website/versioned_docs/version-2.7.2/reference-configuration.md | 3 ++-
site2/website/versioned_docs/version-2.7.3/reference-configuration.md | 3 ++-
site2/website/versioned_docs/version-2.7.4/reference-configuration.md | 3 ++-
site2/website/versioned_docs/version-2.8.0/reference-configuration.md | 3 ++-
site2/website/versioned_docs/version-2.8.1/reference-configuration.md | 3 ++-
site2/website/versioned_docs/version-2.8.2/reference-configuration.md | 3 ++-
site2/website/versioned_docs/version-2.9.0/reference-configuration.md | 3 ++-
site2/website/versioned_docs/version-2.9.1/reference-configuration.md | 3 ++-
11 files changed, 22 insertions(+), 11 deletions(-)
diff --git a/site2/docs/reference-configuration.md
b/site2/docs/reference-configuration.md
index fd8c948..16fb45f 100644
--- a/site2/docs/reference-configuration.md
+++ b/site2/docs/reference-configuration.md
@@ -257,6 +257,7 @@ brokerServiceCompactionThresholdInBytes|If the estimated
backlog size is greater
|isAllowAutoUpdateSchemaEnabled|Allow schema to be auto updated at broker
level.|true|
|schemaCompatibilityStrategy| The schema compatibility strategy at broker
level, see
[here](schema-evolution-compatibility.md#schema-compatibility-check-strategy)
for available values.|FULL|
|systemTopicSchemaCompatibilityStrategy| The schema compatibility strategy is
used for system topics, see
[here](schema-evolution-compatibility.md#schema-compatibility-check-strategy)
for available values.|ALWAYS_COMPATIBLE|
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
|offloadersDirectory|The directory for all the offloader
implementations.|./offloaders|
|bookkeeperMetadataServiceUri| Metadata service uri that bookkeeper is used
for loading corresponding metadata driver and resolving its metadata service
location. This value can be fetched using `bookkeeper shell whatisinstanceid`
command in BookKeeper cluster. For example:
zk+hierarchical://localhost:2181/ledgers. The metadata service uri list can
also be semicolon separated values like below:
zk+hierarchical://zk1:2181;zk2:2181;zk3:2181/ledgers ||
|bookkeeperClientAuthenticationPlugin| Authentication plugin to use when
connecting to bookies ||
@@ -568,8 +569,8 @@ You can set the log level and configuration in the
[log4j2.yaml](https://github
| brokerClientTlsProtocols | Specify the TLS protocols that the broker uses to
negotiate during TLS handshake. | |
| systemTopicEnabled | Enable/Disable system topics. | false |
| topicLevelPoliciesEnabled | Enable or disable topic level policies. Topic
level policies depends on the system topic. Please enable the system topic
first. | false |
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
| proxyRoles | Role names that are treated as "proxy roles". If the broker
sees a request with role as proxyRoles, it demands to see a valid original
principal. | |
-| authenticateOriginalAuthData | If this flag is set, the broker authenticates
the original Auth data. Otherwise, it just accepts the originalPrincipal and
authorizes it (if required). | false |
|authenticationEnabled| Enable authentication for the broker. |false|
|authenticationProviders| A comma-separated list of class names for
authentication providers. |false|
|authorizationEnabled| Enforce authorization in brokers. |false|
diff --git
a/site2/website/versioned_docs/version-2.7.0/reference-configuration.md
b/site2/website/versioned_docs/version-2.7.0/reference-configuration.md
index 7530c7d..c9c67fd 100644
--- a/site2/website/versioned_docs/version-2.7.0/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.7.0/reference-configuration.md
@@ -240,6 +240,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|exposePreciseBacklogInPrometheus| Enable expose the precise backlog stats,
set false to use published counter and consumed counter to calculate, this
would be more efficient but may be inaccurate. |false|
|schemaRegistryStorageClassName|The schema storage implementation used by this
broker.|org.apache.pulsar.broker.service.schema.BookkeeperSchemaStorageFactory|
|isSchemaValidationEnforced|Enforce schema validation on following cases: if a
producer without a schema attempts to produce to a topic with schema, the
producer will be failed to connect. PLEASE be carefully on using this, since
non-java clients don't support schema. If this setting is enabled, then
non-java clients fail to produce.|false|
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
|offloadersDirectory|The directory for all the offloader
implementations.|./offloaders|
|bookkeeperMetadataServiceUri| Metadata service uri that bookkeeper is used
for loading corresponding metadata driver and resolving its metadata service
location. This value can be fetched using `bookkeeper shell whatisinstanceid`
command in BookKeeper cluster. For example:
zk+hierarchical://localhost:2181/ledgers. The metadata service uri list can
also be semicolon separated values like below:
zk+hierarchical://zk1:2181;zk2:2181;zk3:2181/ledgers ||
|bookkeeperClientAuthenticationPlugin| Authentication plugin to use when
connecting to bookies ||
@@ -534,8 +535,8 @@ The [`pulsar-client`](reference-cli-tools.md#pulsar-client)
CLI tool can be used
| brokerClientTlsProtocols | Specify the TLS protocols that the broker uses to
negotiate during TLS handshake. | |
| systemTopicEnabled | Enable/Disable system topics. | false |
| topicLevelPoliciesEnabled | Enable or disable topic level policies. Topic
level policies depends on the system topic. Please enable the system topic
first. | false |
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
| proxyRoles | Role names that are treated as "proxy roles". If the broker
sees a request with role as proxyRoles, it demands to see a valid original
principal. | |
-| authenticateOriginalAuthData | If this flag is set, the broker authenticates
the original Auth data. Otherwise, it just accepts the originalPrincipal and
authorizes it (if required). | false |
|authenticationEnabled| Enable authentication for the broker. |false|
|authenticationProviders| A comma-separated list of class names for
authentication providers. |false|
|authorizationEnabled| Enforce authorization in brokers. |false|
diff --git
a/site2/website/versioned_docs/version-2.7.1/reference-configuration.md
b/site2/website/versioned_docs/version-2.7.1/reference-configuration.md
index cd513fb..06c1904 100644
--- a/site2/website/versioned_docs/version-2.7.1/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.7.1/reference-configuration.md
@@ -240,6 +240,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|exposePreciseBacklogInPrometheus| Enable expose the precise backlog stats,
set false to use published counter and consumed counter to calculate, this
would be more efficient but may be inaccurate. |false|
|schemaRegistryStorageClassName|The schema storage implementation used by this
broker.|org.apache.pulsar.broker.service.schema.BookkeeperSchemaStorageFactory|
|isSchemaValidationEnforced|Enforce schema validation on following cases: if a
producer without a schema attempts to produce to a topic with schema, the
producer will be failed to connect. PLEASE be carefully on using this, since
non-java clients don't support schema. If this setting is enabled, then
non-java clients fail to produce.|false|
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
|offloadersDirectory|The directory for all the offloader
implementations.|./offloaders|
|bookkeeperMetadataServiceUri| Metadata service uri that bookkeeper is used
for loading corresponding metadata driver and resolving its metadata service
location. This value can be fetched using `bookkeeper shell whatisinstanceid`
command in BookKeeper cluster. For example:
zk+hierarchical://localhost:2181/ledgers. The metadata service uri list can
also be semicolon separated values like below:
zk+hierarchical://zk1:2181;zk2:2181;zk3:2181/ledgers ||
|bookkeeperClientAuthenticationPlugin| Authentication plugin to use when
connecting to bookies ||
@@ -534,8 +535,8 @@ The [`pulsar-client`](reference-cli-tools.md#pulsar-client)
CLI tool can be used
| brokerClientTlsProtocols | Specify the TLS protocols that the broker uses to
negotiate during TLS handshake. | |
| systemTopicEnabled | Enable/Disable system topics. | false |
| topicLevelPoliciesEnabled | Enable or disable topic level policies. Topic
level policies depends on the system topic. Please enable the system topic
first. | false |
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
| proxyRoles | Role names that are treated as "proxy roles". If the broker
sees a request with role as proxyRoles, it demands to see a valid original
principal. | |
-| authenticateOriginalAuthData | If this flag is set, the broker authenticates
the original Auth data. Otherwise, it just accepts the originalPrincipal and
authorizes it (if required). | false |
|authenticationEnabled| Enable authentication for the broker. |false|
|authenticationProviders| A comma-separated list of class names for
authentication providers. |false|
|authorizationEnabled| Enforce authorization in brokers. |false|
diff --git
a/site2/website/versioned_docs/version-2.7.2/reference-configuration.md
b/site2/website/versioned_docs/version-2.7.2/reference-configuration.md
index f701f7f..99e0420 100644
--- a/site2/website/versioned_docs/version-2.7.2/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.7.2/reference-configuration.md
@@ -240,6 +240,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|exposePreciseBacklogInPrometheus| Enable expose the precise backlog stats,
set false to use published counter and consumed counter to calculate, this
would be more efficient but may be inaccurate. |false|
|schemaRegistryStorageClassName|The schema storage implementation used by this
broker.|org.apache.pulsar.broker.service.schema.BookkeeperSchemaStorageFactory|
|isSchemaValidationEnforced|Enforce schema validation on following cases: if a
producer without a schema attempts to produce to a topic with schema, the
producer will be failed to connect. PLEASE be carefully on using this, since
non-java clients don't support schema. If this setting is enabled, then
non-java clients fail to produce.|false|
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
|offloadersDirectory|The directory for all the offloader
implementations.|./offloaders|
|bookkeeperMetadataServiceUri| Metadata service uri that bookkeeper is used
for loading corresponding metadata driver and resolving its metadata service
location. This value can be fetched using `bookkeeper shell whatisinstanceid`
command in BookKeeper cluster. For example:
zk+hierarchical://localhost:2181/ledgers. The metadata service uri list can
also be semicolon separated values like below:
zk+hierarchical://zk1:2181;zk2:2181;zk3:2181/ledgers ||
|bookkeeperClientAuthenticationPlugin| Authentication plugin to use when
connecting to bookies ||
@@ -534,8 +535,8 @@ The [`pulsar-client`](reference-cli-tools.md#pulsar-client)
CLI tool can be used
| brokerClientTlsProtocols | Specify the TLS protocols that the broker uses to
negotiate during TLS handshake. | |
| systemTopicEnabled | Enable/Disable system topics. | false |
| topicLevelPoliciesEnabled | Enable or disable topic level policies. Topic
level policies depends on the system topic. Please enable the system topic
first. | false |
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
| proxyRoles | Role names that are treated as "proxy roles". If the broker
sees a request with role as proxyRoles, it demands to see a valid original
principal. | |
-| authenticateOriginalAuthData | If this flag is set, the broker authenticates
the original Auth data. Otherwise, it just accepts the originalPrincipal and
authorizes it (if required). | false |
|authenticationEnabled| Enable authentication for the broker. |false|
|authenticationProviders| A comma-separated list of class names for
authentication providers. |false|
|authorizationEnabled| Enforce authorization in brokers. |false|
diff --git
a/site2/website/versioned_docs/version-2.7.3/reference-configuration.md
b/site2/website/versioned_docs/version-2.7.3/reference-configuration.md
index ed7a625..ccdf9a7 100644
--- a/site2/website/versioned_docs/version-2.7.3/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.7.3/reference-configuration.md
@@ -240,6 +240,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|exposePreciseBacklogInPrometheus| Enable expose the precise backlog stats,
set false to use published counter and consumed counter to calculate, this
would be more efficient but may be inaccurate. |false|
|schemaRegistryStorageClassName|The schema storage implementation used by this
broker.|org.apache.pulsar.broker.service.schema.BookkeeperSchemaStorageFactory|
|isSchemaValidationEnforced|Enforce schema validation on following cases: if a
producer without a schema attempts to produce to a topic with schema, the
producer will be failed to connect. PLEASE be carefully on using this, since
non-java clients don't support schema. If this setting is enabled, then
non-java clients fail to produce.|false|
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
|offloadersDirectory|The directory for all the offloader
implementations.|./offloaders|
|bookkeeperMetadataServiceUri| Metadata service uri that bookkeeper is used
for loading corresponding metadata driver and resolving its metadata service
location. This value can be fetched using `bookkeeper shell whatisinstanceid`
command in BookKeeper cluster. For example:
zk+hierarchical://localhost:2181/ledgers. The metadata service uri list can
also be semicolon separated values like below:
zk+hierarchical://zk1:2181;zk2:2181;zk3:2181/ledgers ||
|bookkeeperClientAuthenticationPlugin| Authentication plugin to use when
connecting to bookies ||
@@ -534,8 +535,8 @@ The [`pulsar-client`](reference-cli-tools.md#pulsar-client)
CLI tool can be used
| brokerClientTlsProtocols | Specify the TLS protocols that the broker uses to
negotiate during TLS handshake. | |
| systemTopicEnabled | Enable/Disable system topics. | false |
| topicLevelPoliciesEnabled | Enable or disable topic level policies. Topic
level policies depends on the system topic. Please enable the system topic
first. | false |
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
| proxyRoles | Role names that are treated as "proxy roles". If the broker
sees a request with role as proxyRoles, it demands to see a valid original
principal. | |
-| authenticateOriginalAuthData | If this flag is set, the broker authenticates
the original Auth data. Otherwise, it just accepts the originalPrincipal and
authorizes it (if required). | false |
|authenticationEnabled| Enable authentication for the broker. |false|
|authenticationProviders| A comma-separated list of class names for
authentication providers. |false|
|authorizationEnabled| Enforce authorization in brokers. |false|
diff --git
a/site2/website/versioned_docs/version-2.7.4/reference-configuration.md
b/site2/website/versioned_docs/version-2.7.4/reference-configuration.md
index c0dab30..f24f818 100644
--- a/site2/website/versioned_docs/version-2.7.4/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.7.4/reference-configuration.md
@@ -240,6 +240,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|exposePreciseBacklogInPrometheus| Enable expose the precise backlog stats,
set false to use published counter and consumed counter to calculate, this
would be more efficient but may be inaccurate. |false|
|schemaRegistryStorageClassName|The schema storage implementation used by this
broker.|org.apache.pulsar.broker.service.schema.BookkeeperSchemaStorageFactory|
|isSchemaValidationEnforced|Enforce schema validation on following cases: if a
producer without a schema attempts to produce to a topic with schema, the
producer will be failed to connect. PLEASE be carefully on using this, since
non-java clients don't support schema. If this setting is enabled, then
non-java clients fail to produce.|false|
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
|offloadersDirectory|The directory for all the offloader
implementations.|./offloaders|
|bookkeeperMetadataServiceUri| Metadata service uri that bookkeeper is used
for loading corresponding metadata driver and resolving its metadata service
location. This value can be fetched using `bookkeeper shell whatisinstanceid`
command in BookKeeper cluster. For example:
zk+hierarchical://localhost:2181/ledgers. The metadata service uri list can
also be semicolon separated values like below:
zk+hierarchical://zk1:2181;zk2:2181;zk3:2181/ledgers ||
|bookkeeperClientAuthenticationPlugin| Authentication plugin to use when
connecting to bookies ||
@@ -534,8 +535,8 @@ The [`pulsar-client`](reference-cli-tools.md#pulsar-client)
CLI tool can be used
| brokerClientTlsProtocols | Specify the TLS protocols that the broker uses to
negotiate during TLS handshake. | |
| systemTopicEnabled | Enable/Disable system topics. | false |
| topicLevelPoliciesEnabled | Enable or disable topic level policies. Topic
level policies depends on the system topic. Please enable the system topic
first. | false |
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
| proxyRoles | Role names that are treated as "proxy roles". If the broker
sees a request with role as proxyRoles, it demands to see a valid original
principal. | |
-| authenticateOriginalAuthData | If this flag is set, the broker authenticates
the original Auth data. Otherwise, it just accepts the originalPrincipal and
authorizes it (if required). | false |
|authenticationEnabled| Enable authentication for the broker. |false|
|authenticationProviders| A comma-separated list of class names for
authentication providers. |false|
|authorizationEnabled| Enforce authorization in brokers. |false|
diff --git
a/site2/website/versioned_docs/version-2.8.0/reference-configuration.md
b/site2/website/versioned_docs/version-2.8.0/reference-configuration.md
index ee2618e..8f2575f 100644
--- a/site2/website/versioned_docs/version-2.8.0/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.8.0/reference-configuration.md
@@ -242,6 +242,7 @@ brokerServiceCompactionThresholdInBytes|If the estimated
backlog size is greater
|exposePreciseBacklogInPrometheus| Enable expose the precise backlog stats,
set false to use published counter and consumed counter to calculate, this
would be more efficient but may be inaccurate. |false|
|schemaRegistryStorageClassName|The schema storage implementation used by this
broker.|org.apache.pulsar.broker.service.schema.BookkeeperSchemaStorageFactory|
|isSchemaValidationEnforced|Enforce schema validation on following cases: if a
producer without a schema attempts to produce to a topic with schema, the
producer will be failed to connect. PLEASE be carefully on using this, since
non-java clients don't support schema. If this setting is enabled, then
non-java clients fail to produce.|false|
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
|offloadersDirectory|The directory for all the offloader
implementations.|./offloaders|
|bookkeeperMetadataServiceUri| Metadata service uri that bookkeeper is used
for loading corresponding metadata driver and resolving its metadata service
location. This value can be fetched using `bookkeeper shell whatisinstanceid`
command in BookKeeper cluster. For example:
zk+hierarchical://localhost:2181/ledgers. The metadata service uri list can
also be semicolon separated values like below:
zk+hierarchical://zk1:2181;zk2:2181;zk3:2181/ledgers ||
|bookkeeperClientAuthenticationPlugin| Authentication plugin to use when
connecting to bookies ||
@@ -543,8 +544,8 @@ You can set the log level and configuration in the
[log4j2.yaml](https://github
| brokerClientTlsProtocols | Specify the TLS protocols that the broker uses to
negotiate during TLS handshake. | |
| systemTopicEnabled | Enable/Disable system topics. | false |
| topicLevelPoliciesEnabled | Enable or disable topic level policies. Topic
level policies depends on the system topic. Please enable the system topic
first. | false |
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
| proxyRoles | Role names that are treated as "proxy roles". If the broker
sees a request with role as proxyRoles, it demands to see a valid original
principal. | |
-| authenticateOriginalAuthData | If this flag is set, the broker authenticates
the original Auth data. Otherwise, it just accepts the originalPrincipal and
authorizes it (if required). | false |
|authenticationEnabled| Enable authentication for the broker. |false|
|authenticationProviders| A comma-separated list of class names for
authentication providers. |false|
|authorizationEnabled| Enforce authorization in brokers. |false|
diff --git
a/site2/website/versioned_docs/version-2.8.1/reference-configuration.md
b/site2/website/versioned_docs/version-2.8.1/reference-configuration.md
index 2c49d15..f259abd 100644
--- a/site2/website/versioned_docs/version-2.8.1/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.8.1/reference-configuration.md
@@ -242,6 +242,7 @@ brokerServiceCompactionThresholdInBytes|If the estimated
backlog size is greater
|exposePreciseBacklogInPrometheus| Enable expose the precise backlog stats,
set false to use published counter and consumed counter to calculate, this
would be more efficient but may be inaccurate. |false|
|schemaRegistryStorageClassName|The schema storage implementation used by this
broker.|org.apache.pulsar.broker.service.schema.BookkeeperSchemaStorageFactory|
|isSchemaValidationEnforced|Enforce schema validation on following cases: if a
producer without a schema attempts to produce to a topic with schema, the
producer will be failed to connect. PLEASE be carefully on using this, since
non-java clients don't support schema. If this setting is enabled, then
non-java clients fail to produce.|false|
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
|offloadersDirectory|The directory for all the offloader
implementations.|./offloaders|
|bookkeeperMetadataServiceUri| Metadata service uri that bookkeeper is used
for loading corresponding metadata driver and resolving its metadata service
location. This value can be fetched using `bookkeeper shell whatisinstanceid`
command in BookKeeper cluster. For example:
zk+hierarchical://localhost:2181/ledgers. The metadata service uri list can
also be semicolon separated values like below:
zk+hierarchical://zk1:2181;zk2:2181;zk3:2181/ledgers ||
|bookkeeperClientAuthenticationPlugin| Authentication plugin to use when
connecting to bookies ||
@@ -544,8 +545,8 @@ You can set the log level and configuration in the
[log4j2.yaml](https://github
| brokerClientTlsProtocols | Specify the TLS protocols that the broker uses to
negotiate during TLS handshake. | |
| systemTopicEnabled | Enable/Disable system topics. | false |
| topicLevelPoliciesEnabled | Enable or disable topic level policies. Topic
level policies depends on the system topic. Please enable the system topic
first. | false |
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
| proxyRoles | Role names that are treated as "proxy roles". If the broker
sees a request with role as proxyRoles, it demands to see a valid original
principal. | |
-| authenticateOriginalAuthData | If this flag is set, the broker authenticates
the original Auth data. Otherwise, it just accepts the originalPrincipal and
authorizes it (if required). | false |
|authenticationEnabled| Enable authentication for the broker. |false|
|authenticationProviders| A comma-separated list of class names for
authentication providers. |false|
|authorizationEnabled| Enforce authorization in brokers. |false|
diff --git
a/site2/website/versioned_docs/version-2.8.2/reference-configuration.md
b/site2/website/versioned_docs/version-2.8.2/reference-configuration.md
index aa31668..241ca64 100644
--- a/site2/website/versioned_docs/version-2.8.2/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.8.2/reference-configuration.md
@@ -243,6 +243,7 @@ brokerServiceCompactionThresholdInBytes|If the estimated
backlog size is greater
|exposePreciseBacklogInPrometheus| Enable expose the precise backlog stats,
set false to use published counter and consumed counter to calculate, this
would be more efficient but may be inaccurate. |false|
|schemaRegistryStorageClassName|The schema storage implementation used by this
broker.|org.apache.pulsar.broker.service.schema.BookkeeperSchemaStorageFactory|
|isSchemaValidationEnforced|Enforce schema validation on following cases: if a
producer without a schema attempts to produce to a topic with schema, the
producer will be failed to connect. PLEASE be carefully on using this, since
non-java clients don't support schema. If this setting is enabled, then
non-java clients fail to produce.|false|
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
|offloadersDirectory|The directory for all the offloader
implementations.|./offloaders|
|bookkeeperMetadataServiceUri| Metadata service uri that bookkeeper is used
for loading corresponding metadata driver and resolving its metadata service
location. This value can be fetched using `bookkeeper shell whatisinstanceid`
command in BookKeeper cluster. For example:
zk+hierarchical://localhost:2181/ledgers. The metadata service uri list can
also be semicolon separated values like below:
zk+hierarchical://zk1:2181;zk2:2181;zk3:2181/ledgers ||
|bookkeeperClientAuthenticationPlugin| Authentication plugin to use when
connecting to bookies ||
@@ -545,8 +546,8 @@ You can set the log level and configuration in the
[log4j2.yaml](https://github
| brokerClientTlsProtocols | Specify the TLS protocols that the broker uses to
negotiate during TLS handshake. | |
| systemTopicEnabled | Enable/Disable system topics. | false |
| topicLevelPoliciesEnabled | Enable or disable topic level policies. Topic
level policies depends on the system topic. Please enable the system topic
first. | false |
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
| proxyRoles | Role names that are treated as "proxy roles". If the broker
sees a request with role as proxyRoles, it demands to see a valid original
principal. | |
-| authenticateOriginalAuthData | If this flag is set, the broker authenticates
the original Auth data. Otherwise, it just accepts the originalPrincipal and
authorizes it (if required). | false |
|authenticationEnabled| Enable authentication for the broker. |false|
|authenticationProviders| A comma-separated list of class names for
authentication providers. |false|
|authorizationEnabled| Enforce authorization in brokers. |false|
diff --git
a/site2/website/versioned_docs/version-2.9.0/reference-configuration.md
b/site2/website/versioned_docs/version-2.9.0/reference-configuration.md
index 4b0b4ca..1751a4e 100644
--- a/site2/website/versioned_docs/version-2.9.0/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.9.0/reference-configuration.md
@@ -242,6 +242,7 @@ brokerServiceCompactionThresholdInBytes|If the estimated
backlog size is greater
|exposePreciseBacklogInPrometheus| Enable expose the precise backlog stats,
set false to use published counter and consumed counter to calculate, this
would be more efficient but may be inaccurate. |false|
|schemaRegistryStorageClassName|The schema storage implementation used by this
broker.|org.apache.pulsar.broker.service.schema.BookkeeperSchemaStorageFactory|
|isSchemaValidationEnforced|Enforce schema validation on following cases: if a
producer without a schema attempts to produce to a topic with schema, the
producer will be failed to connect. PLEASE be carefully on using this, since
non-java clients don't support schema. If this setting is enabled, then
non-java clients fail to produce.|false|
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
|offloadersDirectory|The directory for all the offloader
implementations.|./offloaders|
|bookkeeperMetadataServiceUri| Metadata service uri that bookkeeper is used
for loading corresponding metadata driver and resolving its metadata service
location. This value can be fetched using `bookkeeper shell whatisinstanceid`
command in BookKeeper cluster. For example:
zk+hierarchical://localhost:2181/ledgers. The metadata service uri list can
also be semicolon separated values like below:
zk+hierarchical://zk1:2181;zk2:2181;zk3:2181/ledgers ||
|bookkeeperClientAuthenticationPlugin| Authentication plugin to use when
connecting to bookies ||
@@ -528,8 +529,8 @@ You can set the log level and configuration in the
[log4j2.yaml](https://github
| brokerClientTlsProtocols | Specify the TLS protocols that the broker uses to
negotiate during TLS handshake. | |
| systemTopicEnabled | Enable/Disable system topics. | false |
| topicLevelPoliciesEnabled | Enable or disable topic level policies. Topic
level policies depends on the system topic. Please enable the system topic
first. | false |
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
| proxyRoles | Role names that are treated as "proxy roles". If the broker
sees a request with role as proxyRoles, it demands to see a valid original
principal. | |
-| authenticateOriginalAuthData | If this flag is set, the broker authenticates
the original Auth data. Otherwise, it just accepts the originalPrincipal and
authorizes it (if required). | false |
|authenticationEnabled| Enable authentication for the broker. |false|
|authenticationProviders| A comma-separated list of class names for
authentication providers. |false|
|authorizationEnabled| Enforce authorization in brokers. |false|
diff --git
a/site2/website/versioned_docs/version-2.9.1/reference-configuration.md
b/site2/website/versioned_docs/version-2.9.1/reference-configuration.md
index ed68ff5..1e68f10 100644
--- a/site2/website/versioned_docs/version-2.9.1/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.9.1/reference-configuration.md
@@ -242,6 +242,7 @@ brokerServiceCompactionThresholdInBytes|If the estimated
backlog size is greater
|exposePreciseBacklogInPrometheus| Enable expose the precise backlog stats,
set false to use published counter and consumed counter to calculate, this
would be more efficient but may be inaccurate. |false|
|schemaRegistryStorageClassName|The schema storage implementation used by this
broker.|org.apache.pulsar.broker.service.schema.BookkeeperSchemaStorageFactory|
|isSchemaValidationEnforced|Enforce schema validation on following cases: if a
producer without a schema attempts to produce to a topic with schema, the
producer will be failed to connect. PLEASE be carefully on using this, since
non-java clients don't support schema. If this setting is enabled, then
non-java clients fail to produce.|false|
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
|offloadersDirectory|The directory for all the offloader
implementations.|./offloaders|
|bookkeeperMetadataServiceUri| Metadata service uri that bookkeeper is used
for loading corresponding metadata driver and resolving its metadata service
location. This value can be fetched using `bookkeeper shell whatisinstanceid`
command in BookKeeper cluster. For example:
zk+hierarchical://localhost:2181/ledgers. The metadata service uri list can
also be semicolon separated values like below:
zk+hierarchical://zk1:2181;zk2:2181;zk3:2181/ledgers ||
|bookkeeperClientAuthenticationPlugin| Authentication plugin to use when
connecting to bookies ||
@@ -528,8 +529,8 @@ You can set the log level and configuration in the
[log4j2.yaml](https://github
| brokerClientTlsProtocols | Specify the TLS protocols that the broker uses to
negotiate during TLS handshake. | |
| systemTopicEnabled | Enable/Disable system topics. | false |
| topicLevelPoliciesEnabled | Enable or disable topic level policies. Topic
level policies depends on the system topic. Please enable the system topic
first. | false |
+| topicFencingTimeoutSeconds | If a topic remains fenced for a certain time
period (in seconds), it is closed forcefully. If set to 0 or a negative number,
the fenced topic is not closed. | 0 |
| proxyRoles | Role names that are treated as "proxy roles". If the broker
sees a request with role as proxyRoles, it demands to see a valid original
principal. | |
-| authenticateOriginalAuthData | If this flag is set, the broker authenticates
the original Auth data. Otherwise, it just accepts the originalPrincipal and
authorizes it (if required). | false |
|authenticationEnabled| Enable authentication for the broker. |false|
|authenticationProviders| A comma-separated list of class names for
authentication providers. |false|
|authorizationEnabled| Enforce authorization in brokers. |false|
