Mailing-List: contact user-help@uima.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@uima.apache.org
MIME-Version: 1.0
In-Reply-To: <56FCF25F.8090005@orkash.com>
References: <56FCF25F.8090005@orkash.com>
Date: Thu, 31 Mar 2016 12:29:13 -0400
Message-ID: 
 <CAGRYgEOxmzGMdj8w9L-KmHLen8FqVVH4_ixq3aqNVHt9Qq3j5A@mail.gmail.com>
Subject: Re: DUCC: Unable to do "Fixed" type of Reservation
From: Eddie Epstein <eaepstein@gmail.com>
To: user@uima.apache.org
Content-Type: multipart/alternative; boundary=001a11c37aba506ac6052f5ac37f

--001a11c37aba506ac6052f5ac37f
Content-Type: text/plain; charset=UTF-8

Hi Reshu,

Reserve type allows users to allocate an unconstrained resource. Because
reserve allocations are not constrained by cgroup containers, in v2.x these
allocations were restricted to be an entire machine.

Fixed type allocations, which are always associated with a specific user
process, have CPU and memory constrained by cgroups, if cgroups are enabled
and properly configured. If DUCC does not recognize cgroup support for a
node it falls back to monitoring memory use and killing processes that
exceed the specified threshold above requested allocation size. CGroup
status for each node is shown on the System->Machines page.

Ubuntu locates the cgroup folder differently from Red Hat and Suse OS. DUCC
v2 does have a property to specify this location, but you have found
another bug, this time hopefully only in the documentation.

The default value for this property is:
ducc.agent.launcher.cgroups.basedir=/cgroup/ducc
To override, put a different entry in
{ducc_runtime}/resource/site.ducc.properties

Regards,
Eddie


On Thu, Mar 31, 2016 at 5:48 AM, reshu.agarwal <reshu.agarwal@orkash.com>
wrote:

> Hi,
>
> In DUCC 1.x, we are able to do fixed reservation of some of the memory of
> Nodes but We are restricted to do "reserve" type of reservation in DUCC
> 2.x. I want to know the reason for the same.
>
> I am using ubuntu for DUCC installation and not be able to configure
> c-groups in it, So, I have tried to manage RAM utilization through FIXED
> reservation in DUCC 1.x. But, Now I have no option.
>
> Hope, you can solve my problem.
>
> Cheers.
>
> Reshu.
>

--001a11c37aba506ac6052f5ac37f--