[
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 stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or 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: Minor
> Labels: auto-deprioritized-major, stale-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)
