[
https://issues.apache.org/jira/browse/TAJO-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
hyoungjunkim updated TAJO-333:
------------------------------
Attachment: TAJO-333.patch
This patch is first patch for tajo’s metric system.
Tajo metric system has two metrics type.
h3. system metric
A system metric which likes daemon’s JVM status, number of worker is emits
metrics data periodically.
A system metric set properties(reporter class, period) with
conf/tajo-metrics.properties file.
In the current patch, A system metrics collects minimal information about
daemon. If you need more information, please comment.
h3. basic metric
The basic metric can be used at any time.
For example, If there is more query runtime statistics data, A query optimizer
generates better query plan.
Every query can has a metrics object and can emit metrics data periodically or
query closing time.
{code}
TajoMetrics tajoMetrics = new TajoMetrics();
tajoMetrics.counter(queryId, “numScanBytes”).inc(scanBytes);
…
tajoMetrics.report(new TajoMetricsReporter() {
public void report(SortedMap<String, Gauge> gauges,
SortedMap<String, Counter> counters,
SortedMap<String, Histogram> histograms,
SortedMap<String, Meter> meters,
SortedMap<String, Timer> timers) {
…
}
});
{code}
> Add metric system to Tajo
> -------------------------
>
> Key: TAJO-333
> URL: https://issues.apache.org/jira/browse/TAJO-333
> Project: Tajo
> Issue Type: Bug
> Reporter: Hyunsik Choi
> Assignee: hyoungjunkim
> Labels: metrics
> Fix For: 0.8-incubating
>
> Attachments: TAJO-333.patch
>
>
> Currently, there is no way to measure and observe Tajo's internal operations.
> As a Hadoop job, Tajo also should measure and record a lot of operational
> works.
> I would like to propose the use of Metrics (http://metrics.codahale.com/). It
> is well known as a stable and efficient metric library.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
