Anyone? Otherwise, I will suggest to move forward with the PR using the assumption that Redis must be started manually.
-Matthias On 02/11/2016 08:28 PM, Matthias J. Sax wrote: > Hi, > > In Flink it is possible to have different backends for operator state. I > am wondering what the best approach for different state backends would be. > > Let's assume the backend is a database server. The following questions > arise: > - Should the database server be started manually by the user or can > Flink start the server automatically it used? > (this seems to be the approach for RocksDB as embedded servers) > - Should each job use the same or individual backup server (or maybe a > mix of both?) > > I personally think, that Flink should not start-up a backup server but > assume that it is available when the job is submitted. This allows the > user also the start up multiple instances of the backup server and > choose which one to use for each job individually. > > What do you think about it? I ask because of the current PR for Redis as > StateBackend: > https://github.com/apache/flink/pull/1617 > > There is no embedded mode for Redis as for RocksDB. > > -Matthias >
signature.asc
Description: OpenPGP digital signature
