From yarn-issues-return-142546-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Mon Apr 16 20:16:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id B5203180608 for ; Mon, 16 Apr 2018 20:16:03 +0200 (CEST) Received: (qmail 5449 invoked by uid 500); 16 Apr 2018 18:16:02 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 5437 invoked by uid 99); 16 Apr 2018 18:16:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Apr 2018 18:16:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 2BBFE1802EA for ; Mon, 16 Apr 2018 18:16:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id DntiuAc3JwD6 for ; Mon, 16 Apr 2018 18:16:01 +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 206C85FD11 for ; Mon, 16 Apr 2018 18:16:01 +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 62EDAE03A0 for ; Mon, 16 Apr 2018 18:16:00 +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 10ED0240C6 for ; Mon, 16 Apr 2018 18:16:00 +0000 (UTC) Date: Mon, 16 Apr 2018 18:16:00 +0000 (UTC) From: "Eric Yang (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-8161) ServiceState FLEX should be removed MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16439811#comment-16439811 ] Eric Yang commented on YARN-8161: --------------------------------- [~gsaha] Thank you for filing this issue. The current REST API performs operations such as: {quote} curl -i --negotiate -u : -X PUT -H "Content-Type: application/json" -d@/tmp/flex.json http://eyang-2.openstacklocal:8088/app/v1/services/q1/components/ping {quote} The payload of JSON shows: {quote} { "name" : "ping", "number_of_containers" : 3, "run_privileged_container" : false, "state" : "FLEXING" } {quote} The state is in progressive tense. There is no clear indicator when querying GET status API, whether AM is actually performing the operation, or the state was set by user who issued the operation request. It would be nice to enhance the API to be more responsive by separating user requested operation and state change. For example, the pay load could be: {quote} { "name" : "ping", "number_of_containers" : 3, "run_privileged_container" : false, "state" : "FLEX" } {quote} Application Master code will change to FLEXING when operation is being worked on. GET status API is invoked. {quote} ... { "name" : "ping", "number_of_containers" : 3, "run_privileged_container" : false, "state" : "FLEXING" } ... {quote} When operation is finished, it reaches STABLE state: {quote} ... { "name" : "ping", "number_of_containers" : 3, "run_privileged_container" : false, "state" : "STABLE" } ... {quote} The state transition provides better user feedback between state being triggered, or server is currently working on the operation. The original code was written such that -flex operation is in cli code, which switch to FLEXING when it reaches REST API. For third party developer that does not rely on cli code base, this can be confusing. I think more feedback from the community, can help to decide to simply code base by removing present tense state transition, or adding present tense transition for better user feedback. > ServiceState FLEX should be removed > ----------------------------------- > > Key: YARN-8161 > URL: https://issues.apache.org/jira/browse/YARN-8161 > Project: Hadoop YARN > Issue Type: Sub-task > Components: yarn-native-services > Affects Versions: 3.1.0 > Reporter: Gour Saha > Priority: Major > > ServiceState FLEX is not required to trigger flex up/down of containers and should be removed -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org