blocks|key|1979080|text|使用UpdateFunctionCode+API端点强制刷新所有容器。AWS+SDK将其封装起来，使您更容易使用您喜欢的语言调用API。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1979081|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.aws.amazon.com/lambda/latest/dg/API_UpdateFunctionCode.html|1|https://aws.amazon.com/tools/#sdk^0|2|I|2|I|0|Z|7|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@$9|S|A|T|1|U]|$9|V|A|W|1|X]]|E|$]]|$1|F|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]|N|$5|I|J|K|E|$L|O]]]]

Use the <a href="https://docs.aws.amazon.com/lambda/latest/dg/API_UpdateFunctionCode.html" rel="noreferrer"><code>UpdateFunctionCode</code></a> API endpoint to force a refresh of all containers. <a href="https://aws.amazon.com/tools/#sdk" rel="noreferrer">AWS SDKs</a> wrap this up to make it easier for you to call the API using your preferred language.

blocks|key|1979183|text|我的回答是基于我的评论和验证，来自@DejanVasic|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1979184|aws+lambda+update-function-configuration+--function-name+"myLambda"+--description+"foo"|code-block|syntax|javascript|1979185|这将迫使羔羊的下一轮“冷启动”。|1979186|核实：|1979187|@timestamp,+@message+%7C+sort+@timestamp+desc+%7C+limit+1000+%7C+filter+@message+like+"cold_start:true"|1979188|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|S|8|@]|9|@]|A|$E|F]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I made an Answer based on my comment and verification from @DejanVasic 

<pre><code>aws lambda update-function-configuration --function-name "myLambda" --description "foo"
</code></pre>

This will force the next invokation of the lambda to "cold start".

To verify:

<pre><code>@timestamp, @message | sort @timestamp desc | limit 1000 | filter @message like "cold_start:true"
</code></pre>

blocks|key|1979227|text|我发现的最简单的方法是在基本设置中更改一些内容，比如超时：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1979228|📷|atomic|offset|length|1979229|​|1979230|我已经保存了upped%2B1一秒钟，函数被刷新了|1979231|1979232|1979233|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/083781a1268f50d4d882160ec3e11ef9.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/bf0c6f3ca82d660df25ac3a2e6a16a0f.png^0|0|0|1|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Y|8|@]|9|@$E|Z|F|10|1|11]]|A|$]]|$1|G|3|H|5|6|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|13|8|@]|9|@]|A|$]]|$1|K|3|C|5|D|7|14|8|@]|9|@$E|15|F|16|1|17]]|A|$]]|$1|L|3|H|5|6|7|18|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T|U|-4]]|V|$5|P|Q|R|A|$S|W|U|-4]]]]

Easiest way I found was changing something in Basic Settings like timeout:
<a href="https://i.stack.imgur.com/pDdGi.png" rel="noreferrer"><img src="https://i.stack.imgur.com/pDdGi.png" alt="Basic Settings" /></a>
I've upped+1 by a second, saved, and the function got refreshed
<a href="https://i.stack.imgur.com/fHFCy.png" rel="noreferrer"><img src="https://i.stack.imgur.com/fHFCy.png" alt="Memory and timeout settings" /></a>

blocks|key|743889|text|目前，无法强制重新运行Lambda容器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|743890|但是，您可以重新部署函数，以便从那时起开始使用新的容器。|743891|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Currently, there is no way to force restarts on running Lambda containers.

You can, however, redeploy the function so that it will start using new containers from that point onwards.

blocks|key|1853870|text|如果您正在使用Lambda版本控制系统，另一种方法是发布一个新版本并使用别名将所有流量定向到它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1853871|下面是一个例子：|1853872|发布版本：aws+lambda+publish-version+--function-name+your-function-name-here|offset|length|style|CODE|1853873|更新别名指向新版本：aws+lambda+update-alias+--function-name+your-function-name-here+--name+alias-name-here+--function-version+123+(在上面第一个命令的输出消息中使用函数版本)|1853874|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.aws.amazon.com/cli/latest/reference/lambda/publish-version.html|1|https://docs.aws.amazon.com/cli/latest/reference/lambda/update-alias.html^0|0|0|5|1U|0|4|0|0|A|31|0|4|1|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@$F|Y|G|Z|H|I]]|9|@$F|10|G|11|1|12]]|A|$]]|$1|J|3|K|5|6|7|13|8|@$F|14|G|15|H|I]]|9|@$F|16|G|17|1|18]]|A|$]]|$1|L|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|U]]]]

If you are using the Lambda versioning system, another way to do this is by publishing a new version and using an alias to direct all traffic to it.

Here's an example:

<a href="https://docs.aws.amazon.com/cli/latest/reference/lambda/publish-version.html" rel="nofollow noreferrer">Publish version</a>:
<code>aws lambda publish-version --function-name your-function-name-here</code>

<a href="https://docs.aws.amazon.com/cli/latest/reference/lambda/update-alias.html" rel="nofollow noreferrer">Update the alias</a> pointing to the new version:
<code>aws lambda update-alias --function-name your-function-name-here --name alias-name-here --function-version 123</code> (use the function version in the output message from the first command above)

blocks|key|744185|text|只需添加一个新的环境变量和/或更改现有的环境变量即可。我创建了一个名为假的，并给它一个数字，我增加时，我想要一个冷的开始。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|744186|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Simply add a new environment variable and / or change an existing one. I created one named BOGUS and gave it a number that I increment whenever I want to force a cold start.

blocks|key|1979107|text|强制lambda丢弃现有容器的唯一方法是用一些不同的东西重新部署函数。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1979108|看看我的答案：武力丢弃AWS+Lambda集装箱|offset|length|1979109|祝你好运，莫|1979110|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/47445815/force-discard-aws-lambda-container/47447475#47447475^0|0|7|H|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

The only way force lambda to discard existing containers is to redeploy the function with something different.

Check out my answer here: <a href="https://stackoverflow.com/questions/47445815/force-discard-aws-lambda-container/47447475#47447475">Force Discard AWS Lambda Container</a>

Good luck,
Moe

blocks|key|744169|text|除了上面的一些有效答案:我碰巧在(平均)+AWS实例生存期上运行了一个实验。我找不到运行时间远远超过(平均)两个小时的实例：https://xebia.com/blog/til-that-aws-lambda-terminates-instances-preemptively/。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|744170|TL;DR:+AWS+Lambda在两个小时后先发制人地终止实例(甚至那些处理流量的实例)，标准偏差为30分钟。|744171|entityMap|0|LINK|mutability|MUTABLE|url|https://xebia.com/blog/til-that-aws-lambda-terminates-instances-preemptively/^0|1Q|25|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

In addition to some of the valid answers above: I happened to run an experiment on the (average) AWS Lambda instance lifetime. I could not find instances that ran for much longer than (on average) two hours: <a href="https://xebia.com/blog/til-that-aws-lambda-terminates-instances-preemptively/" rel="nofollow noreferrer">https://xebia.com/blog/til-that-aws-lambda-terminates-instances-preemptively/</a>.
TL;DR: AWS Lambda is preemptively terminating instances (even those handling traffic) after two hours, with a standard deviation of 30 minutes.

blocks|key|1979293|text|对于这个问题，我发现最简单的答案是。对函数进行一些更改，例如添加一个简单的注释行或删除任何空白，然后重新部署该函数。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1979294|它将在部署时清除缓存。|1979295|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The simplest answer for this question I found is. Make some changes in function like adding a simple comment line or removing any white space and then redeploy the function.
It will clear the cache while deploying.

blocks|key|744248|text|在雷纳托·比罗氏回答之后，我使用JavaScript+AWS创建了一个lambda函数，通过更新描述重新启动另一个lambda函数。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|744249|import+{+LambdaClient,+UpdateFunctionConfigurationCommand+}+from+'@aws-sdk/client-lambda';

const+forceLambdaRestart+=+async+event+=>+{
++++try+{
++++++++const+client+=+new+LambdaClient({
++++++++++++region:+'your+region+here',
++++++++++++credentials:+{
++++++++++++++++accessKeyId:+'your+access+key+id',
++++++++++++++++secretAccessKey:+'your+secret+access+key',
++++++++++++},
++++++++});

++++++++const+command+=+new+UpdateFunctionConfigurationCommand({
++++++++++++FunctionName:+event.functionName,
++++++++++++Description:+`forced+update+${Date.now()}`,
++++++++});

++++++++const+data+=+await+client.send(command);

++++++++console.log(data);
++++++++return+data;
++++}+catch+(error)+{
++++++++console.error(error);
++++++++return+error;
++++}
};

forceLambdaRestart();|code-block|syntax|javascript|744250|这似乎足以重新启动lambda并清除内存缓存。|744251|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/50901941/11896010|1|https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/clients/client-lambda/^0|1|7|0|G|E|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]|$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|F|7|11|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|12|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|13|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]|S|$5|N|O|P|C|$Q|T]]]]

Following <a href="https://stackoverflow.com/a/50901941/11896010">Renato Byrro's</a> answer I made a lambda function using <a href="https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/clients/client-lambda/" rel="nofollow noreferrer">JavaScript AWS SDK</a> to restart another lambda function by updating the description.

<pre><code>import { LambdaClient, UpdateFunctionConfigurationCommand } from '@aws-sdk/client-lambda';

const forceLambdaRestart = async event =&gt; {
 try {
 const client = new LambdaClient({
 region: 'your region here',
 credentials: {
 accessKeyId: 'your access key id',
 secretAccessKey: 'your secret access key',
 },
 });

 const command = new UpdateFunctionConfigurationCommand({
 FunctionName: event.functionName,
 Description: `forced update ${Date.now()}`,
 });

 const data = await client.send(command);

 console.log(data);
 return data;
 } catch (error) {
 console.error(error);
 return error;
 }
};

forceLambdaRestart();
</code></pre>

It seems like that is enough to restart the lambda and clear in-memory cache.

I have a AWS Lambda function that creates an object from a s3 call in cold start. I then hold the object in the cache while the function is warm to keep load times down. When files are changed in s3, I have a trigger to run the lambda, but not all the running instances of lambda restart and pull from s3.

Is there a way to bring down all instances of lambda forcing a full cold start?

Also, I don't want to use python.

Restarting AWS lambda function to clear cache

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯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编辑器全新改版上线，欢迎大家体验!

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

社区新版编辑器体验调研

我有一个AWS函数，它在冷启动时通过s3调用创建一个对象。然后，当函数温暖时，我将对象保存在缓存中，以减少加载时间。在s3中更改文件时，我有一个触发器来运行lambda，但不是所有正在运行的lambda实例都重新启动并从s3中提取。有没有一种方法可以让所有的lambda强制完全冷启动？而且，我不想使用python。

问重新启动AWS lambda函数以清除缓存
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问重新启动AWS lambda函数以清除缓存EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问重新启动AWS lambda函数以清除缓存
EN