[
https://issues.apache.org/jira/browse/FLINK-29108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713009#comment-17713009
]
Salva commented on FLINK-29108:
-------------------------------
[[email protected]] There is no recording available for your presentation
right? Queryable state looks like a good feature to me too, I would be
interested in keeping it alive too. On a related note, some people are opting
for externalizing the local state instead, see, e.g.:
-
[https://engineering.contentsquare.com/2022/flink-external-rocksdb-state-to-aerospike/]
- [https://www.youtube.com/watch?v=ZWq_TzsXssM
(FlinkNDB)|https://www.youtube.com/watch?v=ZWq_TzsXssM]
How likely is to add an external state backend to Flink in the short term? In
the meantime, it would be nice to have some guidelines / recommendations for
when to rely on Queryable State vs an external/global DB...
> Kubernetes operator: Support queryable state
> --------------------------------------------
>
> Key: FLINK-29108
> URL: https://issues.apache.org/jira/browse/FLINK-29108
> Project: Flink
> Issue Type: New Feature
> Components: Kubernetes Operator
> Reporter: Ron Crocker
> Priority: Minor
>
> Enable the kubernetes operator to deploy jobs where queryable state is
> desired.
> When queryable state is desired, the operator should configure the deployed
> job with
> # The deployed job has {{queryable-state.enabled:}} {{true}} applied to it.
> # Configure the Queryable State proxy and Queryable State server (via the
> {{queryable-state.proxy}} and {{queryable-state.server}} configuration
> sections respectively). If these sections aren't provided, then the default
> configuration is used.
> The operator will need to create a Kubernetes service fronting the Task
> Managers {{QueryableStateClientProxy}} port (as configured by the above).
> Tearing down the job also tears down the service.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
