You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Yun Tang (Jira)" <ji...@apache.org> on 2023/05/08 11:05:00 UTC

[jira] [Commented] (FLINK-31743) Avoid relocating the RocksDB's log failure when filename exceeds 255 characters

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

Yun Tang commented on FLINK-31743:
----------------------------------

merged in master: bdb0233eb83629c3bb1b1487057b22891c41c437

For older Flink versions, please take a look at my comment https://github.com/apache/flink/pull/22458/files#r1187314041 to create another PR (for 1.17) [~Feifan Wang]

> Avoid relocating the RocksDB's log failure when filename exceeds 255 characters
> -------------------------------------------------------------------------------
>
>                 Key: FLINK-31743
>                 URL: https://issues.apache.org/jira/browse/FLINK-31743
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / State Backends
>    Affects Versions: 1.16.1, 1.15.4
>            Reporter: jinghaihang
>            Assignee: Feifan Wang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.16.2, 1.18.0, 1.17.1
>
>
> Since FLINK-24785 , the file name of the rocksdb LOG is generated by parsing the db path, when the db path is long and the filename exceeds 255 characters, the creation of the file will fail, so the relevant rocksdb LOG cannot be seen in the flink log dir.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)