1) There's no way to configure minimum number of tasks per groom server at this moment. Let's assume that there're 20 nodes (groom servers) and bsp.tasks.maximum is 5. So total task slots are 100. If my job requires only 10 tasks, the tasks can be executed on from 2 to 10 nodes.

Thanks, Edward. I have few specific questions for my application. Myapplication spawns 21 bsp tasks based on the input. But internally I amassigning only first few Bsp peers, say first 4 (based on peer id) , to dothe work. So the rest of peers become useless after few supersteps. Myconcern is that, these "active" bsp peers should not end up in the samemachine, to avoid overloading a single machine.

One way to solve it would be to choose active peer ids in gap of maximumpeers a machine can run. For example, if the maximum tasks per machine is3, I would choose 0, 3, 6 and 9 as active peers. But is it gauranteed to berun in different machines? This solution also assumes the number of bsppeers currently running to be greater than or equal to 10, which is greaterthan previously assumed value (4).So, is there any way I can see the bsp peer to groom server mapping?

If I have to generalize my problem statement, it would be like this: Givenn tasks, out of which m tasks has to selected (m < n) such that those tasksuses the resources optimally (in terms of parallelism, load balancing etc.)On 17-Jan-2017 2:42 PM, "Edward J. Yoon" <[EMAIL PROTECTED]> wrote:

Hi,

1) There's no way to configure minimum number of tasks per groom server atthis moment. Let's assume that there're 20 nodes (groom servers) andbsp.tasks.maximum is 5. So total task slots are 100. If my job requires only10 tasks, the tasks can be executed on from 2 to 10 nodes.

I don't know if I was understood correctly. You mean, tasks that has heavy load should be scheduled in different machines. Right? It sounds quite interesting topic. In that case, the load of each task should be predictable, and new scheduler is needed, like task priority-based load balancing scheduler.

We don't support that feature at the moment. If you want to try to implement and contribute to the project, Please let us know. We'll help you.

Best Regards, Edward J. Yoon

Edward J. Yoon 2017-01-18, 08:41

NEW: Monitor These Apps!

Apache Lucene, Apache Solr and all other Apache Software Foundation project and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext