Please followup on Jenkins failures. Looks like the patch is generated at the wrong directory.
On Thu, Feb 28, 2013 at 1:34 AM, Azuryy Yu <[email protected]> wrote: > Who can review this JIRA(https://issues.apache.org/jira/browse/HDFS-4533), > which is very simple. > > > ---------- Forwarded message ---------- > From: Hadoop QA (JIRA) <[email protected]> > Date: Wed, Feb 27, 2013 at 4:53 PM > Subject: [jira] [Commented] (HDFS-4533) start-dfs.sh ignored additional > parameters besides -upgrade > To: [email protected] > > > > [ > https://issues.apache.org/jira/browse/HDFS-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588130#comment-13588130] > > Hadoop QA commented on HDFS-4533: > --------------------------------- > > {color:red}-1 overall{color}. Here are the results of testing the latest > attachment > http://issues.apache.org/jira/secure/attachment/12571164/HDFS-4533.patch > against trunk revision . > > {color:red}-1 patch{color}. The patch command could not apply the > patch. > > Console output: > https://builds.apache.org/job/PreCommit-HDFS-Build/4008//console > > This message is automatically generated. > > > start-dfs.sh ignored additional parameters besides -upgrade > > ----------------------------------------------------------- > > > > Key: HDFS-4533 > > URL: https://issues.apache.org/jira/browse/HDFS-4533 > > Project: Hadoop HDFS > > Issue Type: Bug > > Components: datanode, namenode > > Affects Versions: 2.0.3-alpha > > Reporter: Fengdong Yu > > Labels: patch > > Fix For: 2.0.4-beta > > > > Attachments: HDFS-4533.patch > > > > > > start-dfs.sh only takes -upgrade option and ignored others. > > So If run the following command, it will ignore the clusterId option. > > start-dfs.sh -upgrade -clusterId 1234 > > -- > 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 > > -- http://hortonworks.com/download/
