[
https://issues.apache.org/jira/browse/FLINK-24785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17705952#comment-17705952
]
jinghaihang commented on FLINK-24785:
-------------------------------------
I encountered a problem during actual use:
Since 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.
Supplementary information: My deployment mode is yarn.
Do you think this is a problem? [~yunta] [~nicholasjiang]
> Relocate RocksDB's log under flink log directory by default
> -----------------------------------------------------------
>
> Key: FLINK-24785
> URL: https://issues.apache.org/jira/browse/FLINK-24785
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / State Backends
> Reporter: Yun Tang
> Assignee: Nicholas Jiang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> Previously, RocksDB's log locates at its own DB folder, which makes the
> debuging RocksDB not so easy. We could let RocksDB's log stay in Flink's log
> directory by default.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
