Architecture #2630
closed
Rudder Webapp and Rudder Inventory should be two different application
Description
The problem here is that if only one of the two is down, we have to restart Jetty for both.
And typically, if it's Rudder webapp that is down, and that Jetty restart in the middle of an inventory processing, then we are doomed (the inventory will be partially processed).
Perhaps we should have two jetty, with only one application for each of them.
Updated by François ARMAND over 12 years ago
- Target version changed from 50 to 48
Updated by Jonathan CLARKE over 12 years ago
- Target version changed from 48 to Ideas (not version specific)
François ARMAND wrote:
The problem here is that if only one of the two is down, we have to restart Jetty for both.
And typically, if it's Rudder webapp that is down, and that Jetty restart in the middle of an inventory processing, then we are doomed (the inventory will be partially processed).
This is a manifestation of #1721.
Perhaps we should have two jetty, with only one application for each of them.
This also seems related to #1974.
Retargeting from 2.6 to general ideas - the 2.6 roadmap has not been decided on yet.
Updated by Jonathan CLARKE over 8 years ago
- Related to User story #7291: Exit sending inventory to rudder-webapp if the queue is full added
Updated by François ARMAND over 4 years ago
- Status changed from New to Resolved
We went in the opposite direction in rudder 6.0. We merged both since their functionnal perimeter was more and more linked, to the point it didn't make any sense to have too app.
If we had to split now, it would perhaps be around policy generation, which is a totally orthogonal process that policy definition and compliance aggregation.