Closed sijie closed 3 years ago
Original Issue: apache/bookkeeper#2545
BUG REPORT Bookkeeper version 4.12.0 OutOfDirectMemory during GarbageCollector. It can't self-healing. Consequencely, disk being writing full.
Screenshots
Additional context JVM params
-Djava.net.preferIPv4Stack=true -Xms1G -Xmx1G -XX:MetaspaceSize=128M -XX:MaxMetaspaceSize=512M -XX:MaxDirectMemorySize=1G -XX:ParallelGCThreads=2 -XX:ConcGCThreads=2 -XX:G1HeapRegionSize=2m -XX:InitiatingHeapOccupancyPercent=45 -XX:G1MixedGCCountTarget=2 -XX:+ParallelRefProcEnabled -XX:+UnlockExperimentalVMOptions -XX:G1OldCSetRegionThresholdPercent=5 -XX:+UseG1GC -XX:MaxGCPauseMillis=10 -XX:+AggressiveOpts -XX:+DoEscapeAnalysis -XX:+DisableExplicitGC -XX:-ResizePLAB -XX:+PrintGCDetails -XX:+PrintGCApplicationStoppedTime -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:+PrintGCDateStamps -XX:GCLogFileSize=64m -Xloggc:/home/edge/middleware/bookkeeper/logs/bookkeeper-gc_%p.log -Dio.netty.leakDetectionLevel=disabled -Dio.netty.recycler.maxCapacity.default=1000 -Dio.netty.recycler.linkCapacity=1024 -Dlog4j.configuration=log4j.properties -Dbookkeeper.root.logger=INFO,ROLLINGFILE
bk_conf and log conf_and_log.zip
Original Issue: apache/bookkeeper#2545
BUG REPORT Bookkeeper version 4.12.0 OutOfDirectMemory during GarbageCollector. It can't self-healing. Consequencely, disk being writing full.
Screenshots
Additional context JVM params
bk_conf and log conf_and_log.zip