You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/03/01 10:39:00 UTC

[jira] [Updated] (FLINK-16686) [State TTL] Make user class loader available in native RocksDB compaction thread

     [ https://issues.apache.org/jira/browse/FLINK-16686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-16686:
-----------------------------------
    Labels: auto-deprioritized-major auto-deprioritized-minor stale-major  (was: auto-deprioritized-major auto-deprioritized-minor)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> [State TTL] Make user class loader available in native RocksDB compaction thread
> --------------------------------------------------------------------------------
>
>                 Key: FLINK-16686
>                 URL: https://issues.apache.org/jira/browse/FLINK-16686
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / State Backends
>    Affects Versions: 1.8.0, 1.11.3, 1.13.0, 1.12.3
>            Reporter: Andrey Zagrebin
>            Priority: Major
>              Labels: auto-deprioritized-major, auto-deprioritized-minor, stale-major
>
> The issue is initially reported [here|https://stackoverflow.com/questions/60745711/flink-kryo-serializer-because-chill-serializer-couldnt-be-found].
> The problem is that the java code of Flink compaction filter is called from RocksDB native C++ code. It is called in the context of the native compaction thread. RocksDB has utilities to create java Thread context for the Flink java callback. Presumably, the Java thread context class loader is not set at all and if it is queried then it produces NullPointerException.
> The provided report enabled a list state with TTL. The compaction filter has to deserialise elements to check expiration. The deserialiser relies on Kryo which queries the thread context class loader which is expected to be the user class loader of the task but turns out to be null.
> We should investigate how to pass the user class loader to the compaction thread of the list state with TTL.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)