[slurm-dev] Re: "Requested node configuration is not available" when using -c

2014-09-11 Thread jette
You have expressed this problem in a very misleading fashion. Here is a table showing the equivalent commands and options for the most common workload managers (Slurm, LSF, PBS, SGE and LoadLeveler) that should help: http://slurm.schedmd.com/rosetta.html Quoting Michal Zielinski : To b

[slurm-dev] Re: "Requested node configuration is not available" when using -c

2014-09-11 Thread Michal Zielinski
To be honest I'm not sure about what setup was done (ex. MPI in the background), but when I run *bsub -n 50 ./script* on our cluster, I get a single process that has access to a total of 50 cores spread across multiple nodes.Some of these nodes may also contain cores that are allocated to a differe

[slurm-dev] Re: "Requested node configuration is not available" when using -c

2014-09-10 Thread Christopher Samuel
On 11/09/14 10:56, Christopher Samuel wrote: > This is an operating system kernel issue, not a queuing system issue, so > Slurm, LSF or Torque will all have the same issue. To clarify the Linux kernel can support these sorts of systems, but you'll either need extra supporting software or special

[slurm-dev] Re: "Requested node configuration is not available" when using -c

2014-09-10 Thread Christopher Samuel
On 10/09/14 23:17, Michal Zielinski wrote: > I thought this was possible because it's possible using LSF without MPI, > but I guess not. This is an operating system kernel issue, not a queuing system issue, so Slurm, LSF or Torque will all have the same issue. There are ways to build SMP system

[slurm-dev] Re: "Requested node configuration is not available" when using -c

2014-09-10 Thread Carlos Fenoy
d will be inferred from CPUS, default is 1) and >>> CoresPerSocket (default is 1) >>> >>> So at this point the slurm.conf has a default configuration of 1 core >>> per node. >>> >>> Phil Eckert >>> LLNL >>> >>> From: Mich

[slurm-dev] Re: "Requested node configuration is not available" when using -c

2014-09-10 Thread Michal Zielinski
t is 1) and >> CoresPerSocket (default is 1) >> >> So at this point the slurm.conf has a default configuration of 1 core >> per node. >> >> Phil Eckert >> LLNL >> >> From: Michal Zielinski >> Reply-To: slurm-dev >> Date: Tuesday,

[slurm-dev] Re: "Requested node configuration is not available" when using -c

2014-09-09 Thread Martin Perry
-dev] Re: "Requested node configuration is not available" when using -c Josh, I believe that -n sets the number of tasks. I only want a single task, as when a single process uses multiple cores. srun -n 2 hostname returns linux-slurm2 linux-slurm3 which is definitely not what I want. Th

[slurm-dev] Re: "Requested node configuration is not available" when using -c

2014-09-09 Thread Chrysovalantis Paschoulas
r node. Phil Eckert LLNL From: Michal Zielinski mailto:michal.zielin...@uconn.edu>> Reply-To: slurm-dev mailto:slurm-dev@schedmd.com>> Date: Tuesday, September 9, 2014 at 6:35 AM To: slurm-dev mailto:slurm-dev@schedmd.com>> Subject: [slurm-dev] Re: "Requested node configu

[slurm-dev] Re: "Requested node configuration is not available" when using -c

2014-09-09 Thread Michal Zielinski
-To: slurm-dev > Date: Tuesday, September 9, 2014 at 6:35 AM > To: slurm-dev > Subject: [slurm-dev] Re: "Requested node configuration is not available" > when using -c > > Josh, > > I believe that *-n *sets the number of tasks. I only want a single task,

[slurm-dev] Re: "Requested node configuration is not available" when using -c

2014-09-09 Thread Josh McSavaney
Hey Mike, I had assumed that this is what you were trying to accomplish. Seeing as your are trying to create a single task with multiple cores, you must first define a node that has enough cores. As far as SLURM knows, you currently have 1 CPU core per node (as Phil stated). SLURM is refusing to

[slurm-dev] Re: "Requested node configuration is not available" when using -c

2014-09-09 Thread Eckert, Phil
mailto:michal.zielin...@uconn.edu>> Reply-To: slurm-dev mailto:slurm-dev@schedmd.com>> Date: Tuesday, September 9, 2014 at 6:35 AM To: slurm-dev mailto:slurm-dev@schedmd.com>> Subject: [slurm-dev] Re: "Requested node configuration is not available" when using -c Josh,

[slurm-dev] Re: "Requested node configuration is not available" when using -c

2014-09-09 Thread Michal Zielinski
Josh, I believe that *-n *sets the number of tasks. I only want a single task, as when a single process uses multiple cores. *srun -n 2 hostname* returns linux-slurm2 linux-slurm3 which is definitely not what I want. Thanks, Mike On Mon, Sep 8, 2014 at 8:07 PM, Josh McSavaney wrote: > I be

[slurm-dev] Re: "Requested node configuration is not available" when using -c

2014-09-09 Thread Michal Zielinski
Attached is the output. Thanks, Mike On Mon, Sep 8, 2014 at 7:42 PM, Christopher Samuel wrote: > > On 09/09/14 07:26, Michal Zielinski wrote: > > I have a small test cluster (node[1-4]) running slurm 14.03.0 setup with >> CR_CPU and no usage restrictions. Each node has just 1 CPU. >> > [...] >

[slurm-dev] Re: "Requested node configuration is not available" when using -c

2014-09-08 Thread Josh McSavaney
I believe your slurm.conf is defining 4 nodes with a single logical processor each. You are then trying to allocate two CPUs on a single node with srun, which (according to your slurm.conf) you do not have. You may want to consider `srun -n 2 hostname` and see where that lands you. Regards, Josh

[slurm-dev] Re: "Requested node configuration is not available" when using -c

2014-09-08 Thread Christopher Samuel
On 09/09/14 07:26, Michal Zielinski wrote: I have a small test cluster (node[1-4]) running slurm 14.03.0 setup with CR_CPU and no usage restrictions. Each node has just 1 CPU. [...] But, *srun -c 2 hostname* does not work, and it returns the above error. I have no idea why I can't dedicate 2