Project

General

Profile

Bug #15073

Add switch to disable some compliance and change tracking features for performance

Added by François ARMAND 2 months ago. Updated about 2 months ago.

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

Description

There is several features that we want to be able to tweak (if possible without restarting rudder) that have a big influence on loaded environement:

- changes. This is highly stressfull for database, and even if Rudder can not work without them, we would like to be able to disable changes to help analyse perf problems,
- dynamic group computation at the begining of generation (idem than for changes)
- wrtiing node compliance level: this can be stressfull and it is not used but if you have the reporting plugins
- writing node compliance: this one should be off by default, there is 0 reason to keep it in Rudder 5.0 as it's not used anymore, not even by the reporting plugin.

All of these feature will be properties that will be switchable via Settings API, but they won't be exposed in the settings web page as they should not be changed.

The can be changed with:

# use 'false' or 'true' 

# compute dynamic group at start of policy generation
curl -k -H "X-API-Token: xxx"  -X POST 'https://.../rudder/api/latest/settings/rudder_generation_compute_dyngroups' -d "value=false" 

# compute "changes" (globaly)
curl -k -H "X-API-Token: xxx"  -X POST 'https://.../rudder/api/latest/settings/rudder_compute_changes' -d "value=false" 

# save compliance levels in database
curl -k -H "X-API-Token: xxx"  -X POST 'https://.../rudder/api/latest/settings/rudder_save_db_compliance_levels' -d "value=false" 

# save detailled compliance reports in database (should be set to false)
curl -k -H "X-API-Token: xxx"  -X POST 'https://.../rudder/api/latest/settings/rudder_save_db_compliance_details' -d "value=false" 

Associated revisions

Revision 3d6382d2 (diff)
Added by François ARMAND 2 months ago

Fixes #15073: Add switch to disable some feature for performance

Revision aaa1d104
Added by Nicolas CHARLES 2 months ago

Merge pull request #2261 from fanf/bug_15073/add_switch_to_disable_some_feature_for_performance

Fixes #15073: Add switch to disable some feature for performance

History

#1

Updated by François ARMAND 2 months ago

  • Status changed from New to In progress
#2

Updated by François ARMAND 2 months ago

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

Updated by François ARMAND 2 months ago

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

Updated by Alexis MOUSSET about 2 months ago

  • Subject changed from Add switch to disable some feature for performance to Add switch to disable some compliance and change tracking features for performance
#10

Updated by Vincent MEMBRÉ about 2 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.12 which was released today.

Also available in: Atom PDF