[
https://issues.apache.org/jira/browse/HAMA-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052497#comment-13052497
]
Steve Loughran commented on HAMA-363:
-------------------------------------
I've been doing some monitoring of HDFS; it's easy to plug in custom stuff in
front of the filesystem, but not so good in the internals.
For HDFS, hama, etc, I'd like to be able to inject monitors into the code (i.e.
a plugin point) once every network connection gets set up, to determine source
and dest (hostname:port) values, plus #of bytes read/written. Just a thought. I
wouldn't put Hama support for this on my priority need, but with a plugin point
here the data can be collected and sampled or streamed to things for
post-execution analysis.
> 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
