blocks|key|369170|text|Heroku应该在每次worker崩溃时重新启动它。据我所知，你不需要选择或配置任何东西。无论你的工作是什么:工作任务一旦失败就会立即执行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|369171|如果您严重依赖于web应用程序中的后台作业。您可以创建一个rake任务来查找要更新的最后一条记录，并执行一个后台作业来更新它。或者可能自动执行rake任务，以查找自上次崩溃以来需要更新的其余记录。|369172|或者，您可以按照this+article中所述(使用delayed_job)手动强制重新启动worker：|offset|length|369173|heroku+workers+0;+
heroku+workers+1;|code-block|syntax|javascript|369174|或者，您可以通过执行以下操作(在this+article中提到)重新启动特定的工作进程：|369175|heroku+restart+worker.1|369176|顺便说一下，试试1.9+stack。在执行此操作之前，请确保您的应用程序与1.9.2兼容。希望那里的崩溃不那么频繁：|369177|heroku+stack:migrate+bamboo-mri-1.9.2|369178|在这种情况下，这些问题仍然会出现。最好联系Heroku支持部门。他们对自己所做的事情反应非常灵敏。|369179|entityMap|0|LINK|mutability|MUTABLE|url|http://devcenter.heroku.com/articles/delayed-job|1|http://devcenter.heroku.com/articles/ps#process_restarts|2|http://devcenter.heroku.com/articles/stack^0|0|0|8|C|0|0|0|G|C|1|0|0|8|9|2|0|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1A|8|@]|9|@$F|1B|G|1C|1|1D]]|A|$]]|$1|H|3|I|5|J|7|1E|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1F|8|@]|9|@$F|1G|G|1H|1|1I]]|A|$]]|$1|O|3|P|5|J|7|1J|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|1K|8|@]|9|@$F|1L|G|1M|1|1N]]|A|$]]|$1|S|3|T|5|J|7|1O|8|@]|9|@]|A|$K|L]]|$1|U|3|V|5|6|7|1P|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]|14|$5|Z|10|11|A|$12|15]]|16|$5|Z|10|11|A|$12|17]]]]

Heroku is supposed to restart a worker every time it crashes. As far as I know, you don't have to select or configure anything. Whatever is in your jobs:work task will be executed as soon as it fails.

In the event that you are heavily dependent on background jobs in your web app. You could create a rake task that finds the last record to be updated and execute a background job to update it. Or perhaps automate the rake task to find the rest of the records that need updating, since the last crash.

Alternatively, you force worker restart manually as indicated in <a href="http://devcenter.heroku.com/articles/delayed-job" rel="noreferrer">this article</a> (using delayed_job):

<pre><code>heroku workers 0; 
heroku workers 1;
</code></pre>

Or perhaps you can restart a specific worker by doing (mentioned in <a href="http://devcenter.heroku.com/articles/ps#process_restarts" rel="noreferrer">this article</a>):

<pre><code>heroku restart worker.1
</code></pre>

By the way, try the <a href="http://devcenter.heroku.com/articles/stack" rel="noreferrer">1.9 stack</a>. Make sure your app is 1.9.2 compatible, before doing so. Hopefully crashes are less frequent there:

<pre><code>heroku stack:migrate bamboo-mri-1.9.2
</code></pre>

In the event, that such issues still arise. Best to contact Heroku support. They are very responsive at what they do.

blocks|key|3061247|text|用于重新启动特定heroku+web+worker的最新命令(2014)：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3061248|heroku+ps:restart+web.1|code-block|syntax|javascript|3061249|(在雪松堆栈上测试)|3061250|entityMap^0|8|H|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

Latest command to restart a specific heroku web worker (2014):

<pre><code>heroku ps:restart web.1
</code></pre>

(tested on Cedar stack)

blocks|key|2226850|text|有时，例如在DB崩溃的情况下，worker可能不会自动重新启动。你需要这样做。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2226851|heroku重启web.1|offset|length|style|BOLD|2226852|这对我很管用。|2226853|entityMap^0|0|0|D|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

At times, for instance in case of DB crashes, the worker may not restart automatically. you would need to do this.

heroku restart web.1

It worked for me.

I have a worker doing some processing 24/7. However, sometimes the code crashes and it needs to be restarted (even if I catch the exception, I have to restart the worker in order for it to work).

What do you do when this happens or am I doing something wrong and this shouldn't happen at all? Does your dynos/workers crash or it is just me?

thanks

Heroku: What to do when your dyno/worker crashes?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我有一个worker在做一些全天候的处理。然而，有时代码会崩溃，需要重新启动(即使我捕捉到异常，我也必须重新启动worker才能让它工作)。当这种情况发生时，或者我做错了什么而这根本不应该发生时，你该怎么办？你的dynos/worker崩溃了还是只有我一个人崩溃了？谢谢

问当你的dyno/worker崩溃时该怎么办？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问当你的dyno/worker崩溃时该怎么办？EN