Project

General

Custom queries

Profile

Actions

Bug #16256

closed

Deadlock on compliance computing

Added by Nicolas CHARLES over 5 years ago. Updated over 5 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Compliance & node report
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:

Description

I generated policies, accepted nodes and the same time, and went to home page several time
after a while, compliance didn't show up...

running jstack show that a lot of thread are BLOCKED (see attachement)


Files

thread_dump (212 KB) thread_dump Nicolas CHARLES, 2019-11-22 23:48
API_casse (497 KB) API_casse Nicolas CHARLES, 2019-11-25 11:08

Related issues 1 (0 open1 closed)

Related to Rudder - Bug #16200: Missing timing info in compliance computation logsReleasedFrançois ARMANDActions
#2

Updated by Nicolas CHARLES over 5 years ago

#3

Updated by Nicolas CHARLES over 5 years ago

  • Related to Bug #16200: Missing timing info in compliance computation logs added
#4

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
#5

Updated by Nicolas CHARLES over 5 years 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/2632
#7

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from Pending technical review to Pending release
#8

Updated by Nicolas CHARLES over 5 years ago

  • Fix check changed from To do to Checked
#9

Updated by Alexis Mousset over 5 years ago

  • Subject changed from Deadlock on compliance on Rudder 5.0 to Deadlock on compliance computing
  • Name check changed from To do to Reviewed
#10

Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from Pending release to Released
Actions

Also available in: Atom PDF