计时器工作需要很长时间才能完成sharepoint 2010 [英] Timer jobs taking long time to complete sharepoint 2010

问题描述

我们有一个自定义计时器作业，该作业计划在生产中每5分钟运行一次，并对两者进行测试.经过测试，其工作时间为10-15秒.但是在生产过程中，要花费4个小时甚至有时比完成更多的时间.

We have a custom timer job which is scheduled to run every 5 mins on production and test both. On test its working and taking 10-15 seconds to complete. But on production its taking 4 hours or sometimes more than that to complete. 

这是不正确的，因为如果计划将其每5分钟运行一次，那么它应该仅在5分钟内完成.我检查了ULS日志，但无非是此上一次出现的'abc，id'{E198FA4D-D3E0-4C82-8365-04DDA5645870}' 服务'{9633170A-1517-41E6-8CC0-395F17FEF380}'仍在运行，因此将跳过当前实例.您应该考虑增加作业之间的间隔

This is not correct because if its scheduled to run every 5 mins then it should complete in that 5 mins only. I checked the ULS logs but nothing more than this " The previous occurrence of the 'abc, id '{E198FA4D-D3E0-4C82-8365-04DDA5645870}' for the service '{9633170A-1517-41E6-8CC0-395F17FEF380}' is still running so that the current instance is skipped . You should consider increasing the interval between the jobs" .

请让我知道我应该关注的领域以及可能的原因.

Please let me know which areas I should look upon and what could be the possible causes for this.

此致

Manish

推荐答案

在定义计时器作业时验证您的SPJobLockType，选择正确的optioon.别忘了在生产环境中，我们通常会有更多的内容数据库，服务器场中的更多计算机，并且如果SPJobLockType的配置不符合您的需要， 您会浪费很多时间:

Verify your SPJobLockType when you define your timer job, choose the right optioon. Don't forget that on production environment we have normally more content databases, more machines in the farm and if your SPJobLockType isn't well configured for your need, you loose much time:

https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.administration.spjoblocktype

 https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.administration.spjoblocktype

这篇关于计时器工作需要很长时间才能完成sharepoint 2010的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！