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 5MB by default, then 100 buffers will use N*500 MB. It could reach 1GB if N > 2. In addition, normally, only if at least 100 producers sent messages to a partition would it be meaningful to configure maxPendingChunkedMessages to 100. IMO, it's hard to see so many producers on a partition in production. Thanks, Yunze Xu > 2022年1月30日 下午6:32，Zike Yang <zky...@streamnative.io.INVALID> 写道： > > 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 inconsistency. But what should we take as the > default value? From the code or the doc? I would like to hear your > discussions. > > [1] > https://github.com/apache/pulsar/blob/d11147616aa6cc7888420f6325bb71cd7f7ab065/pulsar-client/src/main/java/org/apache/pulsar/client/impl/conf/ConsumerConfigurationData.java#L112-L113 > [2] > https://github.com/apache/pulsar/blob/1e2ff8a3941b7cc6d583f528ceedc393b7e607fb/pulsar-client-api/src/main/java/org/apache/pulsar/client/api/ConsumerBuilder.java#L690 > > Thanks, > Zike Yang
