Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Mon, 12 May 2014 00:45:17 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12443902.1261388741330.327130.1399855517174@arcas>
In-Reply-To: <JIRA.12443902.1261388741330@arcas>
References: <JIRA.12443902.1261388741330@arcas>
Subject: [jira] [Resolved] (HBASE-2061) Mobile Cluster Manager
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/HBASE-2061?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Purtell resolved HBASE-2061.
-----------------------------------

    Resolution: Not a Problem

Cool idea but what was I smoking

> Mobile Cluster Manager
> ----------------------
>
>                 Key: HBASE-2061
>                 URL: https://issues.apache.org/jira/browse/HBASE-2061
>             Project: HBase
>          Issue Type: Wish
>            Reporter: Andrew Purtell
>            Priority: Minor
>
> Consider a midlet (for iPhone and Blackberry) that puts up status of HBas=
e, HDFS, and MapReduce services. Extend Stargate for back end support. (Sup=
port active-active failover of Stargate service.) Visualize cluster status =
with a dashboard. Make the summary view fit without needing to scroll. Summ=
arize load with a weather motif. For detail provide a navigable tree view: =
service -> rack -> server -> daemon -> resource. Display metrics and time s=
eries graphs sourced from Ganglia/RRD in the leaves if available, with cont=
rols for selecting metric and time range filtered for the appropriate resou=
rce or aggregate view. For HBase, visualize region deployment and key and q=
uery densities by region; also, load and performance metrics by region. But=
tons for control actions at cluster, server, and daemon scope. Control acti=
ons for MapReduce job tracker. Command line with auto-completion. Support a=
 background mode that maintains a connection open to the cluster and receiv=
es push telemetry. Optimize communication for high latency lossy transport.=
 (Could be based on Avro over compressed SSH tunnelling with suitable frami=
ng and flushing.) If possible the Stargate extension should monitor the tel=
emetry stream and do non-parametric outlier detection (incremental LOF?). (=
The cluster could help with that, look at distributed outlier detection res=
ults in the Sensor Networks literature.) As appropriate alert the device us=
er and provide shortcut(s) on the dashboard to most relevant resource that =
supports control actions.=20
> While travelling in New York I had the "opportunity" to do wizard level c=
luster diagnostics and recovery over ssh on the Blackberry while sitting in=
 Times Square. Let's just say it was inconvenient. So the above is my wish.=
 :-)


--
This message was sent by Atlassian JIRA
(v6.2#6252)