Hi Rohit, What is the collection reader running in the job driver doing? Look at the memory use (RSS) value for the job driver on the job details page. If nothing is logged (be sure to check ducc.log file) my guess would be that the JD ran out of RAM in its cgroup and was killed. The JD cgroup size can be increased dynamically for future jobs without DUCC restart by editing ducc.properties (ducc.jd.share.quantum) The default Xmx for JD is specified by ducc.driver.jvm.args.
Eddie On Wed, Jul 18, 2018 at 9:12 AM, Rohit yadav <rohit.ya...@orkash.com> wrote: > Hi, > > I am running a job on DUCC along with CR,AE and CC.But while running Job > Driver ,CPU consumption of JD increases to 600%. > I wanted to know is it normal to have high CPU consumption in Job Driver. > Also after running for 1-2 hours the DUCC stops. > And after i restart the DUCC and check the logs of JD there is nothing > mentioned why DUCC stopped. > Also, my DUCC is running on 3 nodes. > The JD is configured at the head node. > -- > Best, > *Rohit Yadav* >
