You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Guozhang Wang (Jira)" <ji...@apache.org> on 2021/09/01 17:05:00 UTC

[jira] [Commented] (KAFKA-13257) KafkaStreams Support For Latest RocksDB Version

    [ https://issues.apache.org/jira/browse/KAFKA-13257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408280#comment-17408280 ] 

Guozhang Wang commented on KAFKA-13257:
---------------------------------------

Hello [~kannan94], in the next release 3.0 which is going to be released very soon, we have upgraded rocksDB to 6.19 (https://issues.apache.org/jira/browse/KAFKA-8897).

> KafkaStreams Support For Latest RocksDB Version
> -----------------------------------------------
>
>                 Key: KAFKA-13257
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13257
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 2.8.0
>            Reporter: Alagukannan
>            Priority: Major
>         Attachments: hs_err_pid6.log
>
>
> Hi,
>  Can you please let us know if there is any plan for adding the latest versions of rocksDB in kafka streams. If your planning it what's the timeline we are looking at. If not planning to upgrade what's the reason behind it. Is there any significant impact on upgrading like backward combability etc.. Just to remind this general query to know about the rocksdb upgrade and its impact on streams application.
> The main pain point behind asking this upgrade is, We tried to build an application with kafka streams 2.8.0 on an alpine based OS and the docker base image is as follows  azul/zulu-openjdk-alpine:11.0.12-11.50.19-jre-headless.  The streams application worked fine until it had an interaction with state store(rocksdb). The jvm crashed with the following error:
>  #
>  # A fatal error has been detected by the Java Runtime Environment:
>  #
>  # SIGSEGV (0xb) at pc=0x00007f9551951b27, pid=6, tid=207
>  #
>  # JRE version: OpenJDK Runtime Environment Zulu11.45+27-CA (11.0.10+9) (build 11.0.10+9-LTS)
>  # Java VM: OpenJDK 64-Bit Server VM Zulu11.45+27-CA (11.0.10+9-LTS, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
>  # Problematic frame:
>  # C [librocksdbjni15322693993163550519.so+0x271b27] std::_Rb_tree<std::string, std::string, std::_Identity<std::string>, std::less<std::string>, std::allocator<std::string> >::_M_erase(std::_Rb_tree_node<std::string>*)+0x27
> Then we found out rocksdb works well on glibc and not musl lib, where as alpine supports musl lib alone for native dependencies. Further looking into rocksdb for a solution we found that they have started supporting both glib and musl native libs from 6.5.x versions.
>  But latest kafka streams(2.8.0) is having rocksdb(5.18.x) version. This is the main reason behind asking for the rocksDB upgrade in kafka streams as well.
> Have attached the PID log where JVM failures are happening.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)