I have a simpler question. Just storing the message-ids raw will fit ~300K
entries in one ledger entry. With the bitmap changes, we can store a
couple of million within one 5MB ledger entry. So can you tell us what
numbers of unacked messages are creating a problem? What exactly are the
issues
yufan022 opened a new pull request #95:
URL: https://github.com/apache/pulsar-helm-chart/pull/95
Fixes #94
### Motivation
fix `io.kubernetes.client.openapi.ApiException: Forbidden`
### Modifications
fix typo
### Verifying this change
- [ ] Make sure
yufan022 opened a new issue #94:
URL: https://github.com/apache/pulsar-helm-chart/issues/94
**Describe the bug**
Get some error log on k8s.
```
10:33:59.441 [Timer-0] ERROR
org.apache.pulsar.functions.runtime.kubernetes.KubernetesRuntimeFactory - Error
while trying to fetch config
+1 binding
OS: MacOS 10.15.6
- verified packages checksum and signatures ( asc and sha all good)
- the source package rat check(mvn apache-rat:check), licence check, build
and unit test all run successfully.
- bin package build from source, 'bin/pulsar standalone' and client
produce/consume run
massakam commented on a change in pull request #138:
URL: https://github.com/apache/pulsar-client-node/pull/138#discussion_r559980339
##
File path: tests/end_to_end.test.js
##
@@ -665,5 +669,87 @@ const Pulsar = require('../index.js');
await consumer.close();
awai
massakam commented on a change in pull request #138:
URL: https://github.com/apache/pulsar-client-node/pull/138#discussion_r559977594
##
File path: tests/end_to_end.test.js
##
@@ -665,5 +669,87 @@ const Pulsar = require('../index.js');
await consumer.close();
awai
