rvashishth opened a new issue #9988:
URL: https://github.com/apache/pulsar/issues/9988
**Describe the bug**
Bookkeeper pod failed to start with below Error. Even though the allocated
memory to pods & `MaxDirectMemorySize` size is much more the what is mentioned
in error log.
```
08:13:25.210 [SyncThread-8-1] INFO
org.apache.bookkeeper.bookie.EntryLogManagerBase - Creating a new entry log
file because current active log channel has not initialized yet
08:13:25.212 [SyncThread-8-1] ERROR org.apache.bookkeeper.proto.BookieServer
- Unable to allocate memory, exiting bookie
io.netty.util.internal.OutOfDirectMemoryError: failed to allocate 16777216
byte(s) of direct memory (used: 117440543, max: 129761280)
at
io.netty.util.internal.PlatformDependent.incrementMemoryCounter(PlatformDependent.java:754)
~[io.netty-netty-common-4.1.51.Final.jar:4.1.51.Final]
```
**To Reproduce**
Steps to reproduce the behavior:
1. Install pulsar-helm-chart version 2.7.0 using the pulsar image 2.7.1
2. Bookie pods won't start and status will change to `CrashLoopBackOff`
**Expected behavior**
Pulsar helm chart should be able install the release with default values
file.
**Screenshots**
NA
**Desktop (please complete the following information):**
NA
**Additional context**
A pod starts and immediately after throw above mentioned error.
I am creating 4 bookie pod in my setup.
Bookie Container Resource Limits are below
```
resources:
limits:
cpu: 400m
memory: 512Mi
requests:
cpu: 200m
memory: 512Mi
```
[PULSAR_MEM values are default to chart values file. -Xms128m -Xmx256m
-XX:MaxDirectMemorySize=256m](https://github.com/apache/pulsar-helm-chart/blob/ba356e5df7b4509171ca1995178f1ba4369eb642/charts/pulsar/values.yaml#L479)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
