Actions
Bug #14342
closedAgent connection cache does not work, and does not improve performance as expected
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Small
Priority:
66
Name check:
Fix check:
Regression:
Description
Feb 19 12:48:26 nrm-vir-rudder-01 cf-serverd[852]: CFEngine(server) rudder 192.168.190.9> Accepting connection Feb 19 12:48:26 nrm-vir-rudder-01 cf-serverd[852]: rudder info: 192.168.190.9> Closing connection, terminating thread Feb 19 12:48:26 nrm-vir-rudder-01 cf-serverd[852]: CFEngine(server) rudder 192.168.190.9> Closing connection, terminating thread Feb 19 12:48:27 nrm-vir-rudder-01 cf-serverd[852]: rudder info: 192.168.190.9> Accepting connection Feb 19 12:48:27 nrm-vir-rudder-01 cf-serverd[852]: CFEngine(server) rudder 192.168.190.9> Accepting connection Feb 19 12:48:27 nrm-vir-rudder-01 cf-serverd[852]: rudder info: 192.168.190.9> Closing connection, terminating thread Feb 19 12:48:27 nrm-vir-rudder-01 cf-serverd[852]: CFEngine(server) rudder 192.168.190.9> Closing connection, terminating thread Feb 19 12:48:28 nrm-vir-rudder-01 cf-serverd[852]: rudder info: 192.168.190.9> Accepting connection Feb 19 12:48:28 nrm-vir-rudder-01 cf-serverd[852]: CFEngine(server) rudder 192.168.190.9> Accepting connection Feb 19 12:48:28 nrm-vir-rudder-01 cf-serverd[852]: rudder info: 192.168.190.9> Closing connection, terminating thread Feb 19 12:48:28 nrm-vir-rudder-01 cf-serverd[852]: CFEngine(server) rudder 192.168.190.9> Closing connection, terminating thread Feb 19 12:48:28 nrm-vir-rudder-01 cf-serverd[852]: rudder info: 192.168.190.9> Accepting connection Feb 19 12:48:28 nrm-vir-rudder-01 cf-serverd[852]: CFEngine(server) rudder 192.168.190.9> Accepting connection Feb 19 12:48:28 nrm-vir-rudder-01 cf-serverd[852]: rudder info: 192.168.190.9> Closing connection, terminating thread Feb 19 12:48:28 nrm-vir-rudder-01 cf-serverd[852]: CFEngine(server) rudder 192.168.190.9> Closing connection, terminating thread Feb 19 12:48:28 nrm-vir-rudder-01 cf-serverd[852]: rudder info: 192.168.190.9> Accepting connection Feb 19 12:48:28 nrm-vir-rudder-01 cf-serverd[852]: CFEngine(server) rudder 192.168.190.9> Accepting connection Feb 19 12:48:29 nrm-vir-rudder-01 cf-serverd[852]: rudder info: 192.168.190.9> Closing connection, terminating thread Feb 19 12:48:29 nrm-vir-rudder-01 cf-serverd[852]: CFEngine(server) rudder 192.168.190.9> Closing connection, terminating thread Feb 19 12:48:30 nrm-vir-rudder-01 cf-serverd[852]: rudder info: 192.168.190.9> Accepting connection Feb 19 12:48:30 nrm-vir-rudder-01 cf-serverd[852]: CFEngine(server) rudder 192.168.190.9> Accepting connection Feb 19 12:48:30 nrm-vir-rudder-01 cf-serverd[852]: rudder info: 192.168.190.9> Closing connection, terminating thread Feb 19 12:48:30 nrm-vir-rudder-01 cf-serverd[852]: CFEngine(server) rudder 192.168.190.9> Closing connection, terminating thread Feb 19 12:48:30 nrm-vir-rudder-01 cf-serverd[852]: rudder info: 192.168.190.9> Accepting connection Feb 19 12:48:30 nrm-vir-rudder-01 cf-serverd[852]: CFEngine(server) rudder 192.168.190.9> Accepting connection Feb 19 12:48:30 nrm-vir-rudder-01 cf-serverd[852]: rudder info: 192.168.190.9> Closing connection, terminating thread Feb 19 12:48:30 nrm-vir-rudder-01 cf-serverd[852]: CFEngine(server) rudder 192.168.190.9> Closing connection, terminating thread Feb 19 12:48:30 nrm-vir-rudder-01 cf-serverd[852]: rudder info: 192.168.190.9> Accepting connection Feb 19 12:48:30 nrm-vir-rudder-01 cf-serverd[852]: CFEngine(server) rudder 192.168.190.9> Accepting connection Feb 19 12:48:30 nrm-vir-rudder-01 cf-serverd[852]: rudder info: 192.168.190.9> Closing connection, terminating thread Feb 19 12:48:30 nrm-vir-rudder-01 cf-serverd[852]: CFEngine(server) rudder 192.168.190.9> Closing connection, terminating thread Feb 19 12:48:52 nrm-vir-rudder-01 cf-serverd[852]: rudder info: 192.168.90.250> Accepting connection
It should probably not behave like this.
Seen in 5.0.6.
Updated by Alexis Mousset almost 6 years ago
- Subject changed from Agent make a lot of different connections to Connection cache does not work accross bundles
Updated by Alexis Mousset almost 6 years ago
- Assignee set to Alexis Mousset
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Effort required set to Small
- Priority changed from 0 to 67
Updated by Alexis Mousset almost 6 years ago
- Target version changed from 5.0.7 to 4.3.10
Updated by Alexis Mousset almost 6 years ago
- Status changed from New to In progress
Updated by Alexis Mousset almost 6 years ago
Updated by François ARMAND almost 6 years ago
- Target version changed from 4.3.10 to 4.3.11
Updated by Alexis Mousset almost 6 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-packages/pull/1813
Updated by Alexis Mousset almost 6 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-packages|729cb93ba438a210a2ee807062d14f14ee92b53e.
Updated by Vincent MEMBRÉ over 5 years ago
- Subject changed from Connection cache does not work accross bundles to Agent connection cache does not work, and does not improve performance accordingly
- Priority changed from 67 to 66
Updated by Vincent MEMBRÉ over 5 years ago
- Subject changed from Agent connection cache does not work, and does not improve performance accordingly to Agent connection cache does not work, and does not improve performance as expected
Updated by Vincent MEMBRÉ over 5 years ago
This bug has been fixed in Rudder 4.3.11 and 5.0.9 which were released today.
Updated by Vincent MEMBRÉ over 5 years ago
- Status changed from Pending release to Released
Actions