You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "tsteinholz (via GitHub)" <gi...@apache.org> on 2023/08/29 16:47:07 UTC

[GitHub] [pulsar-helm-chart] tsteinholz opened a new issue, #389: Pulsar Broker JVM Arguments are Ignored

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: commits-unsubscribe@pulsar.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Pulsar Broker JVM Arguments are Ignored [pulsar-helm-chart]

Posted by "lhotari (via GitHub)" <gi...@apache.org>.
lhotari closed issue #389: Pulsar Broker JVM Arguments are Ignored
URL: https://github.com/apache/pulsar-helm-chart/issues/389


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Pulsar Broker JVM Arguments are Ignored [pulsar-helm-chart]

Posted by "lhotari (via GitHub)" <gi...@apache.org>.
lhotari commented on issue #389:
URL: https://github.com/apache/pulsar-helm-chart/issues/389#issuecomment-1912715786

   > "Pulsar Operator will automatically generate the JVM memory options based on the Pod memory size. You can override this by entering a new value."
   
   The repository isn't for the Pulsar Operator. I don't see how this issue applies to Apache Pulsar Helm chart.


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [pulsar-helm-chart] tsteinholz commented on issue #389: Pulsar Broker JVM Arguments are Ignored

Posted by "tsteinholz (via GitHub)" <gi...@apache.org>.
tsteinholz commented on issue #389:
URL: https://github.com/apache/pulsar-helm-chart/issues/389#issuecomment-1697822482

   Using the `@deprecated` config map field in the values.yaml also fails
   
   ```
       broker:
         configData:
           PULSAR_MEM: >
             -Xms2g -Xmx2g -XX:MaxDirectMemorySize=4g
   ```
   https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/values.yaml#L758C14-L758C14


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [pulsar-helm-chart] tsteinholz commented on issue #389: Pulsar Broker JVM Arguments are Ignored

Posted by "tsteinholz (via GitHub)" <gi...@apache.org>.
tsteinholz commented on issue #389:
URL: https://github.com/apache/pulsar-helm-chart/issues/389#issuecomment-1697840317

   Update: it seems like writing the PULSAR_MEM directly to the configmap works, the `jvm` section appears to be obsolete. If that is true, then the jvm section should be deprecated / removed to avoid confusion. Especially with the false statement "Pulsar Operator will automatically generate the JVM memory options based on the Pod memory size. You can override this by entering a new value."


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org