[
https://issues.apache.org/jira/browse/TAJO-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
hyoungjunkim updated TAJO-333:
------------------------------
Attachment: tajo-ganglia-02.png
tajo-ganglia-01.png
TAJO-333_2.patch
Jihoon, thanks for your review.
In this patch
- change "runEB" to "executedExecutionBlocksNum"
- add METRICS_PROPERTY_FILENAME variable in TajoConf.ConfVars
- propertyChangeChecker issue In TajoSystemMetrics
ReloadingStrategy of PropertiesConfiguration class has not thread for
checking property file. So configurationChanged method fired when getXXX method
called.
- "localhost" In MetricsConsoleReporter issue
TajoMetricsReporter does not print host and port when hostAndPort valus is
null.
- I removed unnecessary debug code and fixed spell in tajo-metrics.properties
and removed unused imports.
- I think that the main purpose of this issue is making metrics system and
applying to daemon's metrics. So The adding task for query's metrics like the
size of intermediate data which you mentioned is next step.
- Added ganglia reporter
> Add metric system to Tajo
> -------------------------
>
> Key: TAJO-333
> URL: https://issues.apache.org/jira/browse/TAJO-333
> Project: Tajo
> Issue Type: New Feature
> Reporter: Hyunsik Choi
> Assignee: hyoungjunkim
> Labels: metrics
> Fix For: 0.8-incubating
>
> Attachments: TAJO-333.patch, TAJO-333_2.patch, tajo-ganglia-01.png,
> tajo-ganglia-02.png
>
>
> 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)
