Hi, Pulsar community,
We found that there are inconsistencies between the code and the
documentation regarding the default value of maxPendingChunkedMessage.
In the java client code, we use 10 as the default value. [1] But in
the java doc, we use 100 as the default value. [2]
We need to fix this
After thinking for a while, I’d prefer 10 as the default value and I changed
the default value to 10 in C++ client, see
https://github.com/apache/pulsar/pull/14070.
A chunked buffer to contain all chunks could use much memory, for example, if a
message was split into N chunks, since each chunk is
Hi, Yunze,
Thanks for your opinion.
> A chunked buffer to contain all chunks could use much memory, for example, if
> a
> message was split into N chunks, since each chunk is 5MB by default, then 100
> buffers will use N*500 MB. It could reach 1GB if N > 2.
>
> In addition, normally, only if at
Hi,
I would like to start a discussion about PIP-136: Sync Pulsar policies
across multiple clouds.
PIP documentation: https://github.com/apache/pulsar/issues/13728
*Motivation*
Apache Pulsar is a cloud-native, distributed messaging framework which
natively provides geo-replication. Many organiza
lhotari opened a new pull request #220:
URL: https://github.com/apache/pulsar-helm-chart/pull/220
### Motivation
- 5 seconds seems to be a too short probe timeout on a system with low
resources such as in CI
### Modifications
- change default timeout to 30 seconds (whic
