andrekramer1 opened a new issue #134:
URL: https://github.com/apache/pulsar-helm-chart/issues/134
**Describe the bug**
When using Pulsar 2.8.0 (recently released) with the helm chart which is
currently at 2.7.2 bookie pods fail to initialize as the init commands java
command (to run bookkeeper shell) fails because of invalid command line
arguments for the GC configuration.
**To Reproduce**
Change image to 2.8.0 (we were using a private build but problem would still
apply to public image) and create or update a cluster. Bookies fail to init.
**Expected behavior**
Bookies to init after the java bookkeeper shell get instance id
initialization.
**Additional context**
A simple fix is to modify the PULSAR_GC environment variable by changing the
charts/pulsar/values.yaml file to be:
PULSAR_GC: >
-XX:+UseG1GC
-XX:MaxGCPauseMillis=10
-XX:+ParallelRefProcEnabled
-XX:+UnlockExperimentalVMOptions
-XX:+DoEscapeAnalysis
-XX:ParallelGCThreads=4
-XX:ConcGCThreads=4
-XX:G1NewSizePercent=50
-XX:+DisableExplicitGC
-XX:-ResizePLAB
-XX:+ExitOnOutOfMemoryError
-XX:+PerfDisableSharedMem
-XX:+PrintGCDetails
-verbosegc
-Xloggc:/var/log/bookie-gc.log
(Removing 4 -XX/-X args)
Current values.yaml:
PULSAR_GC: >
-XX:+UseG1GC
-XX:MaxGCPauseMillis=10
-XX:+ParallelRefProcEnabled
-XX:+UnlockExperimentalVMOptions
-XX:+DoEscapeAnalysis
-XX:ParallelGCThreads=4
-XX:ConcGCThreads=4
-XX:G1NewSizePercent=50
-XX:+DisableExplicitGC
-XX:-ResizePLAB
-XX:+ExitOnOutOfMemoryError
-XX:+PerfDisableSharedMem
-XX:+PrintGCDetails
-XX:+PrintGCTimeStamps
-XX:+PrintGCApplicationStoppedTime
-XX:+PrintHeapAtGC
-verbosegc
-Xloggc:/var/log/bookie-gc.log
-XX:G1LogLevel=finest
--
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]
