[
https://issues.apache.org/jira/browse/MAPREDUCE-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281561#comment-13281561
]
Nikhil S. Ketkar commented on MAPREDUCE-3315:
---------------------------------------------
Sharad based on your comment:
"MWProtocol: Would be better to have a heartbeat kind of interface between
worker and master via which worker sends the status reports and results of
completed workunits as HeartbeatRequest and gets more WorkUnits and
instructions as HeartbeatResponse. Using MWMessage for passing workunit and
result is confusing. workunit and result could be just Writable objects.
special instructions like kill should be given via separate Action commands in
the HeartbeatResponse."
Do you mean this?
{code}
public interface MWProtocol {
public static final long versionID = 1L;
Writable heartBeat(Writable workUnit);
// User implements action commands and status reports himself
// Worker implemented by the user should handle all action commands take
appropriate action like dying and also send send status
// Master implemented by the user should construct and send action commands,
consume status report and take proper action
}
{code}
Or this?
{code}
public interface MWProtocol {
public static final long versionID = 1L;
HeartbeatResponse heartBeat(Writable HeartbeatRequest);
}
public class HeartbeatResponse implements Writable {
// This class has an action command which is hidden from the user
// The framework will operate on the action command, like causing a worker to
die
// User extends this class to carry Work
}
public class HeartbeatRequest implements Writable {
// This class has worker status which is hidden from the user
// User extends this class to carry Result
}
{code}
Or, did I misunderstand the comment?
> Master-Worker Application on YARN
> ---------------------------------
>
> Key: MAPREDUCE-3315
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3315
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Reporter: Sharad Agarwal
> Assignee: Sharad Agarwal
> Fix For: 0.24.0
>
> Attachments: MAPREDUCE-3315-1.patch, MAPREDUCE-3315-2.patch,
> MAPREDUCE-3315-3.patch, MAPREDUCE-3315.patch
>
>
> Currently master worker scenarios are forced fit into Map-Reduce. Now with
> YARN, these can be first class and would benefit real/near realtime workloads
> and be more effective in using the cluster resources.
--
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
