ate.backend: rocksdb
state.checkpoints.dir: hdfs:///checkpoint-path
Best
Yun Tang
From: Bajaj, Abhinav
Sent: Wednesday, April 29, 2020 3:16
To: Yun Tang ; user@flink.apache.org
Cc: Chesnay Schepler
Subject: Re: RocksDB default logging configuration
Thanks Yun for your r
.
Thanks much,
~ Abhinav Bajaj
From: Yun Tang
Date: Monday, April 27, 2020 at 8:17 PM
To: "Bajaj, Abhinav" , "user@flink.apache.org"
Cc: Chesnay Schepler
Subject: Re: RocksDB default logging configuration
CAUTION: This email originated from outside of the organization. Do not
-L301
Best
Yun Tang
From: Bajaj, Abhinav
Sent: Tuesday, April 28, 2020 8:03
To: user@flink.apache.org
Cc: Chesnay Schepler
Subject: Re: RocksDB default logging configuration
It seems requiring the checkpoint URL to create the RocksDBStateBackend mixes
up the operational aspects o
possible.
I am using Flink 1.7.1.
Thanks Chesnay for your response below.
~ Abhinav Bajaj
From: Chesnay Schepler
Date: Wednesday, April 22, 2020 at 11:17 PM
To: "Bajaj, Abhinav" , "user@flink.apache.org"
Subject: Re: RocksDB default logging configuration
CAUTION: This e
*RocksDB default logging configuration
Hi,
Some of our teams ran into the disk space issues because of RocksDB
default logging configuration - FLINK-15068
<https://issues.apache.org/jira/browse/FLINK-15068>.
It seems the workaround suggested uses the OptionsFactory to set some
of the parameters
Bumping this one again to catch some attention.
From: "Bajaj, Abhinav"
Date: Monday, April 20, 2020 at 3:23 PM
To: "user@flink.apache.org"
Subject: RocksDB default logging configuration
Hi,
Some of our teams ran into the disk space issues because of RocksDB default
l
Hi,
Some of our teams ran into the disk space issues because of RocksDB default
logging configuration -
FLINK-15068<https://issues.apache.org/jira/browse/FLINK-15068>.
It seems the workaround suggested uses the OptionsFactory to set some of the
parameters from inside the job.
Si
