Hi daniel.ewing,
Not sure I can follow the argument here:
This was confusing to me, as it seems to explain something that is different from a heterogeneous cluster.
I'd consider the situation in the paragraph a form of hetergeneous cluster. The section says
As this is configurable on engine level, you can also work in a mixed setup, when some deployments are shared between all nodes and some are not. You can assign the globally shared process applications to an engine that is not deployment aware and the others to a deployment aware engine, probably both running against the same database. This way, jobs created in the context of the shared process applications will get executed on any cluster node, while the others only get executed on their respective nodes.
As soon as we have process applications that not deployed on all engines, we have a hetergeneous cluster. It would be great, if you could elaborate, I think I am misunderstanding your point.
Lastly, if you find something in the docs that is unclear and you have a good improvement idea (maybe not the case here), feel free to just create pull request with the proposed changed. At the top of every docs page there is a little github button that takes you immediately to the source of the page.
Cheers,
Thorben
Hi daniel.ewing,
Not sure I can follow the argument here:
I'd consider the situation in the paragraph a form of hetergeneous cluster. The section says
As soon as we have process applications that not deployed on all engines, we have a hetergeneous cluster. It would be great, if you could elaborate, I think I am misunderstanding your point.
Lastly, if you find something in the docs that is unclear and you have a good improvement idea (maybe not the case here), feel free to just create pull request with the proposed changed. At the top of every docs page there is a little github button that takes you immediately to the source of the page.
Cheers,
Thorben