Re: Difficulties with Minio state storage

2020-09-09 Thread Rex Fenley
Good news! Eliminating bsEnv.setStateBackend( new RocksDBStateBackend( "s3://flink-jdbc-test_graph-minio_1/data/checkpoints:9000", true ) ) moving all configuration into FLINK_PROPERTIES and switching to http seemed to do the trick! Thanks for all the help! On Wed, Sep 9, 2020 at

Re: Difficulties with Minio state storage

2020-09-09 Thread Rex Fenley
Thanks yall, Yangze, > I've tried to use MinIO as state backend and everything seems works well For clarity, I'm using RocksDB state backend with Minio as state storage. > s3.endpoint: http://localhost:9000 Also, I'm doing everything from docker-compose so localhost isn't going to work in my

Re: Difficulties with Minio state storage

2020-09-09 Thread Arvid Heise
Hi Rex, you could also check the end to end tests that use minio in flink's repo. You definitely need to use an http endpoint. The setup [1] uses also another way to specify the s3.path.style.access (with dashes). I think we needed it especially for presto. It seems like the settings differ a

Re: Difficulties with Minio state storage

2020-09-08 Thread Yangze Guo
Hi, Rex, I've tried to use MinIO as state backend and everything seems works well. Just sharing my configuration: ``` s3.access-key: s3.secret-key: s3.endpoint: http://localhost:9000 s3.path.style.access: true state.checkpoints.dir: s3://flink/checkpoints ``` I think the problem might be caused

Difficulties with Minio state storage

2020-09-08 Thread Rex Fenley
Hello! I'm trying to test out Minio as state storage backend using docker-compose on my local machine but keep running into errors that seem strange to me. Any help would be much appreciated :) The problem: With the following environment: environment: - | FLINK_PROPERTIES=