[
https://issues.apache.org/jira/browse/HAMA-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13221113#comment-13221113
]
Suraj Menon commented on HAMA-498:
----------------------------------
First of all sorry I couldn't look into these matters yet; got a little busy
with work. Good news is that Friday is here. I would be uploading the changes
for 498 and 445 soon.I think most of the suggested changes were comparatively
minor and test related. It is better that I don't slow you down on your work.
I forgot to mention in the previous posts that I had fixed the problem of open
port 40000 by not sublclassing from HamaTestCase and subclassing from TestCase
instead. I want to make sure if that what you saw in netstat is a side-effect
of HAMA-498 test cases. I am not starting a BSPMaster instance(usually bound on
the port) for the tests. This is the only part of changes I foresee would take
some time. Let me use the time difference between Berlin and Washington DC
before I get back to you tomorrow. ;)
> BSPTask should periodically ping its parent.
> --------------------------------------------
>
> Key: HAMA-498
> URL: https://issues.apache.org/jira/browse/HAMA-498
> Project: Hama
> Issue Type: Sub-task
> Components: bsp
> Affects Versions: 0.4.0
> Reporter: Edward J. Yoon
> Assignee: Suraj Menon
> Labels: newbie
> Fix For: 0.5.0
>
> Attachments: HAMA-498.patch
>
>
> As described in http://wiki.apache.org/hama/GroomServerFaultTolerance
> BSPTask should periodically ping its parent 'GroomServer' for their health
> status.
> 1. If Tasks are unable to ping their parent 'GroomServer', it should be
> killed themselves.
> 2. And, if GroomServer does not receive ping from the childs, GroomServer
> should check whether that child is running.
> You don't need to implement recovery logic in this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira