Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 597DD200C2F for ; Mon, 6 Mar 2017 22:25:39 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 58132160B81; Mon, 6 Mar 2017 21:25:39 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A3621160B66 for ; Mon, 6 Mar 2017 22:25:38 +0100 (CET) Received: (qmail 98890 invoked by uid 500); 6 Mar 2017 21:25:37 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 98881 invoked by uid 99); 6 Mar 2017 21:25:37 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Mar 2017 21:25:37 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 79939C05B0 for ; Mon, 6 Mar 2017 21:25:37 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.651 X-Spam-Level: X-Spam-Status: No, score=0.651 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id KAp1QkkLmZU6 for ; Mon, 6 Mar 2017 21:25:36 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 9D7AA5F36B for ; Mon, 6 Mar 2017 21:25:36 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id AD94CE08DE for ; Mon, 6 Mar 2017 21:25:33 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1246524174 for ; Mon, 6 Mar 2017 21:25:33 +0000 (UTC) Date: Mon, 6 Mar 2017 21:25:33 +0000 (UTC) From: "Anita Gnanamalar Jebaraj (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-20333) Value for "User Limit Factor" should be float instead of integer in YARN Queue Manager. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 06 Mar 2017 21:25:39 -0000 Anita Gnanamalar Jebaraj created AMBARI-20333: ------------------------------------------------- Summary: Value for "User Limit Factor" should be float instead of integer in YARN Queue Manager. Key: AMBARI-20333 URL: https://issues.apache.org/jira/browse/AMBARI-20333 Project: Ambari Issue Type: Bug Affects Versions: trunk Reporter: Anita Gnanamalar Jebaraj Assignee: Anita Gnanamalar Jebaraj Priority: Minor Fix For: trunk According to yarn documentation, "yarn.scheduler.capacity..user-limit-factor" should be a float: https://hadoop.apache.org/docs/r2.4.1/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html Hence the user should be allowed to enter decimal values for 'User limit factor' -- This message was sent by Atlassian JIRA (v6.3.15#6346)