You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bookkeeper.apache.org by GitBox <gi...@apache.org> on 2020/07/20 18:02:24 UTC

[GitHub] [bookkeeper] odidev commented on pull request #2379: Updated netty,netty-boringssl and rocksdb

odidev commented on pull request #2379:
URL: https://github.com/apache/bookkeeper/pull/2379#issuecomment-661245588


   @eolivelli , 
   
   > I see this is a major version bump for RocksDB.
   > Is the upgrade of RocksDB automatic? I am talking about files on disk. Do you need manual upgrade of data files?
   > In case of problems, if you rollback rocksdb to previous version, will the bookie work?
   
   Latest RocksDB is supported on aarch64, and its latest version was not being used in bookkeeper. So manually boomed RocksDB in bookkeeper in this PR.If rollback rocksdb to previous version , various tests are failing on aarch64 with JNI error like:
   `
   [ERROR] test(org.apache.bookkeeper.bookie.storage.ldb.ConversionTest)  Time elapsed: 2.506 s  <<< ERROR!
   com.google.common.util.concurrent.UncheckedExecutionException: Failed to load RocksDB JNI library
           at org.apache.bookkeeper.bookie.storage.ldb.ConversionTest.test(ConversionTest.java:118)
   Caused by: java.io.IOException: Failed to load RocksDB JNI library
           at org.apache.bookkeeper.bookie.storage.ldb.ConversionTest.test(ConversionTest.java:118)
   Caused by: java.lang.UnsatisfiedLinkError: /tmp/librocksdbjni4423711401334751285.so: /tmp/librocksdbjni4423711401334751285.so: cannot open shared object file: No such file or directory (Possible cause: can't load AMD 64-bit .so on a AARCH64-bit platform)
           at org.apache.bookkeeper.bookie.storage.ldb.ConversionTest.test(ConversionTest.java:118)
   `
   
   So latest rocksdb should be used.Current “Integration test” check failure does not seems specific to rocksdb or netty version updates.
   


----------------------------------------------------------------
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:
users@infra.apache.org