Project

General

Profile

Actions

Bug #4841

closed

Job Scheduler Technique should not use ifelapsed to avoid running several time same job

Added by Nicolas CHARLES almost 10 years ago. Updated almost 10 years ago.

Status:
Released
Priority:
N/A
Category:
Techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Since in #4769 we are going to remove cf_lock.tcdb files, we need to make sure that we don't use ifelapsed to avoid running several time the same job (if we run manually the agent after killing the lock base, in the right ( minutes interval)
There is nearly no impact, as the probability of this hitting a user is nearly null (have to run manually the agent, in the right interval, right after a moment where lock is killed)


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #4769: rudder-agent may be stucked by tokyo cabinet database bloatingReleasedJonathan CLARKE2014-04-23Actions
Actions #1

Updated by Nicolas CHARLES almost 10 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Jonathan CLARKE
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/362
Actions #2

Updated by Nicolas CHARLES almost 10 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Applied in changeset policy-templates:commit:36a7c3bc16d7d7ed9818256a31451d147dc573db.

Actions #3

Updated by Nicolas CHARLES almost 10 years ago

Applied in changeset policy-templates:commit:4c721ba20758b85aaeb6b46546208492155b6434.

Actions #4

Updated by Vincent MEMBRÉ almost 10 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.9.5 (announcement , changelog) and 2.10.1 (announcement , changelog), which were released today.

Actions

Also available in: Atom PDF