[
https://issues.apache.org/jira/browse/FLINK-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328821#comment-17328821
]
Flink Jira Bot commented on FLINK-5931:
---------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> 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
> Priority: Major
> Labels: stale-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
(v8.3.4#803005)
