Hi Luqman, Is there a specific reason why you want to keep the data nodes separate from the compute nodes? As you say this beats the point of collocation. You should use the data nodes for compute and ensure you have a way to monitor and kill spurious tasks that may be executed on the grid.
C. > On 13 Nov 2017, at 11:50, luqmanahmad <luqmanah...@gmail.com> wrote: > > Hi there, > > Just trying to clarify few bits in my head around data nodes and compute > nodes. > > Let's say we have 10 data nodes which are solely storing the data using > affinity collocation and we have 10 compute nodes as well for computing > different tasks on the cluster. > > Now we know that if we want to perform some operation on the data and we > know where it resides we can use the affinity API to perform some operation > on it which is indeed much better as there would be no data movement across > the node which makes sense as well. But then on the other side, we have got > compute nodes as well which are just sitting idle. Although we have got the > luxury of using distributed closures then wouldn't it be an overhead of > carrying all the data to a compute node to perform and then sending the data > back. > > Just trying to find a use case where the separate group of the cluster could > be useful. For example data-node, compute-node etc. If anyone can clear this > would be much appreciated. > > Thanks, > Luqman > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
