User story #3945
closed
Store agent executions history in a 'lightweight' table, to speed up Rudder web interface
Description
Looking for agent executions is very ressource consumming in Rudder for now (ie : opening list nodes page is very very long if you got numerous nodes, be causeit is looking for the latest reports from each node)
If we had a completely separated table only containing executions, this would really ease the process (very few lines compared to millions in rudderSysEvents)
An agent execution consists in:
- The Id of the node executing the agent
- The time when that execution was ran
- If this execution was complete or not
We should have an actor parsing reports, regularly ran(~ every ten seconds, configurable), getting new reports and determine agent executions
Updated by 
Updated by Jonathan CLARKE
Updated by Nicolas PERRON about 11 years ago
- Status changed from 13 to Pending release
Updated by Vincent MEMBRÉ about 11 years ago
- Subject changed from Store agent executions history to Store agent executions history in a 'ligthweight' table, to speed up Rudder
Updated by Vincent MEMBRÉ about 11 years ago
- Subject changed from Store agent executions history in a 'ligthweight' table, to speed up Rudder to Store agent executions history in a 'lightweight' table, to speed up Rudder web interface
Updated by Vincent MEMBRÉ about 11 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.8.0~beta1, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-October/000056.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog28
- Download information: http://www.rudder-project.org/foswiki/Download/