Project

General

Profile

Bug #11937

yum is run at each cf-promises, having a massive perf cost, on redhat-like system

Added by Nicolas CHARLES 5 months ago. Updated 4 months ago.

Status:
Released
Priority:
N/A
Category:
Generic methods
Target version:
Severity:
User visibility:
Effort required:

Description

On redhat like system, at each cf-promises (but also at each cf-server restart), we run the command

LANG=C /usr/bin/yum --setopt=exit_on_lock=True 2>&1 | /bin/grep -q -E '(Command line error: no such option: --setopt|Main config did not have a exit_on_lock attr. before setopt)'

it goes without saying that it has a huge perf cost (0,5 s CPU on a test platform, about a third of total cf-promises run)

we could guard the execution by a simple "agent" class, and have easy gain

Associated revisions

Revision 9ea51b52 (diff)
Added by Nicolas CHARLES 5 months ago

Fixes #11937: yum is run at each cf-promises, having a massive perf cost, on redhat-like system

History

#1 Updated by Nicolas CHARLES 5 months ago

  • Status changed from New to In progress

#2 Updated by Nicolas CHARLES 5 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Alexis MOUSSET
  • Pull Request set to https://github.com/Normation/ncf/pull/675

#3 Updated by Normation Quality Assistant 5 months ago

  • Assignee changed from Alexis MOUSSET to Nicolas CHARLES

#4 Updated by Nicolas CHARLES 5 months ago

  • Status changed from Pending technical review to Pending release

#5 Updated by Vincent MEMBRÉ 4 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.1.10 and 4.2.4 which were released today.

Also available in: Atom PDF