tsteinholz opened a new issue, #389:
URL: https://github.com/apache/pulsar-helm-chart/issues/389
**Describe the bug**
Increasing pods requests / limits and even manually specifying the JVM
memoryOptions has no affect on the pod JVM allocation.
**To Reproduce**
Attempt to configure Pulsar broker JVM configurations with just broker
requests
```
broker:
resources:
requests:
memory: "8Gi"
cpu: "0.2"
limits: {}
# memory: "2Gi"
# cpu: "0.8"
```
Or try to manually specify the JVM size
```
jvm:
# Pulsar Operator will automatically generate the JVM memory options
based on the Pod memory size. You can override this by entering a new value.
(False or misleading statement)
memoryOptions:
- >
-Xms2g
-Xmx2g
-XX:MaxDirectMemorySize=4g
```
**Expected behavior**
The pods should be allocated with requested JVM memory options that are
specified in the release
```
jvm:
memoryOptions:
- "-Xms2g -Xmx2g -XX:MaxDirectMemorySize=4g \n"
```
Actual Behavior:
```
PULSAR_MEM : -Xms153m -Xmx153m -XX:MaxDirectMemorySize=307m
```
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
- OS: [e.g. iOS]
**Additional context**
Add any other context about the problem here.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
