blocks|key|2894003|text|尝试将fs.s3a.connection.maximum设置为50或100左右|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2894004|entityMap^0|3|P|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Try setting <code>fs.s3a.connection.maximum</code> to something like 50 or 100

blocks|key|2050290|text|为了详细说明Steve说了什么……问题很可能是，正在使用的HTTP客户机没有足够大的“连接池”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2050291|与单个桶交互的每个S3A客户机(作为单个用户)都有自己的专用开放HTTP1.1连接池，以及用于上载和复制操作的线程池。默认池大小的目的是在性能和内存/线程使用之间取得平衡。|blockquote|2050292|要了解可以优化的内容(包括fs.s3a.connection.max+)，请参阅这个Hadoop页面的“优化选项”部分。|offset|length|style|CODE|2050293|entityMap|0|LINK|mutability|MUTABLE|url|https://hadoop.apache.org/docs/r3.1.1/hadoop-aws/tools/hadoop-aws/performance.html^0|0|0|D|L|14|A|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$]]|$1|E|3|F|5|6|7|U|8|@$G|V|H|W|I|J]]|9|@$G|X|H|Y|1|Z]]|A|$]]|$1|K|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

to elaborate a bit on what Steve said...it's likely that the problem is the HTTP client being used doesn't have a large enough "connection pool". 

<blockquote>
 Each S3A client interacting with a single bucket, as a single user,
 has its own dedicated pool of open HTTP 1.1 connections alongside a
 pool of threads used for upload and copy operations. The default pool
 sizes are intended to strike a balance between performance and
 memory/thread use.
</blockquote>

For a good overview of things that you can tune (which includes <code>fs.s3a.connection.max</code> see the "Options to Tune" section of <a href="https://hadoop.apache.org/docs/r3.1.1/hadoop-aws/tools/hadoop-aws/performance.html" rel="nofollow noreferrer">this Hadoop page</a>.

blocks|key|2050355|text|因为Flink使用AWS连接代码，所以要执行的设置是fs.s3.maxConnections，这与纯Hadoop配置不一样。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2050356|在AWS上运行时，您可以参考以下文档：https://aws.amazon.com/cn/premiumsupport/knowledge-center/emr-timeout-connection-wait/|2050357|entityMap|0|LINK|mutability|MUTABLE|url|https://aws.amazon.com/cn/premiumsupport/knowledge-center/emr-timeout-connection-wait/^0|Q|K|0|J|2E|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@]|D|@$9|T|A|U|1|V]]|E|$]]|$1|H|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

Because Flink uses AWS connection code, the setting to bump is <code>fs.s3.maxConnections</code>, which isn't the same as a pure Hadoop configuration.

When running on AWS EMR, you can refer to this document: <a href="https://aws.amazon.com/cn/premiumsupport/knowledge-center/emr-timeout-connection-wait/" rel="nofollow noreferrer">https://aws.amazon.com/cn/premiumsupport/knowledge-center/emr-timeout-connection-wait/</a>

blocks|key|837192|text|对于任何发现这个的人-根据Flink文档的说法|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|837193|例如，Hadoop有一个fs.s3a.connection.maximum配置密钥。如果您想要更改它，需要将s3.connection.maximum:+xyz放在flink-+want+.+you中。Flink将在内部将其转换回fs.s3a.connection.maximum。|blockquote|837194|因此，要设置最大连接的值，实际上需要将s3.connection.maximum:+xyz+(或为我工作的s3a.connection.maximum:+xyz+)放在Flink配置中，以更改此值。|style|CODE|837195|entityMap|0|LINK|mutability|MUTABLE|url|https://nightlies.apache.org/flink/flink-docs-release-1.14/docs/deployment/filesystems/s3/#hadooppresto-s3-file-systems-plugins^0|D|7|0|0|0|J|Q|1H|R|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|C|$]]|$1|G|3|H|5|6|7|X|8|@$A|Y|B|Z|I|J]|$A|10|B|11|I|J]]|9|@]|C|$]]|$1|K|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

For anyone that finds this - according to the <a href="https://nightlies.apache.org/flink/flink-docs-release-1.14/docs/deployment/filesystems/s3/#hadooppresto-s3-file-systems-plugins" rel="nofollow noreferrer">Flink documentation</a>
<blockquote>
For example, Hadoop has a fs.s3a.connection.maximum configuration key. If you want to change it, you need to put s3.connection.maximum: xyz to the flink-conf.yaml. Flink will internally translate this back to fs.s3a.connection.maximum.
</blockquote>
So to set the value for maximum connections you actually want to put <code>s3.connection.maximum: xyz</code> (or <code>s3a.connection.maximum: xyz</code> which worked for me) in your Flink config to change this value.

I have a Flink job which has large state in a Map operator. We are taking savepoint which has around 80GB storing to AWS S3. We have around 100 parallelism for this operator. However, when we recover from the savepoint, there is always exception like

<blockquote>
 Caused by: java.io.InterruptedIOException: Failed to open s3a://xxxx/UbfK/flink/savepoints/logjoin/savepoint-a9600e-39fd2cc07076/f9a31490-461a-42f3-88be-ec169145c35f at 0 on s3a://adshonor-data-cube-test-apse1/UbfK/flink/savepoints/logjoin/savepoint-a9600e-39fd2cc07076/f9a31490-461a-42f3-88be-ec169145c35f: org.apache.flink.fs.s3base.shaded.com.amazonaws.SdkClientException: Unable to execute HTTP request: Timeout waiting for connection from pool.
</blockquote>

Is there a configuration parameter to increase the timeout settings for AWS S3 in Flink or another way to avoid this error?

Apache Flink: AWS S3 timeout exception when starting a job from a savepoint

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我有一个Flink作业，它在Map操作符中有很大的状态。我们正在采取保存点，它有大约80 S3的存储到AWS S3。对于这个操作符，我们有大约100个并行性。但是，当我们从保存点恢复时，总是会出现如下的异常原因是: s3a://xxxx/UbfK/flink/savepoints/logjoin/savepoint-a9600e-39fd2cc07076/f9a31490-461a-42f3-88

问Apache :从保存点启动作业时AWS S3超时异常
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Apache :从保存点启动作业时AWS S3超时异常EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Apache :从保存点启动作业时AWS S3超时异常
EN