Project

General

Profile

Actions

Bug #19351

closed

Semaphore on Nodeinfoservice is not working

Added by Nicolas CHARLES over 1 year ago. Updated over 1 year ago.

Status:
Released
Priority:
N/A
Category:
Performance and scalability
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Regression:

Description

So every request to the NodeInfoService when an update has been done will trigger a full update of cache, causing a queries to pill up and massive slowdown


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #19363: Semaphore in APIAccountRepository,GitArchiverUtils and maybe PolicyServerManagementService are not semaphoringReleasedVincent MEMBRÉActions
Actions #1

Updated by Nicolas CHARLES over 1 year ago

  • Status changed from New to In progress
Actions #2

Updated by Nicolas CHARLES over 1 year ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/3654
Actions #3

Updated by Nicolas CHARLES over 1 year ago

  • Subject changed from queryAndChekNodeId sometimes query for 0 nodes to Semaphore on Nodeinfoservice is not working
  • Description updated (diff)
Actions #4

Updated by Nicolas CHARLES over 1 year ago

  • Related to Bug #19363: Semaphore in APIAccountRepository,GitArchiverUtils and maybe PolicyServerManagementService are not semaphoring added
Actions #5

Updated by Nicolas CHARLES over 1 year ago

  • Status changed from Pending technical review to Pending release
Actions #32

Updated by Vincent MEMBRÉ over 1 year ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.1.14 and 6.2.8 which were released today.

Actions

Also available in: Atom PDF