Return-Path: X-Original-To: apmail-ambari-user-archive@www.apache.org Delivered-To: apmail-ambari-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9F7341908A for ; Mon, 7 Mar 2016 21:58:32 +0000 (UTC) Received: (qmail 76260 invoked by uid 500); 7 Mar 2016 21:58:27 -0000 Delivered-To: apmail-ambari-user-archive@ambari.apache.org Received: (qmail 76171 invoked by uid 500); 7 Mar 2016 21:58:27 -0000 Mailing-List: contact user-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ambari.apache.org Delivered-To: mailing list user@ambari.apache.org Received: (qmail 76161 invoked by uid 99); 7 Mar 2016 21:58:27 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Mar 2016 21:58:27 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id AE5A11A02AC for ; Mon, 7 Mar 2016 21:58:26 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id G1OepOgBly-R for ; Mon, 7 Mar 2016 21:58:25 +0000 (UTC) Received: from mail-oi0-f41.google.com (mail-oi0-f41.google.com [209.85.218.41]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 9BDDF5FB00 for ; Mon, 7 Mar 2016 21:58:25 +0000 (UTC) Received: by mail-oi0-f41.google.com with SMTP id d205so89636939oia.0 for ; Mon, 07 Mar 2016 13:58:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=kw81d3WtmGQS7p/V9jh567Xoz8FOAoiG/0FOV/7r89c=; b=f7Rac0Y1d9D1vremkAXBeWpu5NnjchAj5KQ7gWGI3S7g7OzKkhNDXOfdOlp1CKUgYr d0VGT1ElZGEjTiPZRhruYbeqAlK3luDLRKf9CCsudMC8I+DuNxhHXQx+Lo2dMTnRqTW5 E3x/cphVZrEaY/f4B6yDUeYykwoyCYpZ2kmvYkkUKBoknU4cbanRPHNiA05hC3W3lFLq VLnNRL/7mDszm691xpClkn488yAUk+YVueM+yJaSav3eU8tHNG6Z/AB6uRseN15f0BJN dtS+ZInhSTqjaD4APdYUtB6zScyEyY4tb5shPYNznloAa6yffSK7S9GkpGByye1HSSQb GPdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=kw81d3WtmGQS7p/V9jh567Xoz8FOAoiG/0FOV/7r89c=; b=g33tXNBE2RKO0k3PTatPMSbnLezlutidwEhczZkgC87RxL6V692WzWY7xP19IvMd1N MYFHY1lG9HJjRX2iYRHgyCYq1tvzyoGLqtgRmgN8v1zNYbU0vxtdgSUr7BD+VnUEZ6ml veuHq/D13NhXq8u+tvK5GDz87un97rRb7sfWvHBrWWAeT3HFW2Krg5xdFvJZKVqHjZuG +WXomVqZ1ccjMBkgf/sBj9HItpokLBGd9iV5RWhduAiDFLOtLF3v7YZsfRpcmdJP17r5 qQhjTfPIOUwDvcIM6w2LrtpUpsT/LdATibscGPEeTPreokLhNLg80+ML6KkOWfxKcTNv R7Ng== X-Gm-Message-State: AD7BkJKjkkJfs5js+nKHVmpSHkfL8N3xmjuuk0/L22L1vi6JiH9S2ovAjanSOidwjxQ2CVWA3gOQn+5HhYDkRw== X-Received: by 10.202.49.12 with SMTP id x12mr15378803oix.106.1457387899606; Mon, 07 Mar 2016 13:58:19 -0800 (PST) MIME-Version: 1.0 Received: by 10.60.246.103 with HTTP; Mon, 7 Mar 2016 13:57:40 -0800 (PST) From: rammohan ganapavarapu Date: Mon, 7 Mar 2016 13:57:40 -0800 Message-ID: Subject: Ambari:2.2.0 resources unavailable issue To: user@ambari.apache.org Content-Type: multipart/alternative; boundary=001a113cd6980e5ced052d7c90a8 --001a113cd6980e5ced052d7c90a8 Content-Type: text/plain; charset=UTF-8 Hi, I have a hadoop cluster with ambari2.2.0, when i submit a oozie workflow, job is failing with resources unavailable, also i observed that oozie thread count is high. Where as same workflow is running fine on the cluster with ambari2.1, any config changes or tuning that i have to worry in 2.2.0 version? Threads: Thread Count=1008 Peak Thread Count=1008 Total Started Threads=17237 Deamon Threads=986 Ram --001a113cd6980e5ced052d7c90a8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

I have a hadoop cluster with am= bari2.2.0, when i submit a oozie workflow, job is failing with resources un= available, also i observed that oozie thread count is high. Where as same w= orkflow is running fine on the cluster with ambari2.1, any config changes o= r tuning that i have to worry in 2.2.0 version?


Threads:= =C2=A0
=C2=A0=C2=A0=C2=A0=C2=A0 Thread Count= =3D1008=C2=A0=C2=A0Peak Thread Count=3D1008=C2=A0=C2=A0Total Started Thread= s=3D17237=C2=A0=C2=A0Deamon Threads=3D986


Ram
 --001a113cd6980e5ced052d7c90a8--