[
https://issues.apache.org/jira/browse/HAMA-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053173#comment-13053173
]
ChiaHung Lin commented on HAMA-363:
-----------------------------------
Hi Steve,
The way by plugin to receive internal state/ statistics can be done through
implementing MetricsSink interface and register sink to the MetricsSystem. The
metrics system will periodically harvests internal state from source, which
implements MetricsSource, putting it to sink. For example, at the moment there
is a JvmMetrics which records java vm related information; therefore, by
registering a sink one can obtain jvm statistics periodically.
This seems to me correspond to the behaviour in use case explained in your
comment. For monitoring network connection, an instance of network
MetricsSource can be added to the metrics system beforehand, and a sink can be
implemented for receiving related statistics such as source and dest value,
etc. But there may have something I miss or I am not aware of due to my limited
knowledge. Any chance you can help point out if something is missing in the
current system?
Thank you for the feedback. It is very important to know actual user scenarios
for improvement.
> Add network condition monitoring function to BSPMaster
> ------------------------------------------------------
>
> Key: HAMA-363
> URL: https://issues.apache.org/jira/browse/HAMA-363
> Project: Hama
> Issue Type: New Feature
> Components: bsp
> Affects Versions: 0.3.0
> Reporter: Edward J. Yoon
> Fix For: 0.4.0
>
> Attachments: HAMA-363.patch, HAMA-363.patch, HAMA-363.patch
>
>
> There's few reason why this issue is important. Basically Master server
> should know the status of cluster:
> * to optimize the network usage
> * to handle network connectivity problems
> * to handle different network conditions
> And, I would like to see some network usage statistics.
> In this issue, we implement only basic function which is collect network
> usage.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
