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 c64fc8d6a4c Docs sync done from apache/pulsar(#e16a35d)
c64fc8d6a4c is described below
commit c64fc8d6a4cdbbfa65a53bddd38ccf7a85b51c45
Author: Pulsar Site Updater <[email protected]>
AuthorDate: Thu Aug 18 12:01:44 2022 +0000
Docs sync done from apache/pulsar(#e16a35d)
---
site2/website-next/docs/client-libraries-java.md | 2 +-
.../website-next/docs/developing-binary-protocol.md | 2 +-
.../client-libraries-java.md | 21 ---------------------
.../developing-binary-protocol.md | 18 ------------------
.../version-2.10.0/client-libraries-java.md | 2 +-
.../version-2.10.0/developing-binary-protocol.md | 2 +-
.../version-2.10.1/client-libraries-java.md | 2 +-
.../version-2.10.1/developing-binary-protocol.md | 2 +-
.../version-2.10.x/developing-binary-protocol.md | 2 +-
.../version-2.2.0/client-libraries-java.md | 21 ---------------------
.../version-2.2.1/developing-binary-protocol.md | 18 ------------------
.../version-2.3.0/client-libraries-java.md | 21 ---------------------
.../version-2.3.0/developing-binary-protocol.md | 18 ------------------
.../version-2.3.1/developing-binary-protocol.md | 18 ------------------
.../version-2.3.2/client-libraries-java.md | 21 ---------------------
.../version-2.3.2/developing-binary-protocol.md | 18 ------------------
.../version-2.4.1/developing-binary-protocol.md | 18 ------------------
.../version-2.4.2/developing-binary-protocol.md | 18 ------------------
.../version-2.5.0/developing-binary-protocol.md | 18 ------------------
.../version-2.8.x/developing-binary-protocol.md | 11 +++++++++++
.../version-2.9.x/developing-binary-protocol.md | 11 +++++++++++
21 files changed, 29 insertions(+), 235 deletions(-)
diff --git a/site2/website-next/docs/client-libraries-java.md
b/site2/website-next/docs/client-libraries-java.md
index 670736ad3ad..eab3446a349 100644
--- a/site2/website-next/docs/client-libraries-java.md
+++ b/site2/website-next/docs/client-libraries-java.md
@@ -168,7 +168,7 @@ You can set the client memory allocator configurations
through Java properties.<
|---|---|---|---|---
`pulsar.allocator.pooled` | String | If set to `true`, the client uses a
direct memory pool. <br /> If set to `false`, the client uses a heap memory
without pool | true | <li> true </li> <li> false </li>
`pulsar.allocator.exit_on_oom` | String | Whether to exit the JVM when OOM
happens | false | <li> true </li> <li> false </li>
-`pulsar.allocator.leak_detection` | String | Service URL provider for Pulsar
service | Disabled | <li> Disabled </li> <li> Simple </li> <li> Advanced </li>
<li> Paranoid </li>
+`pulsar.allocator.leak_detection` | String | The leak detection policy for
Pulsar bytebuf allocator. <li> **Disabled**: No leak detection and no overhead.
</li> <li> **Simple**: Instruments 1% of the allocated buffer to track for
leaks. </li> <li> **Advanced**: Instruments 1% of the allocated buffer to track
for leaks, reporting stack traces of places where the buffer is used. </li>
<li> **Paranoid**: Instruments 100% of the allocated buffer to track for leaks,
reporting stack traces of [...]
`pulsar.allocator.out_of_memory_policy` | String | When an OOM occurs, the
client throws an exception or fallbacks to heap | FallbackToHeap | <li>
ThrowException </li> <li> FallbackToHeap </li>
**Example**:
diff --git a/site2/website-next/docs/developing-binary-protocol.md
b/site2/website-next/docs/developing-binary-protocol.md
index 1e4ebe62817..97937119e2b 100644
--- a/site2/website-next/docs/developing-binary-protocol.md
+++ b/site2/website-next/docs/developing-binary-protocol.md
@@ -68,7 +68,7 @@ If you want to use broker entry metadata for **consumers**:
1. Use the client protocol version [18 or
later](https://github.com/apache/pulsar/blob/ca37e67211feda4f7e0984e6414e707f1c1dfd07/pulsar-common/src/main/proto/PulsarApi.proto#L259).
-2. Configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter and set the
[`enableExposingBrokerEntryMetadataToClient`](reference-configuration.md#broker)
parameter to `true` in the `broker.conf` file.
+2. Configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter and set the
[`exposingBrokerEntryMetadataToClientEnabled`](reference-configuration-broker.md#exposingbrokerentrymetadatatoclientenabled)
parameter to `true` in the `broker.conf` file.
## Message metadata
diff --git
a/site2/website-next/versioned_docs/version-2.1.1-incubating/client-libraries-java.md
b/site2/website-next/versioned_docs/version-2.1.1-incubating/client-libraries-java.md
index b201e8573e8..386bc5ef4da 100644
---
a/site2/website-next/versioned_docs/version-2.1.1-incubating/client-libraries-java.md
+++
b/site2/website-next/versioned_docs/version-2.1.1-incubating/client-libraries-java.md
@@ -160,27 +160,6 @@ Check out the Javadoc for the {@inject:
javadoc:PulsarClient:/client/org/apache/
> In addition to client-level configuration, you can also apply
> [producer](#configure-producer) and [consumer](#configure-consumer) specific
> configuration as described in sections below.
-### Client memory allocator configuration
-You can set the client memory allocator configurations through Java
properties.<br />
-
-| Property | Type | <div>Description</div> | Default | Available values
-|---|---|---|---|---
-`pulsar.allocator.pooled` | String | If set to `true`, the client uses a
direct memory pool. <br /> If set to `false`, the client uses a heap memory
without pool | true | <li> true </li> <li> false </li>
-`pulsar.allocator.exit_on_oom` | String | Whether to exit the JVM when OOM
happens | false | <li> true </li> <li> false </li>
-`pulsar.allocator.leak_detection` | String | Service URL provider for Pulsar
service | Disabled | <li> Disabled </li> <li> Simple </li> <li> Advanced </li>
<li> Paranoid </li>
-`pulsar.allocator.out_of_memory_policy` | String | When an OOM occurs, the
client throws an exception or fallbacks to heap | FallbackToHeap | <li>
ThrowException </li> <li> FallbackToHeap </li>
-
-**Example**:
-
-```
-
--Dpulsar.allocator.pooled=true
--Dpulsar.allocator.exit_on_oom=false
--Dpulsar.allocator.leak_detection=Disabled
--Dpulsar.allocator.out_of_memory_policy=ThrowException
-
-```
-
### Cluster-level failover
This chapter describes the concept, benefits, use cases, constraints, usage,
working principles, and more information about the cluster-level failover. It
contains the following sections:
diff --git
a/site2/website-next/versioned_docs/version-2.1.1-incubating/developing-binary-protocol.md
b/site2/website-next/versioned_docs/version-2.1.1-incubating/developing-binary-protocol.md
index 2c228f623dc..f39e44c80de 100644
---
a/site2/website-next/versioned_docs/version-2.1.1-incubating/developing-binary-protocol.md
+++
b/site2/website-next/versioned_docs/version-2.1.1-incubating/developing-binary-protocol.md
@@ -52,24 +52,6 @@ Payload commands have this basic structure:
| `metadata` | Required | The message
[metadata](#message-metadata) stored as a binary protobuf message
| |
| `payload` | Required | Anything left in the frame
is considered the payload and can include any sequence of bytes |
|
-## Broker entry metadata
-
-Broker entry metadata is stored alongside the message metadata as a serialized
protobuf message.
-It is created by the broker when the message arrived at the broker and passed
without changes to the consumer if configured.
-
-| Field | Required or optional | Description
|
-|:-------------------|:----------------|:------------------------------------------------------------------------------------------------------------------------------|
-| `broker_timestamp` | Optional | The timestamp when a message arrived
at the broker (`id est` as the number of milliseconds since January 1st, 1970
in UTC) |
-| `index` | Optional | The index of the message. It is
assigned by the broker.
-
-If you want to use broker entry metadata for **brokers**, configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter in the `broker.conf` file.
-
-If you want to use broker entry metadata for **consumers**:
-
-1. Use the client protocol version [18 or
later](https://github.com/apache/pulsar/blob/ca37e67211feda4f7e0984e6414e707f1c1dfd07/pulsar-common/src/main/proto/PulsarApi.proto#L259).
-
-2. Configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter and set the
[`enableExposingBrokerEntryMetadataToClient`](reference-configuration.md#broker)
parameter to `true` in the `broker.conf` file.
-
## Message metadata
Message metadata is stored alongside the application-specified payload as a
serialized protobuf message. Metadata is created by the producer and passed
without changes to the consumer.
diff --git
a/site2/website-next/versioned_docs/version-2.10.0/client-libraries-java.md
b/site2/website-next/versioned_docs/version-2.10.0/client-libraries-java.md
index 030d9f6f9d5..0b402f1cc45 100644
--- a/site2/website-next/versioned_docs/version-2.10.0/client-libraries-java.md
+++ b/site2/website-next/versioned_docs/version-2.10.0/client-libraries-java.md
@@ -168,7 +168,7 @@ You can set the client memory allocator configurations
through Java properties.<
|---|---|---|---|---
`pulsar.allocator.pooled` | String | If set to `true`, the client uses a
direct memory pool. <br /> If set to `false`, the client uses a heap memory
without pool | true | <li> true </li> <li> false </li>
`pulsar.allocator.exit_on_oom` | String | Whether to exit the JVM when OOM
happens | false | <li> true </li> <li> false </li>
-`pulsar.allocator.leak_detection` | String | Service URL provider for Pulsar
service | Disabled | <li> Disabled </li> <li> Simple </li> <li> Advanced </li>
<li> Paranoid </li>
+`pulsar.allocator.leak_detection` | String | The leak detection policy for
Pulsar bytebuf allocator. <li> **Disabled**: No leak detection and no overhead.
</li> <li> **Simple**: Instruments 1% of the allocated buffer to track for
leaks. </li> <li> **Advanced**: Instruments 1% of the allocated buffer to track
for leaks, reporting stack traces of places where the buffer is used. </li>
<li> **Paranoid**: Instruments 100% of the allocated buffer to track for leaks,
reporting stack traces of [...]
`pulsar.allocator.out_of_memory_policy` | String | When an OOM occurs, the
client throws an exception or fallbacks to heap | FallbackToHeap | <li>
ThrowException </li> <li> FallbackToHeap </li>
**Example**:
diff --git
a/site2/website-next/versioned_docs/version-2.10.0/developing-binary-protocol.md
b/site2/website-next/versioned_docs/version-2.10.0/developing-binary-protocol.md
index 9787f91e362..11394505ac8 100644
---
a/site2/website-next/versioned_docs/version-2.10.0/developing-binary-protocol.md
+++
b/site2/website-next/versioned_docs/version-2.10.0/developing-binary-protocol.md
@@ -69,7 +69,7 @@ If you want to use broker entry metadata for **consumers**:
1. Use the client protocol version [18 or
later](https://github.com/apache/pulsar/blob/ca37e67211feda4f7e0984e6414e707f1c1dfd07/pulsar-common/src/main/proto/PulsarApi.proto#L259).
-2. Configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter and set the
[`enableExposingBrokerEntryMetadataToClient`](reference-configuration.md#broker)
parameter to `true` in the `broker.conf` file.
+2. Configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter and set the
[`exposingBrokerEntryMetadataToClientEnabled`](reference-configuration-broker.md#exposingbrokerentrymetadatatoclientenabled)
parameter to `true` in the `broker.conf` file.
## Message metadata
diff --git
a/site2/website-next/versioned_docs/version-2.10.1/client-libraries-java.md
b/site2/website-next/versioned_docs/version-2.10.1/client-libraries-java.md
index efba798e6b2..b2aa8f815d1 100644
--- a/site2/website-next/versioned_docs/version-2.10.1/client-libraries-java.md
+++ b/site2/website-next/versioned_docs/version-2.10.1/client-libraries-java.md
@@ -168,7 +168,7 @@ You can set the client memory allocator configurations
through Java properties.<
|---|---|---|---|---
`pulsar.allocator.pooled` | String | If set to `true`, the client uses a
direct memory pool. <br /> If set to `false`, the client uses a heap memory
without pool | true | <li> true </li> <li> false </li>
`pulsar.allocator.exit_on_oom` | String | Whether to exit the JVM when OOM
happens | false | <li> true </li> <li> false </li>
-`pulsar.allocator.leak_detection` | String | Service URL provider for Pulsar
service | Disabled | <li> Disabled </li> <li> Simple </li> <li> Advanced </li>
<li> Paranoid </li>
+`pulsar.allocator.leak_detection` | String | The leak detection policy for
Pulsar bytebuf allocator. <li> **Disabled**: No leak detection and no overhead.
</li> <li> **Simple**: Instruments 1% of the allocated buffer to track for
leaks. </li> <li> **Advanced**: Instruments 1% of the allocated buffer to track
for leaks, reporting stack traces of places where the buffer is used. </li>
<li> **Paranoid**: Instruments 100% of the allocated buffer to track for leaks,
reporting stack traces of [...]
`pulsar.allocator.out_of_memory_policy` | String | When an OOM occurs, the
client throws an exception or fallbacks to heap | FallbackToHeap | <li>
ThrowException </li> <li> FallbackToHeap </li>
**Example**:
diff --git
a/site2/website-next/versioned_docs/version-2.10.1/developing-binary-protocol.md
b/site2/website-next/versioned_docs/version-2.10.1/developing-binary-protocol.md
index 9787f91e362..11394505ac8 100644
---
a/site2/website-next/versioned_docs/version-2.10.1/developing-binary-protocol.md
+++
b/site2/website-next/versioned_docs/version-2.10.1/developing-binary-protocol.md
@@ -69,7 +69,7 @@ If you want to use broker entry metadata for **consumers**:
1. Use the client protocol version [18 or
later](https://github.com/apache/pulsar/blob/ca37e67211feda4f7e0984e6414e707f1c1dfd07/pulsar-common/src/main/proto/PulsarApi.proto#L259).
-2. Configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter and set the
[`enableExposingBrokerEntryMetadataToClient`](reference-configuration.md#broker)
parameter to `true` in the `broker.conf` file.
+2. Configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter and set the
[`exposingBrokerEntryMetadataToClientEnabled`](reference-configuration-broker.md#exposingbrokerentrymetadatatoclientenabled)
parameter to `true` in the `broker.conf` file.
## Message metadata
diff --git
a/site2/website-next/versioned_docs/version-2.10.x/developing-binary-protocol.md
b/site2/website-next/versioned_docs/version-2.10.x/developing-binary-protocol.md
index 9787f91e362..11394505ac8 100644
---
a/site2/website-next/versioned_docs/version-2.10.x/developing-binary-protocol.md
+++
b/site2/website-next/versioned_docs/version-2.10.x/developing-binary-protocol.md
@@ -69,7 +69,7 @@ If you want to use broker entry metadata for **consumers**:
1. Use the client protocol version [18 or
later](https://github.com/apache/pulsar/blob/ca37e67211feda4f7e0984e6414e707f1c1dfd07/pulsar-common/src/main/proto/PulsarApi.proto#L259).
-2. Configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter and set the
[`enableExposingBrokerEntryMetadataToClient`](reference-configuration.md#broker)
parameter to `true` in the `broker.conf` file.
+2. Configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter and set the
[`exposingBrokerEntryMetadataToClientEnabled`](reference-configuration-broker.md#exposingbrokerentrymetadatatoclientenabled)
parameter to `true` in the `broker.conf` file.
## Message metadata
diff --git
a/site2/website-next/versioned_docs/version-2.2.0/client-libraries-java.md
b/site2/website-next/versioned_docs/version-2.2.0/client-libraries-java.md
index b201e8573e8..386bc5ef4da 100644
--- a/site2/website-next/versioned_docs/version-2.2.0/client-libraries-java.md
+++ b/site2/website-next/versioned_docs/version-2.2.0/client-libraries-java.md
@@ -160,27 +160,6 @@ Check out the Javadoc for the {@inject:
javadoc:PulsarClient:/client/org/apache/
> In addition to client-level configuration, you can also apply
> [producer](#configure-producer) and [consumer](#configure-consumer) specific
> configuration as described in sections below.
-### Client memory allocator configuration
-You can set the client memory allocator configurations through Java
properties.<br />
-
-| Property | Type | <div>Description</div> | Default | Available values
-|---|---|---|---|---
-`pulsar.allocator.pooled` | String | If set to `true`, the client uses a
direct memory pool. <br /> If set to `false`, the client uses a heap memory
without pool | true | <li> true </li> <li> false </li>
-`pulsar.allocator.exit_on_oom` | String | Whether to exit the JVM when OOM
happens | false | <li> true </li> <li> false </li>
-`pulsar.allocator.leak_detection` | String | Service URL provider for Pulsar
service | Disabled | <li> Disabled </li> <li> Simple </li> <li> Advanced </li>
<li> Paranoid </li>
-`pulsar.allocator.out_of_memory_policy` | String | When an OOM occurs, the
client throws an exception or fallbacks to heap | FallbackToHeap | <li>
ThrowException </li> <li> FallbackToHeap </li>
-
-**Example**:
-
-```
-
--Dpulsar.allocator.pooled=true
--Dpulsar.allocator.exit_on_oom=false
--Dpulsar.allocator.leak_detection=Disabled
--Dpulsar.allocator.out_of_memory_policy=ThrowException
-
-```
-
### Cluster-level failover
This chapter describes the concept, benefits, use cases, constraints, usage,
working principles, and more information about the cluster-level failover. It
contains the following sections:
diff --git
a/site2/website-next/versioned_docs/version-2.2.1/developing-binary-protocol.md
b/site2/website-next/versioned_docs/version-2.2.1/developing-binary-protocol.md
index 2c228f623dc..f39e44c80de 100644
---
a/site2/website-next/versioned_docs/version-2.2.1/developing-binary-protocol.md
+++
b/site2/website-next/versioned_docs/version-2.2.1/developing-binary-protocol.md
@@ -52,24 +52,6 @@ Payload commands have this basic structure:
| `metadata` | Required | The message
[metadata](#message-metadata) stored as a binary protobuf message
| |
| `payload` | Required | Anything left in the frame
is considered the payload and can include any sequence of bytes |
|
-## Broker entry metadata
-
-Broker entry metadata is stored alongside the message metadata as a serialized
protobuf message.
-It is created by the broker when the message arrived at the broker and passed
without changes to the consumer if configured.
-
-| Field | Required or optional | Description
|
-|:-------------------|:----------------|:------------------------------------------------------------------------------------------------------------------------------|
-| `broker_timestamp` | Optional | The timestamp when a message arrived
at the broker (`id est` as the number of milliseconds since January 1st, 1970
in UTC) |
-| `index` | Optional | The index of the message. It is
assigned by the broker.
-
-If you want to use broker entry metadata for **brokers**, configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter in the `broker.conf` file.
-
-If you want to use broker entry metadata for **consumers**:
-
-1. Use the client protocol version [18 or
later](https://github.com/apache/pulsar/blob/ca37e67211feda4f7e0984e6414e707f1c1dfd07/pulsar-common/src/main/proto/PulsarApi.proto#L259).
-
-2. Configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter and set the
[`enableExposingBrokerEntryMetadataToClient`](reference-configuration.md#broker)
parameter to `true` in the `broker.conf` file.
-
## Message metadata
Message metadata is stored alongside the application-specified payload as a
serialized protobuf message. Metadata is created by the producer and passed
without changes to the consumer.
diff --git
a/site2/website-next/versioned_docs/version-2.3.0/client-libraries-java.md
b/site2/website-next/versioned_docs/version-2.3.0/client-libraries-java.md
index b201e8573e8..386bc5ef4da 100644
--- a/site2/website-next/versioned_docs/version-2.3.0/client-libraries-java.md
+++ b/site2/website-next/versioned_docs/version-2.3.0/client-libraries-java.md
@@ -160,27 +160,6 @@ Check out the Javadoc for the {@inject:
javadoc:PulsarClient:/client/org/apache/
> In addition to client-level configuration, you can also apply
> [producer](#configure-producer) and [consumer](#configure-consumer) specific
> configuration as described in sections below.
-### Client memory allocator configuration
-You can set the client memory allocator configurations through Java
properties.<br />
-
-| Property | Type | <div>Description</div> | Default | Available values
-|---|---|---|---|---
-`pulsar.allocator.pooled` | String | If set to `true`, the client uses a
direct memory pool. <br /> If set to `false`, the client uses a heap memory
without pool | true | <li> true </li> <li> false </li>
-`pulsar.allocator.exit_on_oom` | String | Whether to exit the JVM when OOM
happens | false | <li> true </li> <li> false </li>
-`pulsar.allocator.leak_detection` | String | Service URL provider for Pulsar
service | Disabled | <li> Disabled </li> <li> Simple </li> <li> Advanced </li>
<li> Paranoid </li>
-`pulsar.allocator.out_of_memory_policy` | String | When an OOM occurs, the
client throws an exception or fallbacks to heap | FallbackToHeap | <li>
ThrowException </li> <li> FallbackToHeap </li>
-
-**Example**:
-
-```
-
--Dpulsar.allocator.pooled=true
--Dpulsar.allocator.exit_on_oom=false
--Dpulsar.allocator.leak_detection=Disabled
--Dpulsar.allocator.out_of_memory_policy=ThrowException
-
-```
-
### Cluster-level failover
This chapter describes the concept, benefits, use cases, constraints, usage,
working principles, and more information about the cluster-level failover. It
contains the following sections:
diff --git
a/site2/website-next/versioned_docs/version-2.3.0/developing-binary-protocol.md
b/site2/website-next/versioned_docs/version-2.3.0/developing-binary-protocol.md
index 2c228f623dc..f39e44c80de 100644
---
a/site2/website-next/versioned_docs/version-2.3.0/developing-binary-protocol.md
+++
b/site2/website-next/versioned_docs/version-2.3.0/developing-binary-protocol.md
@@ -52,24 +52,6 @@ Payload commands have this basic structure:
| `metadata` | Required | The message
[metadata](#message-metadata) stored as a binary protobuf message
| |
| `payload` | Required | Anything left in the frame
is considered the payload and can include any sequence of bytes |
|
-## Broker entry metadata
-
-Broker entry metadata is stored alongside the message metadata as a serialized
protobuf message.
-It is created by the broker when the message arrived at the broker and passed
without changes to the consumer if configured.
-
-| Field | Required or optional | Description
|
-|:-------------------|:----------------|:------------------------------------------------------------------------------------------------------------------------------|
-| `broker_timestamp` | Optional | The timestamp when a message arrived
at the broker (`id est` as the number of milliseconds since January 1st, 1970
in UTC) |
-| `index` | Optional | The index of the message. It is
assigned by the broker.
-
-If you want to use broker entry metadata for **brokers**, configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter in the `broker.conf` file.
-
-If you want to use broker entry metadata for **consumers**:
-
-1. Use the client protocol version [18 or
later](https://github.com/apache/pulsar/blob/ca37e67211feda4f7e0984e6414e707f1c1dfd07/pulsar-common/src/main/proto/PulsarApi.proto#L259).
-
-2. Configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter and set the
[`enableExposingBrokerEntryMetadataToClient`](reference-configuration.md#broker)
parameter to `true` in the `broker.conf` file.
-
## Message metadata
Message metadata is stored alongside the application-specified payload as a
serialized protobuf message. Metadata is created by the producer and passed
without changes to the consumer.
diff --git
a/site2/website-next/versioned_docs/version-2.3.1/developing-binary-protocol.md
b/site2/website-next/versioned_docs/version-2.3.1/developing-binary-protocol.md
index 2c228f623dc..f39e44c80de 100644
---
a/site2/website-next/versioned_docs/version-2.3.1/developing-binary-protocol.md
+++
b/site2/website-next/versioned_docs/version-2.3.1/developing-binary-protocol.md
@@ -52,24 +52,6 @@ Payload commands have this basic structure:
| `metadata` | Required | The message
[metadata](#message-metadata) stored as a binary protobuf message
| |
| `payload` | Required | Anything left in the frame
is considered the payload and can include any sequence of bytes |
|
-## Broker entry metadata
-
-Broker entry metadata is stored alongside the message metadata as a serialized
protobuf message.
-It is created by the broker when the message arrived at the broker and passed
without changes to the consumer if configured.
-
-| Field | Required or optional | Description
|
-|:-------------------|:----------------|:------------------------------------------------------------------------------------------------------------------------------|
-| `broker_timestamp` | Optional | The timestamp when a message arrived
at the broker (`id est` as the number of milliseconds since January 1st, 1970
in UTC) |
-| `index` | Optional | The index of the message. It is
assigned by the broker.
-
-If you want to use broker entry metadata for **brokers**, configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter in the `broker.conf` file.
-
-If you want to use broker entry metadata for **consumers**:
-
-1. Use the client protocol version [18 or
later](https://github.com/apache/pulsar/blob/ca37e67211feda4f7e0984e6414e707f1c1dfd07/pulsar-common/src/main/proto/PulsarApi.proto#L259).
-
-2. Configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter and set the
[`enableExposingBrokerEntryMetadataToClient`](reference-configuration.md#broker)
parameter to `true` in the `broker.conf` file.
-
## Message metadata
Message metadata is stored alongside the application-specified payload as a
serialized protobuf message. Metadata is created by the producer and passed
without changes to the consumer.
diff --git
a/site2/website-next/versioned_docs/version-2.3.2/client-libraries-java.md
b/site2/website-next/versioned_docs/version-2.3.2/client-libraries-java.md
index b201e8573e8..386bc5ef4da 100644
--- a/site2/website-next/versioned_docs/version-2.3.2/client-libraries-java.md
+++ b/site2/website-next/versioned_docs/version-2.3.2/client-libraries-java.md
@@ -160,27 +160,6 @@ Check out the Javadoc for the {@inject:
javadoc:PulsarClient:/client/org/apache/
> In addition to client-level configuration, you can also apply
> [producer](#configure-producer) and [consumer](#configure-consumer) specific
> configuration as described in sections below.
-### Client memory allocator configuration
-You can set the client memory allocator configurations through Java
properties.<br />
-
-| Property | Type | <div>Description</div> | Default | Available values
-|---|---|---|---|---
-`pulsar.allocator.pooled` | String | If set to `true`, the client uses a
direct memory pool. <br /> If set to `false`, the client uses a heap memory
without pool | true | <li> true </li> <li> false </li>
-`pulsar.allocator.exit_on_oom` | String | Whether to exit the JVM when OOM
happens | false | <li> true </li> <li> false </li>
-`pulsar.allocator.leak_detection` | String | Service URL provider for Pulsar
service | Disabled | <li> Disabled </li> <li> Simple </li> <li> Advanced </li>
<li> Paranoid </li>
-`pulsar.allocator.out_of_memory_policy` | String | When an OOM occurs, the
client throws an exception or fallbacks to heap | FallbackToHeap | <li>
ThrowException </li> <li> FallbackToHeap </li>
-
-**Example**:
-
-```
-
--Dpulsar.allocator.pooled=true
--Dpulsar.allocator.exit_on_oom=false
--Dpulsar.allocator.leak_detection=Disabled
--Dpulsar.allocator.out_of_memory_policy=ThrowException
-
-```
-
### Cluster-level failover
This chapter describes the concept, benefits, use cases, constraints, usage,
working principles, and more information about the cluster-level failover. It
contains the following sections:
diff --git
a/site2/website-next/versioned_docs/version-2.3.2/developing-binary-protocol.md
b/site2/website-next/versioned_docs/version-2.3.2/developing-binary-protocol.md
index 2c228f623dc..f39e44c80de 100644
---
a/site2/website-next/versioned_docs/version-2.3.2/developing-binary-protocol.md
+++
b/site2/website-next/versioned_docs/version-2.3.2/developing-binary-protocol.md
@@ -52,24 +52,6 @@ Payload commands have this basic structure:
| `metadata` | Required | The message
[metadata](#message-metadata) stored as a binary protobuf message
| |
| `payload` | Required | Anything left in the frame
is considered the payload and can include any sequence of bytes |
|
-## Broker entry metadata
-
-Broker entry metadata is stored alongside the message metadata as a serialized
protobuf message.
-It is created by the broker when the message arrived at the broker and passed
without changes to the consumer if configured.
-
-| Field | Required or optional | Description
|
-|:-------------------|:----------------|:------------------------------------------------------------------------------------------------------------------------------|
-| `broker_timestamp` | Optional | The timestamp when a message arrived
at the broker (`id est` as the number of milliseconds since January 1st, 1970
in UTC) |
-| `index` | Optional | The index of the message. It is
assigned by the broker.
-
-If you want to use broker entry metadata for **brokers**, configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter in the `broker.conf` file.
-
-If you want to use broker entry metadata for **consumers**:
-
-1. Use the client protocol version [18 or
later](https://github.com/apache/pulsar/blob/ca37e67211feda4f7e0984e6414e707f1c1dfd07/pulsar-common/src/main/proto/PulsarApi.proto#L259).
-
-2. Configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter and set the
[`enableExposingBrokerEntryMetadataToClient`](reference-configuration.md#broker)
parameter to `true` in the `broker.conf` file.
-
## Message metadata
Message metadata is stored alongside the application-specified payload as a
serialized protobuf message. Metadata is created by the producer and passed
without changes to the consumer.
diff --git
a/site2/website-next/versioned_docs/version-2.4.1/developing-binary-protocol.md
b/site2/website-next/versioned_docs/version-2.4.1/developing-binary-protocol.md
index 2c228f623dc..f39e44c80de 100644
---
a/site2/website-next/versioned_docs/version-2.4.1/developing-binary-protocol.md
+++
b/site2/website-next/versioned_docs/version-2.4.1/developing-binary-protocol.md
@@ -52,24 +52,6 @@ Payload commands have this basic structure:
| `metadata` | Required | The message
[metadata](#message-metadata) stored as a binary protobuf message
| |
| `payload` | Required | Anything left in the frame
is considered the payload and can include any sequence of bytes |
|
-## Broker entry metadata
-
-Broker entry metadata is stored alongside the message metadata as a serialized
protobuf message.
-It is created by the broker when the message arrived at the broker and passed
without changes to the consumer if configured.
-
-| Field | Required or optional | Description
|
-|:-------------------|:----------------|:------------------------------------------------------------------------------------------------------------------------------|
-| `broker_timestamp` | Optional | The timestamp when a message arrived
at the broker (`id est` as the number of milliseconds since January 1st, 1970
in UTC) |
-| `index` | Optional | The index of the message. It is
assigned by the broker.
-
-If you want to use broker entry metadata for **brokers**, configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter in the `broker.conf` file.
-
-If you want to use broker entry metadata for **consumers**:
-
-1. Use the client protocol version [18 or
later](https://github.com/apache/pulsar/blob/ca37e67211feda4f7e0984e6414e707f1c1dfd07/pulsar-common/src/main/proto/PulsarApi.proto#L259).
-
-2. Configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter and set the
[`enableExposingBrokerEntryMetadataToClient`](reference-configuration.md#broker)
parameter to `true` in the `broker.conf` file.
-
## Message metadata
Message metadata is stored alongside the application-specified payload as a
serialized protobuf message. Metadata is created by the producer and passed
without changes to the consumer.
diff --git
a/site2/website-next/versioned_docs/version-2.4.2/developing-binary-protocol.md
b/site2/website-next/versioned_docs/version-2.4.2/developing-binary-protocol.md
index 2c228f623dc..f39e44c80de 100644
---
a/site2/website-next/versioned_docs/version-2.4.2/developing-binary-protocol.md
+++
b/site2/website-next/versioned_docs/version-2.4.2/developing-binary-protocol.md
@@ -52,24 +52,6 @@ Payload commands have this basic structure:
| `metadata` | Required | The message
[metadata](#message-metadata) stored as a binary protobuf message
| |
| `payload` | Required | Anything left in the frame
is considered the payload and can include any sequence of bytes |
|
-## Broker entry metadata
-
-Broker entry metadata is stored alongside the message metadata as a serialized
protobuf message.
-It is created by the broker when the message arrived at the broker and passed
without changes to the consumer if configured.
-
-| Field | Required or optional | Description
|
-|:-------------------|:----------------|:------------------------------------------------------------------------------------------------------------------------------|
-| `broker_timestamp` | Optional | The timestamp when a message arrived
at the broker (`id est` as the number of milliseconds since January 1st, 1970
in UTC) |
-| `index` | Optional | The index of the message. It is
assigned by the broker.
-
-If you want to use broker entry metadata for **brokers**, configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter in the `broker.conf` file.
-
-If you want to use broker entry metadata for **consumers**:
-
-1. Use the client protocol version [18 or
later](https://github.com/apache/pulsar/blob/ca37e67211feda4f7e0984e6414e707f1c1dfd07/pulsar-common/src/main/proto/PulsarApi.proto#L259).
-
-2. Configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter and set the
[`enableExposingBrokerEntryMetadataToClient`](reference-configuration.md#broker)
parameter to `true` in the `broker.conf` file.
-
## Message metadata
Message metadata is stored alongside the application-specified payload as a
serialized protobuf message. Metadata is created by the producer and passed
without changes to the consumer.
diff --git
a/site2/website-next/versioned_docs/version-2.5.0/developing-binary-protocol.md
b/site2/website-next/versioned_docs/version-2.5.0/developing-binary-protocol.md
index 2c228f623dc..f39e44c80de 100644
---
a/site2/website-next/versioned_docs/version-2.5.0/developing-binary-protocol.md
+++
b/site2/website-next/versioned_docs/version-2.5.0/developing-binary-protocol.md
@@ -52,24 +52,6 @@ Payload commands have this basic structure:
| `metadata` | Required | The message
[metadata](#message-metadata) stored as a binary protobuf message
| |
| `payload` | Required | Anything left in the frame
is considered the payload and can include any sequence of bytes |
|
-## Broker entry metadata
-
-Broker entry metadata is stored alongside the message metadata as a serialized
protobuf message.
-It is created by the broker when the message arrived at the broker and passed
without changes to the consumer if configured.
-
-| Field | Required or optional | Description
|
-|:-------------------|:----------------|:------------------------------------------------------------------------------------------------------------------------------|
-| `broker_timestamp` | Optional | The timestamp when a message arrived
at the broker (`id est` as the number of milliseconds since January 1st, 1970
in UTC) |
-| `index` | Optional | The index of the message. It is
assigned by the broker.
-
-If you want to use broker entry metadata for **brokers**, configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter in the `broker.conf` file.
-
-If you want to use broker entry metadata for **consumers**:
-
-1. Use the client protocol version [18 or
later](https://github.com/apache/pulsar/blob/ca37e67211feda4f7e0984e6414e707f1c1dfd07/pulsar-common/src/main/proto/PulsarApi.proto#L259).
-
-2. Configure the
[`brokerEntryMetadataInterceptors`](reference-configuration.md#broker)
parameter and set the
[`enableExposingBrokerEntryMetadataToClient`](reference-configuration.md#broker)
parameter to `true` in the `broker.conf` file.
-
## Message metadata
Message metadata is stored alongside the application-specified payload as a
serialized protobuf message. Metadata is created by the producer and passed
without changes to the consumer.
diff --git
a/site2/website-next/versioned_docs/version-2.8.x/developing-binary-protocol.md
b/site2/website-next/versioned_docs/version-2.8.x/developing-binary-protocol.md
index 9084b006b9b..7a2a034b044 100644
---
a/site2/website-next/versioned_docs/version-2.8.x/developing-binary-protocol.md
+++
b/site2/website-next/versioned_docs/version-2.8.x/developing-binary-protocol.md
@@ -50,6 +50,17 @@ Payload commands have this basic structure:
| metadata | The message [metadata](#message-metadata) stored as a binary
protobuf message | |
| payload | Anything left in the frame is considered the payload and can
include any sequence of bytes | |
+## Broker entry metadata
+
+Broker entry metadata is stored alongside the message metadata as a serialized
protobuf message.
+
+It is created by the broker when the message arrived at the broker and passed
without changes to the consumer if configured.
+
+| Field | Required or optional | Description
|
+|:-------------------|:----------------|:------------------------------------------------------------------------------------------------------------------------------|
+| `broker_timestamp` | Optional | The timestamp when a message arrived
at the broker (`id est` as the number of milliseconds since January 1st, 1970
in UTC) |
+| `index` | Optional | The index of the message. It is
assigned by the broker.
+
## Message metadata
Message metadata is stored alongside the application-specified payload as a
serialized protobuf message. Metadata is created by the producer and passed on
unchanged to the consumer.
diff --git
a/site2/website-next/versioned_docs/version-2.9.x/developing-binary-protocol.md
b/site2/website-next/versioned_docs/version-2.9.x/developing-binary-protocol.md
index a18a8b8d561..6a782a42552 100644
---
a/site2/website-next/versioned_docs/version-2.9.x/developing-binary-protocol.md
+++
b/site2/website-next/versioned_docs/version-2.9.x/developing-binary-protocol.md
@@ -50,6 +50,17 @@ Payload commands have this basic structure:
| metadata | The message [metadata](#message-metadata) stored as a binary
protobuf message | |
| payload | Anything left in the frame is considered the payload and can
include any sequence of bytes | |
+## Broker entry metadata
+
+Broker entry metadata is stored alongside the message metadata as a serialized
protobuf message.
+
+It is created by the broker when the message arrived at the broker and passed
without changes to the consumer if configured.
+
+| Field | Required or optional | Description
|
+|:-------------------|:----------------|:------------------------------------------------------------------------------------------------------------------------------|
+| `broker_timestamp` | Optional | The timestamp when a message arrived
at the broker (`id est` as the number of milliseconds since January 1st, 1970
in UTC) |
+| `index` | Optional | The index of the message. It is
assigned by the broker.
+
## Message metadata
Message metadata is stored alongside the application-specified payload as a
serialized protobuf message. Metadata is created by the producer and passed on
unchanged to the consumer.
