flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "vinoyang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-5931) Make Flink highly available even if defaultFS is unavailable
Date Wed, 13 Mar 2019 06:49:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16791378#comment-16791378
] 

vinoyang commented on FLINK-5931:
---------------------------------

[~wheat9] Are you still working on this issue? What's the status?

> Make Flink highly available even if defaultFS is unavailable
> ------------------------------------------------------------
>
>                 Key: FLINK-5931
>                 URL: https://issues.apache.org/jira/browse/FLINK-5931
>             Project: Flink
>          Issue Type: New Feature
>          Components: Runtime / Coordination
>            Reporter: Haohui Mai
>            Assignee: Haohui Mai
>            Priority: Major
>
> In order to use Flink in mission-critical environments, Flink must be available even
if the {{defaultFS}} is unavailable.
> We have deployed HDFS in HA mode in our production environment. In our experience we
have experienced performance degradations and downtime when the HDFS cluster is being expanded
or under maintenances. Under this case it is desirable to deploy jobs through alternative
filesystem (e.g., S3).
> This jira is to track the improvements to Flink to enable Flink to continue to operate
even {{defaultFS}} is unavailable.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message