[
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 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.
> 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-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)
