Souce connector can not be created successfully on pulsar cluster that installed by the offical helm chart
See original GitHub issueDescribe the bug I install pulsar on kubernetes using official helm chart . All my connector can not created successfully, even the builtin( for example debezium-mysql ). I found the OutOfDirectMemoryError of direct memory in the log of broker. But the exception still exists after increate direct memory from 256MB to 2GB.
But the connector runs in local mode normally.
To Reproduce
- helm upgrade --install pulsar apache/pulsar --timeout 10m --set initialize=true 2
bin/pulsar-admin source create --tenant iot --namespace pipe \
--name xxxxx --destination-topic-name xxx/xxx/xxx --parallelism 1 --archive builtin://debezium-mysql \
--source-config '{ "database.hostname": "mysql", "database.port": "3306", "database.user": "xxxx", "database.password": "xxxxx","database.server.id": "1","database.server.name": "xxxxx","database.whitelist": "xxxx", "table.whitelist": "xxxxxx","schemas.enable":false,"pulsar.service.url": "pulsar://pulsar-proxy:6650" }'
- the broker log
06:24:14.597 [DL-io-0] ERROR org.apache.bookkeeper.common.allocator.impl.ByteBufAllocatorImpl - Unable to allocate memory
io.netty.util.internal.OutOfDirectMemoryError: failed to allocate 16777216 byte(s) of direct memory (used: 251658247, max: 268435456)
at io.netty.util.internal.PlatformDependent.incrementMemoryCounter(PlatformDependent.java:742) ~[io.netty-netty-common-4.1.48.Final.jar:4.1.48.Final]
at io.netty.util.internal.PlatformDependent.allocateDirectNoCleaner(PlatformDependent.java:697) ~[io.netty-netty-common-4.1.48.Final.jar:4.1.48.Final]
at io.netty.buffer.PoolArena$DirectArena.allocateDirect(PoolArena.java:758) ~[io.netty-netty-buffer-4.1.48.Final.jar:4.1.48.Final]
at io.netty.buffer.PoolArena$DirectArena.newChunk(PoolArena.java:734) ~[io.netty-netty-buffer-4.1.48.Final.jar:4.1.48.Final]
at io.netty.buffer.PoolArena.allocateNormal(PoolArena.java:245) ~[io.netty-netty-buffer-4.1.48.Final.jar:4.1.48.Final]
at io.netty.buffer.PoolArena.allocate(PoolArena.java:227) ~[io.netty-netty-buffer-4.1.48.Final.jar:4.1.48.Final]
at io.netty.buffer.PoolArena.allocate(PoolArena.java:147) ~[io.netty-netty-buffer-4.1.48.Final.jar:4.1.48.Final]
Expected behavior The source connector created successfully.
Additional context helm chart version: 2.7.0 and 2.6.3-2 kubernetes:v1.18.10
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Deploy Pulsar cluster using Helm
To use the Pulsar Helm chart to create the Kubernetes namespace automatically, you can include this option in the helm install command.
Read more >Get Started | StreamNative Documentation
This document guides you through every step of installing and running StreamNative Platform with operators on Kubernetes quickly. It includes the following ...
Read more >Comparing Apache Kafka and Apache Pulsar
There is no official binary Helm package, so one has to clone the whole Pulsar repository to install it — the Helm chart...
Read more >Mastering Apache Pulsar
Jowanza Joseph, staff software engineer at Finicity, explains how to deploy production Pulsar clusters, write reliable event streaming ...
Read more >Luna Streaming FAQs - DataStax Documentation
How do I install DataStax Luna Streaming in my Kubernetes cluster? ... DataStax Luna Streaming provide that I cannot get with open-source Apache...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is my chart values
This should be open we have the same issue in 2.8.2