[
https://issues.apache.org/jira/browse/HADOOP-9192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13549016#comment-13549016
]
Todd Lipcon commented on HADOOP-9192:
-------------------------------------
Hi Suresh. I've always been clear about my feelings on the "alpha" label. I'm
sure you remember the thread "Large feature development" from back in September:
{quote}
So, at risk of this thread just becoming a laundry list of bugs that
have existed in HDFS, or a list of bugs in YARN, I'll summarize: I
still think that YARN is "alpha" and HDFS 2 is at least as "stable" as
Hadoop 1.0.
{quote}
The bylaws for our project have no clear definition on how a project gets
labeled alpha vs beta vs stable. Had I known that the "alpha" label would be
used to avoid our agreed-upon requirements for wire compatibility, I would have
voted against the label at release time. Unfortunately, since I am not the RM
for the 2.0.x line, there's no way for me or any other committer to say "look,
we should treat this as stable", other than by voting against individual issues
that break compatibility for the stable components.
Per the thread on general "Locking protocols for 2.x.x" from April 2012, it
seemed to be the consensus that we could lock down the client-server wire
protocol within a few months. In the thread in September, I tried to argue that
HDFS should be labeled "stable" at that point, but lacking any clear policies
around the labeling, there's not much I could do other than argue. So, now I'm
just treating HDFS 2.0 as de facto stable.
As for YARN, I am not active in the YARN project and therefore don't have time,
expertise, or interest to review whether changes there are compatible or not. I
haven't looked at YARN in a few months, so perhaps now it's at the point where
it should also be considered stable and block incompatible changes, or perhaps
it's still in a state of flux. I don't know, so I won't -1 an incompatible YARN
change. But I will -1 wire-incompatible client-server HDFS changes.
> Move token related request/response messages to common
> ------------------------------------------------------
>
> Key: HADOOP-9192
> URL: https://issues.apache.org/jira/browse/HADOOP-9192
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 2.0.2-alpha
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
> Attachments: HADOOP-9192.patch, HADOOP-9192.patch, HADOOP-9192.patch
>
>
> Get, Renew and Cancel delegation token requests and responses are repeated in
> HDFS, Yarn and MR. This jira proposes to move these messages into
> Security.proto in common.
--
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
