HDFS-1943 <https://issues.apache.org/jira/browse/HDFS-1943> is a resolved
bug which was opened only against 0.22 and 0.23. No one in the community
(including you) saw fit to raise it as a concern for 0.20-security, despite
multiple public invitations to propose jiras for inclusion in 0.20.205.
Testing a release candidate is a community effort, and out of all the
people in the community who tested the RC, no one found or raised this as an
Nevertheless, I would be happy to include the fix in the next release. If
you would like it to be included, please re-open the jira for a backport,
and preferably submit a tested patch. And yes, I am considering a
0.20.205.1 bug fix release, so if a tested patch is submitted in the near
future, it can go in.
Regarding the second issue, "unfortunate placement of the task-controller
binary", again please open a jira and submit a tested patch. I'll be happy
to include it in the next release.
Thank you for raising these issues. I hope in the future the Bigtop team
will consider testing the next Hadoop release candidate before the vote
closes instead of after.
On Thu, Oct 20, 2011 at 8:18 PM, Roman Shaposhnik <[EMAIL PROTECTED]> wrote:
> On Tue, Oct 18, 2011 at 12:24 PM, Matt Foley <[EMAIL PROTECTED]> wrote:
> > On Friday 14 Oct, the Hadoop community voted ten to zero (including four
> > members voting in favor) to accept the release of Hadoop 0.20.205.0.
> Once we pulled this release into Bigtop the first thing we discovered was
> that datanode can't be started out-of-the-box because of the infamous:
> I'm a little bit surprised it didn't get caught during your testing
> since it shows
> up right away. Given that its really annoying I'm wondering whether it
> can be patched somehow in a .1 fixup perhaps?
> Second thing was an unfortunate placement of the task-controller binary
> that prevents having multiple arcs installed on the same machine. Other
> than that -- looks good so far.