Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AAFE2102D3 for ; Thu, 4 Dec 2014 03:16:13 +0000 (UTC) Received: (qmail 41693 invoked by uid 500); 4 Dec 2014 03:16:12 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 41500 invoked by uid 500); 4 Dec 2014 03:16:12 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 41369 invoked by uid 99); 4 Dec 2014 03:16:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Dec 2014 03:16:12 +0000 Date: Thu, 4 Dec 2014 03:16:12 +0000 (UTC) From: "Federico Piccinini (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-12633) Move online configuration script to be a separate class and add support for non-default ports MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Federico Piccinini created HBASE-12633: ------------------------------------------ Summary: Move online configuration script to be a separate class and add support for non-default ports Key: HBASE-12633 URL: https://issues.apache.org/jira/browse/HBASE-12633 Project: HBase Issue Type: Improvement Components: scripts Affects Versions: 0.89-fb Reporter: Federico Piccinini Priority: Trivial Fix For: 1.0.0 The online configuration change script helps us reloading configurations in an online manner. In a majority of the cases, we want to reload configurations on all the servers. In some cases, we reload the config on a single server. Right now we use a script. However, it would be nice to revisit the code and do two things: (1) Move the code to a Java class. This in general will help with error reporting/handling, etc. and would be more convenient. (2) Be able to handle cases where the host name does not use the default port. -- This message was sent by Atlassian JIRA (v6.3.4#6332)