Project

General

Profile

Actions
Copy link

Bug #19244

closed

There are 2 policy generation at each start of rudder policy server

Added by Nicolas CHARLES almost 3 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
Performance and scalability
Target version:
6.1.19
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:

Description

One is triggered at every start, and one is caused by 

INFO  scheduled.job - Update in node inventories main information detected: triggering a policy generation

which happens during the current policy generation

it's not problemati, but that annoying

Actions
Copy link
 #1

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.13 to 6.1.14
Actions
Copy link
 #2

Updated by Nicolas CHARLES almost 3 years ago

it also happens with a clear cache

Actions
Copy link
 #3

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions
Copy link
 #8

Updated by François ARMAND about 2 years ago

  • Status changed from New to Resolved

In 7.0, we delay the first generation to after full startup.

Actions
Copy link

Also available in: Atom PDF