[
https://issues.apache.org/jira/browse/FLINK-24314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shiwuliang updated FLINK-24314:
-------------------------------
Affects Version/s: 1.13.2
> Always use memory state backend with RocksDB
> --------------------------------------------
>
> Key: FLINK-24314
> URL: https://issues.apache.org/jira/browse/FLINK-24314
> Project: Flink
> Issue Type: Bug
> Affects Versions: 1.13.0, 1.13.2
> Reporter: shiwuliang
> Priority: Major
> Attachments: image-2021-09-17-10-59-50-094.png,
> image-2021-09-17-12-03-58-285.png, image-2021-09-17-12-04-55-009.png,
> image-2021-09-17-12-16-46-277.png, image-2021-09-17-17-46-07-196.png,
> image-2021-09-17-17-47-20-950.png, image-2021-09-17-17-50-19-099.png
>
>
> When I config to use `RocksDBStatebackend`,
>
> {code:java}
> //代码占位符
> RocksDBStateBackend rocksDBStateBackend = new
> RocksDBStateBackend("hdfs://xxxx");
> streamEnv.setStateBackend(rocksDBStateBackend);{code}
>
> there are some exception like this:
> !image-2021-09-17-10-59-50-094.png|width=1446,height=420!
>
> Seems like the RocksdbStatebackend will use FsStateBackend to store
> checkpoints. So it means that I have used FileSystemStateBackend, why does
> this exception occur?
>
> I use flink 1.13.0 and found a similar question like this at:
> [https://stackoverflow.com/questions/68314652/flink-state-backend-config-with-the-state-processor-api]
>
> I'm not sure if his question is same with mine.
> I want to know how can I solve this and if it is indeed a 1.13.0 bug, how can
> I bypass it besides upgrading?
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
