-
Notifications
You must be signed in to change notification settings - Fork 13.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KAFKA-5576: increase the rocksDB version to 5.5.1 for Power support #3519
Conversation
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
@yussufsh which power support you were referring to? http://rocksdb.org/blog/ cc @enothereska |
I noticed a unit test failure with message |
Also when running locally on my laptop I got: |
@enothereska Thanks for looking at this. Also, let me know the jdk & scala version you are working with. |
@guozhangwang From version 5.3.6 onwards , rocksdb has IBM PowerPC64 Little-Endian support (PPC64LE). https://github.com/facebook/rocksdb/releases/tag/v5.3.6 |
@enothereska I got the AssertionError in RocksDBStoreTest#shouldThrowProcessorStateExceptionOnOpeningReadOnlyDir if that is what you are referring to? |
@yussufsh thank you. One error you can see is the one from Jenkins above "JDK 7...". If you go under Details you'll see a |
I am not able to see the details of the build failure where you mentioned pure virtual error. However I am still getting the AssertionError on the RHEL machine:
|
Hi @enothereska |
Hi @yussufsh we need to have 1) the Jenkins build on the unit test to pass at least once (they are running on AWS), and 2) you can help validate that all unit tests still passed on RHEL machine using I can help with 3), and 1) could be done by typing |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Now the failures are gone, this is good to go i guess. |
I don't think so the build has the version changes. I need to rebase the feature branch with latest Kafka code then we can request the build. I will do this as soon as I am back in office. |
The build has the version changes. In the console output, i am able to see maven downloads rocksDB 5.5.1 artifact |
Hi @guozhangwang |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
When running locally on a MacOS (version 10.10.5), I still see the following error message as @enothereska reported:
As shown above I ran it twice and both times it fails but around different test cases, so I suspect it is not boiled down to a specific test case but a general transient issue in rocksDB |
Thanks @guozhangwang |
I think there might be regression introduced in the 5.4.5, and lasts in 5.5.1 and 5.6.1 as well. We need to hold on further upgrading until it was resolved in a future release. |
This is the issue containing the discussion: facebook/rocksdb#2533 (comment) |
Notable updates: 1. Gradle 4.1 includes a number of performance and CLI improvements as well as initial Java 9 support. 2. Scala 2.12.3 has substantial compilation time improvements. 3. lz4-java 1.4 allows us to remove a workaround in KafkaLZ4BlockInputStream (not done in this PR). 4. snappy-java 1.1.4 improved performance of compression (5%) and decompression (20%). There was a slight increase in the compressed size in one of our tests. Not updated: 1. PowerMock due to a couple of regressions. I investigated one of them and filed powermock/powermock#828. 2. Jackson, which will be done via #3631. 3. Rocksdb, which will be done via #3519. Author: Ismael Juma <ismael@juma.me.uk> Reviewers: Jason Gustafson <jason@confluent.io> Closes #3619 from ijuma/update-deps-for-1.0.0
The latest version is now 5.7.3. Do we also have to upgrade due to the license change? |
I can try that, not sure if the issue is resolved in 5.7.3. |
@yussufsh @ayappanec We have upgraded to 5.8 in #3819. If that has resolved your intention please feel free to close this PR. |
Thnanks @guozhangwang |
No description provided.