flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From StephanEwen <...@git.apache.org>
Subject [GitHub] flink pull request #3060: [FLINK-5408] [RocksDB backend] Uniquify RocksDB JN...
Date Wed, 04 Jan 2017 23:31:26 GMT
GitHub user StephanEwen opened a pull request:


    [FLINK-5408] [RocksDB backend] Uniquify RocksDB JNI library path to avoid multiple classloader

    When the RocksDB is loaded from different ClassLoaders (for example because it is in the
user code jar, or loaded dynamically in tests) it may fail with an
    java.lang.UnsatisfiedLinkError: Native Library /path/to/temp/dir/librocksdbjni-linux64.so
already loaded in another classloader.
    Apparently the JVM can handle multiple instances of the same JNI library being loaded
in different class loaders, but not when coming from the same file path.
    This makes sure the JNI lib path is unique to circumvent this.
    The test reflectively loads different versions of the class from different class loaders
to validate that.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/StephanEwen/incubator-flink rdb_loading

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3060
commit d5256a2e89004c436bc7943affaec16b91cdb56a
Author: Stephan Ewen <sewen@apache.org>
Date:   2017-01-04T23:18:13Z

    [FLINK-5408] [RocksDB backend] Uniquify RocksDB JNI library path to avoid multiple classloader


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message