Eli Reisman created GIRAPH-569:
----------------------------------
Summary: Decided what the versioning story should be for Giraph on
YARN
Key: GIRAPH-569
URL: https://issues.apache.org/jira/browse/GIRAPH-569
Project: Giraph
Issue Type: Task
Affects Versions: 0.2.0
Reporter: Eli Reisman
Priority: Minor
Right now, Giraph straddles the fence between a new and old YARN API. The place
we're starting is a good compromise but we will need to make some decisions if
we want to backport.
Pros:
Service as many version of YARN as possible, going back potentially to 2.0.1 or
2.0.0.
Cons:
I would like to provide the slickest, most up-to-date example of how to run a
framework like Giraph with a YARN cluster so that others can take an example
from us. I have been told by folks who know that these newer API's are more
concise and more robust. But this is currently looking like supporting
2.0.3-alpha at the very oldest, and newer versions up to trunk, and thats it.
This sort sucks because we have legitimate, working profiles for the whole
2.0.x line and there may be some expectations there.
On the other hand, by not backporting, could go the other direction and adopt
some of the newest 2.0.4-alpha API and just assume YARN is maturing and folks
using it now would update with each alpha release right away anyhow. Adding the
new API's to the whole YARN impl (especially the GiraphApplicationMaster) would
make the implementation a real nice example of how to use the new API's and
would make the profile more robust in job runs.
Opinions?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
