DUCC is designed for multi-user environments, and in particular tries to balance resources fairly quickly across users in a fair-share allocation. The default mechanism used is preemption. To eliminate preemption specify a "non-preemptable" scheduling class for jobs such as "fixed".
Other options that could be of interest include: ducc.rm.initialization.cap This limits allocation to jobs until initialization is successful, limiting the "damage" to other running preemptable jobs if a new job will not even initialize. ducc.rm.expand.by.doubling This limits the rate at which resources are allocated to allow gaining some knowledge about job throughput to avoid over allocating resources. ducc.rm.prediction Used along with doubling to avoid unnecessary allocation. Regards, Eddie On Fri, Apr 20, 2018 at 5:31 AM, priyank sharma <[email protected]> wrote: > Hey! > > I am facing trouble while running one job at a time in ducc. I want that > if one job is running the other one should wait for it to complete and then > start. > My configuration file is attached below. > Please help me with what I am missing. > > -- > Thanks and Regards > Priyank Sharma > >
