You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Haohui Mai (JIRA)" <ji...@apache.org> on 2017/02/27 20:06:45 UTC

[jira] [Commented] (FLINK-5931) Make Flink highly available even if defaultFS is unavailable

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

Haohui Mai commented on FLINK-5931:
-----------------------------------

I have confirmed with [~gtCarrera9] (a YARN committer and Hadoop PMC) that YARN can continue to operate even if the {{defaultFS}} is unavailable.

> 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: Improvement
>            Reporter: Haohui Mai
>            Assignee: Haohui Mai
>
> 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
(v6.3.15#6346)