Bug #26384
openrudder agent update is really slow
Description
The command rudder agent update is really slow - even on the root server it can take several second
It turns out, most of the time spent is on opening the database
3153052 0.000028 newfstatat(6, "", {st_mode=S_IFREG|0600, st_size=0, ...}, AT_EMPTY_PATH) = 0 3153052 0.000113 newfstatat(AT_FDCWD, "/var/rudder/cfengine-community/state/am_policy_hub", 0x7ffd9a740fc0, 0) = -1 ENOENT (No such file or directory) 3153052 0.000147 openat(AT_FDCWD, "/var/rudder/cfengine-community/state/cf_state.lmdb-lock", O_RDWR|O_CREAT|O_CLOEXEC, 0600) = 5 3153052 0.000135 openat(AT_FDCWD, "/var/rudder/cfengine-community/state/cf_state.lmdb", O_RDWR|O_CREAT, 0600) = 7 3153052 0.000163 openat(AT_FDCWD, "/var/rudder/cfengine-community/state/cf_state.lmdb", O_WRONLY|O_DSYNC|O_CLOEXEC) = 8 3153052 0.000090 close(6) = 0
For each file checked, a persistent class is set
Commenting persist_time in the success body in update.cf changes from
# time /var/rudder/cfengine-community/bin/cf-agent -Kf failsafe.cf real 0m7.564s user 0m0.523s sys 0m0.672s
to
# time /var/rudder/cfengine-community/bin/cf-agent -Kf failsafe.cf real 0m0.536s user 0m0.296s sys 0m0.228s
on the root server
We would set a simple class, and define a persistant class based on that once the update is done
Happens on 8.1 and 8.2 at least
Updated by Nicolas CHARLES about 1 month ago
- Severity set to Minor - inconvenience | misleading | easy workaround
- UX impact set to It bothers me each time
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 0 to 44
Updated by Alexis Mousset about 1 month ago
- Status changed from New to In progress
- Assignee set to Alexis Mousset
Updated by Alexis Mousset about 1 month ago
- Status changed from In progress to New
- Assignee deleted (
Alexis Mousset)
Updated by Alexis Mousset about 1 month ago
- Assignee set to Alexis Mousset
- Priority changed from To review to 2
Updated by Vincent MEMBRÉ about 1 month ago
- Target version changed from 8.2.5 to 8.2.6
Updated by François ARMAND about 1 month ago
- Priority changed from 2 to 1 (highest)
Some users are starting to notice it too, so it might be important to try to identify the root cause.
Switching to P1 because it's worrying enought and fall in the "likely complex, difficult bug to correct that needs our attention"
Updated by Alexis Mousset 26 days ago
- Status changed from New to Pending technical review
- Assignee changed from Alexis Mousset to Félix DALLIDET
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1869
Updated by Alexis Mousset 25 days ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-techniques|8fdf53852a3836abb0f0e31c21facd0a969afbbb.
Updated by François ARMAND 12 days ago
- Related to Bug #26553: Red triangle on system policies since agent update class definition change added
Updated by Alexis Mousset 7 days ago
- Status changed from Pending release to New
Reverted, it broke update reports (for policies and shared-files on relays).
Updated by Alexis Mousset 7 days ago
- Assignee changed from Félix DALLIDET to Alexis Mousset
Updated by François ARMAND 5 days ago
- Related to Bug #26597: Relay « Cannot propagate shared files » added