[
https://issues.apache.org/jira/browse/FLINK-5993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-5993:
----------------------------------
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.
> Add section about Azure deployment
> -----------------------------------
>
> Key: FLINK-5993
> URL: https://issues.apache.org/jira/browse/FLINK-5993
> Project: Flink
> Issue Type: Improvement
> Components: Documentation
> Reporter: Ufuk Celebi
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> Running Flink on Azure can lead to unexpected problems. From the user mailing
> list:
> {quote}
> For anyone seeing this thread in the future, we managed to solve the issue.
> The problem was in the Azure storage SDK.
> Flink is using Hadoop 2.7, so we used version 2.7.3 of the Hadoop-azure
> package. This package uses version 2.0.0 of the azure-storage package, dated
> from 2014. It has several bugs that were since fixed, specifically one where
> the socket timeout was infinite. We updated this package to version 5.0.0 and
> everything is working smoothly now.
> {quote}
> (http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Flink-checkpointing-gets-stuck-td11776.html)
> At least this caveat should be covered.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
