Slack digest for #dev - 2019-08-20

[Apache Pulsar Slack <ap...@gmail.com>]

2019-08-19 16:17:30 UTC - pradeep: While createing Producer using loadConfig() mehtod , loadData() method of ConfigurationDataUtils throws exception  No serializer found for class org.apache.pulsar.client.impl.DefaultBatcherBuilder and no properties discovered to create BeanSerializer (to avoid exception, disable SerializationFeature.FAIL_ON_EMPTY_BEANS) (through reference chain: org.apache.pulsar.client.impl.conf.ProducerConfigurationData["batcherBuilder"])

line - 42 (String existingConfigJson = mapper.writeValueAsString(existingData);)
----
2019-08-19 23:10:07 UTC - David Lucas: @David Lucas has joined the channel
----
2019-08-20 02:33:37 UTC - da peng: @da peng has joined the channel
----
2019-08-20 08:27:39 UTC - Jianfeng Qiao: I disabled backlog quota check via setting backlogQuotaCheckEnabled=false in broker.conf, why I still run into the exception says "Cannot create producer on topic with backlog quota exceeded org.apache.pulsar.client.api.PulsarClientException$ProducerBlockedQuotaExceededError: Cannot create producer on topic with backlog quota exceeded"? Anyone know about this?
----
2019-08-20 08:30:21 UTC - Penghui Li: @Jianfeng Qiao I think you need to set the limit of backlog quota to -1
----
2019-08-20 08:45:35 UTC - Jianfeng Qiao: What is backlogQuotaCheckEnabled for?
----
2019-08-20 08:56:32 UTC - Penghui Li: backlogQuotaCheckEnabled is for checker of backlog quota, if you set backlogQuotaCheckEnabled=false,  checker of the backlog quota will not be activated.

if enable the checker, checker will drop backlog while use consumer_backlog_eviction policy, and will disconnect producer while use producer_request_hold.
----
2019-08-20 08:58:27 UTC - Penghui Li: So if just set backlogQuotaCheckEnabled=false and then create a producer on a backlog exceeded topic, broker will still reject the producer.
----