[
https://issues.apache.org/jira/browse/FLINK-31743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17711654#comment-17711654
]
jinghaihang commented on FLINK-31743:
-------------------------------------
Hi [~roman]
Previously, Tang Yun and I discussed a two-step approach to addressing this
issue:
firstly, avoiding relocation of logs in RocksDB when the path name exceeds 255
characters on the Flink side.
Secondly, renaming the file from the FRocksDB perspective.
I have completed development of the second step, but I am still working on the
first.
It's important to consider the potential impact on distinguishing between
multiple operator logs in the previous database directory.
While I am quite busy this week, I plan to allocate time to address this over
the next couple of days.
What do you think?
> 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: jinghaihang
> Priority: Major
> 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)
