The reason why this feature is not part of Flink is that it is not trivial to solve. There are definitely different solutions to the problem. I think that a solution will probably be built around Flink and not integrated into it because it goes a bit beyond what Flink's current focus is. I can tell you that companies are looking at this problem and want to solve it within their commercial offerings.
Cheers, Till On Thu, Apr 29, 2021 at 12:40 PM Enrique <enriquela...@gmail.com> wrote: > Hi Till and Bhagi, > > As part of our product, we also have a production requirement to deploy > Flink in multi zones and currently have it configured with Kubernetes HA. > > Till, is the reason this is not supported out of the box also due to the > fact Kubernetes HA relies on RWX storage and this is considered an > anti-pattern in the cloud native space? I've seen in Cloud Native > deployments that the recommended way is to replicate the state through > software instead of replicating the state through a shared > filesystem/storage which is a common pattern in data-centers. The cloud > native approach results in each instance of Flink across nodes owning their > own RWO filesystem and communicating through the network to other instance > across nodes to replicate state. I was just wondering if this had been > considered in the move to a more cloud-native Flink deployment? > > Cheers, > > Enrique > > > > > > -- > Sent from: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/ >
