yws-tracy commented on issue #2269:
URL: https://github.com/apache/bookkeeper/issues/2269#issuecomment-1207418852

   > 
   @sunshujie1990  we met the same problem, was your problems finally solved? 
we use DbLedgerStorage
   <img width="1267" alt="image" 
src="https://user-images.githubusercontent.com/34879511/183294702-152a341a-9bf2-40f3-a538-8142d49e0181.png";>
   
   bookkeeper version:  4.10.0
   bookie conf:
   ```
   apiVersion: v1
   data:
     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:+HeapDumpOnOutOfMemoryError 
-XX:HeapDumpPath=/pulsar/pulsar.hprof -XX:+PrintGCDetails 
-XX:+PrintGCTimeStamps -XX:+PrintGCApplicationStoppedTime -XX:+PrintHeapAtGC 
-verbosegc -Xloggc:/var/log/bookie-gc.log -XX:G1LogLevel=finest
     PULSAR_MEM: |
       -Xms32g -Xmx32g -XX:MaxDirectMemorySize=32g
     PULSAR_PREFIX_dbStorage_readAheadCacheMaxSizeMb: "5120"
     PULSAR_PREFIX_journalDirectories: /pulsar/data/bookkeeper/journal
     PULSAR_PREFIX_numAddWorkerThreads: "4"
     PULSAR_PREFIX_numReadWorkerThreads: "16"
     autoRecoveryDaemonEnabled: "false"
     dbStorage_rocksDB_blockCacheSize: "536870912"
     dbStorage_rocksDB_writeBufferSizeMB: "1024"
     dbStorage_writeCacheMaxSizeMb: "5120"
     httpServerEnabled: "true"
     httpServerPort: "8000"
     journalDirectories: /pulsar/data/bookkeeper/journal
     journalMaxBackups: "0"
     ledgerDirectories: /pulsar/data/bookkeeper/ledgers
     statsProviderClass: 
org.apache.bookkeeper.stats.prometheus.PrometheusMetricsProvider
     useHostNameAsBookieID: "true"
     zkLedgersRootPath: /ledgers
   ```
   cc @sijie  is it a bug of bookkeeper in 4.10.0 version ?   any reply 
appreciate in adavance


-- 
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]

Reply via email to