Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BF311112ED for ; Fri, 18 Jul 2014 21:00:17 +0000 (UTC) Received: (qmail 76199 invoked by uid 500); 18 Jul 2014 21:00:15 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 76028 invoked by uid 500); 18 Jul 2014 21:00:15 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 75704 invoked by uid 99); 18 Jul 2014 21:00:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Jul 2014 21:00:15 +0000 Date: Fri, 18 Jul 2014 21:00:15 +0000 (UTC) From: "Allen Wittenauer (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (HADOOP-3969) Provide Mechanism to optionally expose public org.apache.hadoop.util.Services APIs 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/HADOOP-3969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-3969. -------------------------------------- Resolution: Incomplete Having REST interfaces for everything would be great, but this JIRA isn't the place to do it at this point. > Provide Mechanism to optionally expose public org.apache.hadoop.util.Services APIs > ----------------------------------------------------------------------------------- > > Key: HADOOP-3969 > URL: https://issues.apache.org/jira/browse/HADOOP-3969 > Project: Hadoop Common > Issue Type: New Feature > Reporter: Pete Wyckoff > > Enhance manageability of Hadoop Services by providing Jute, Thrift, REST, ... APIs to select methods in the Service class (or potentially others). > This will allow external tools written in a myriad of languages to query the state of Hadoop Servers and/or interact with them. > This can be encapsulated in the Service class by defining a very simple interface and then optionally instantiating such an implementation provided in the Configuration. > Some methods to be implemented include all the public methods in Service: > {code} > ping() > isRunning() > terminate() > getServiceState() > verifyServiceState() > isTerminated(), > {code} > INTERFACE: > {code} > package org.apache.hadoop.util; > public interface ExposeServiceAPIs { > /** > * @param service - the service whose APIs are to be exposed > * @param serviceName - a symbolic name for the service > * @param configuration - the hadoop configuration object > **/ > public void initialize(Service service, String serviceName, Configuration conf) throws IOException, > public boolean start(); > public boolean stop(); > } ; > {code} > Two straightforward implementations of this would be: > 1. Servlet that exposes the APIs via REST > 2. Thrift DDL of the service APIs and an implementation in Java + bindings in C++, Java, Perl, Python, Ruby, PHP -- This message was sent by Atlassian JIRA (v6.2#6252)