locked
One-to-one Task to Node mapping RRS feed

  • Question

  • How can we realize the following job scheduling problem:
    Maybe with own PowerShell scripting.

    We have jobs  of several application and every job has  several thousand of tasks.
    The task itself runs very short (10 sec).
    Now we have the limitation that every task of an application can run only once on a node.
    The mapping is also a 1-to-1 task to node of every application

    Job1 of App1                      
     |-------- Task1  --> Node 1 
     |-------- Task2  --> Node 2
     +-------- Task3  --> Node 3

    Job<n> of App2                      
     |-------- Task1  --> Node 3
     |-------- Task2  --> Node 2
     |-------  Task3  --> Node 1
     +-------  Task4  --> Wait until a node is free

    Friday, April 20, 2012 7:46 AM

All replies

  • Hi,

    Please take a look at this http://technet.microsoft.com/en-us/library/cc972879(v=ws.10).aspx

    You need to specify "NumNodes 1" for each task in your job.

    Michael

    Monday, April 30, 2012 4:59 PM
  • Hello Michael,

    thank you for your answer. We had tested what you are suggest before we made this entry in the forum. The problem is, when we use the "NumNodes 1" parameter, only one task from one job can run on the node.We want to have that only one task from each job can run simulatious on one node.

    For example if we have 4 jobs with 10 tasks each on every node should run 1 task from job 1, 1 task from job 2, ...

    Best regards
    Steffen

    Friday, June 1, 2012 7:23 AM
  • Hi Steffen,

    I don't know if I quite get that, did you try to set the scheduler mode to 'balanced'?

    Michael

    Friday, June 1, 2012 5:13 PM
  • How about /nodegroup: /numcores: together

    Task1 (App1,App2,App3 ...) job submit /nodegroup:Node1 /numcores:1-1

    Task2 (App1,App2,App3 ...) job submit /nodegroup:Node2 /numcores:1-1

    etc...


    Daniel Drypczewski

    Thursday, September 27, 2012 3:39 AM