[
https://issues.apache.org/jira/browse/FLINK-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-5931:
----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> 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.20.1#820001)
