Re: Looking to a Hadoop 3 release

A heads up that I think we're getting close on the blockers for the first alpha. Looking at my list, I see two I'd like to get in still: YARN-5270 and HADOOP-13316. Will cut a branch and roll the release once those go in; my test builds have looked good thus far. My original plan was to do alphas

[jira] [Resolved] (HADOOP-13325) s3n fails to work with S3 Frankfurt or Seol - 400 : Bad Request

[ https://issues.apache.org/jira/browse/HADOOP-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved HADOOP-13325. - Resolution: Won't Fix > s3n fails to work with S3 Frankfurt or Seol - 400 : Bad Request

[jira] [Created] (HADOOP-13325) s3n fails to work with S3 Frankfurt or Seol

Steve Loughran created HADOOP-13325: --- Summary: s3n fails to work with S3 Frankfurt or Seol Key: HADOOP-13325 URL: https://issues.apache.org/jira/browse/HADOOP-13325 Project: Hadoop Common

[jira] [Created] (HADOOP-13324) s3a doesn't authenticate with S3 frankfurt (or other V4 auth only endpoints)

Steve Loughran created HADOOP-13324: --- Summary: s3a doesn't authenticate with S3 frankfurt (or other V4 auth only endpoints) Key: HADOOP-13324 URL: https://issues.apache.org/jira/browse/HADOOP-13324

[jira] [Created] (HADOOP-13323) Downgrade stack trace on FS load from Warn to debug

Steve Loughran created HADOOP-13323: --- Summary: Downgrade stack trace on FS load from Warn to debug Key: HADOOP-13323 URL: https://issues.apache.org/jira/browse/HADOOP-13323 Project: Hadoop Common

[DICUSS] Upgrading Guice to 4.0(HADOOP-12064)

Hi developers, I will plan to upgrade Google Guice dependency on trunk. The change also includes asm and cglib upgrade. I checked following points: * Both HDFS and YARN UIs work well. * All webIU-related tests pass as described on HADOOP-12064. * Ran mapreduce job, and it works well.

Re: Failure to submit job on trunk hadoop cluster

Hey Sunil and Rohith, Thanks a lot! As you mentioned, it works well after configuring mapreduce.admin.user.env and yarn.app.mapreduce.am.env. As Sangjin also mentioned on MAPREDUCE-6704, it's better to configure mapred.child.env instead of mapreduce.admin.user.env until the problem described

RE: Failure to submit job on trunk hadoop cluster

Hi Tsuyoshi I think it is modified for security reasons. I too did not find any JIRA id corresponding to this commit. Related discussion happened in the following JIRA. https://issues.apache.org/jira/browse/MAPREDUCE-6704 Thanks & Regards Rohith Sharma K S -Original Message- From:

Re: Failure to submit job on trunk hadoop cluster

Hi Tsuyoshi I think you might need to set below environment variables for HADOOP_MAPRED_HOME mapreduce.admin.user.env yarn.app.mapreduce.am.env Thanks Sunil On Mon, Jun 27, 2016 at 4:10 PM Tsuyoshi Ozawa wrote: > Hi, > > Have anyone tried to submit jobs on trunk cluster? >

Failure to submit job on trunk hadoop cluster

Hi, Have anyone tried to submit jobs on trunk cluster? I failed to launch jobs by class not found error with following error messages. Should I change environment variables to setup from branch-2's one? I'm using the same configuration as Hadoop 2 can run. $ hadoop jar

[jira] [Created] (HADOOP-13322) Comment in Kerberos file is not properly parsed

Serhiy Boychenko created HADOOP-13322: - Summary: Comment in Kerberos file is not properly parsed Key: HADOOP-13322 URL: https://issues.apache.org/jira/browse/HADOOP-13322 Project: Hadoop Common