Re: Algorithm for assigning Executor to Workers?

Perhaps we can consider a new feature where a task label can be used instead of the task id. On Wednesday, May 11, 2016 1:11 AM, Vincent Wang wrote: You can add a configuration when submitting the application, the format is: gearpump {   streaming {     localities {       app1: {   

Re: Algorithm for assigning Executor to Workers?

Huafeng, Manu - thank you for quick response. As for Task id, I agree it's not ideal :) Let me read the document to get better understanding of the matter. Karol śr., 11.05.2016 o 10:19 użytkownik Manu Zhang napisał: > Hi Karol, > > Weihua has previously written up this nice doc IoT features m

Re: Algorithm for assigning Executor to Workers?

Hi Karol, Weihua has previously written up this nice doc IoT features map with Gearpump . You may find more details about how Gearpump can work in the environment of cluster and edge devices and the g

Re: Algorithm for assigning Executor to Workers?

You can add a configuration when submitting the application, the format is: gearpump { streaming { localities { app1: {//This is the application name to be submitted workerId: [//The worker id where to launch Task0_0 and Task0_1 TaskId(0,0), TaskId(0,1

Algorithm for assigning Executor to Workers?

What are the criteria that decide which Executor/Tasks goes to which Workers right now? I am considering the following scenario. Let's assume that we have a cluster with some "specialized" nodes (for example a worker on IoT device that is responsible for controlling some actuators, dedicated work