[jira] [Commented] (MAPREDUCE-5805) Unable to parse launch time from job history file

2014-05-27 Thread jay vyas (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14010737#comment-14010737
 ] 

jay vyas commented on MAPREDUCE-5805:
-

Any possible relation of this to MAPREDUCE-5902 ?

 Unable to parse launch time from job history file
 -

 Key: MAPREDUCE-5805
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5805
 Project: Hadoop Map/Reduce
  Issue Type: Bug
  Components: jobhistoryserver
Affects Versions: 2.3.0
Reporter: Fengdong Yu
Assignee: Akira AJISAKA
 Fix For: 2.4.0

 Attachments: MAPREDUCE-5805.patch


 when job complete, there are WARN complains in the log:
 {code}
 2014-03-19 13:31:10,036 WARN 
 org.apache.hadoop.mapreduce.v2.jobhistory.FileNameIndexUtils: Unable to parse 
 launch time from job history file 
 job_1395204058904_0003-1395206473646-root-test_one_word-1395206966214-4-2-SUCCEEDED-root.test-queue-1395206480070.jhist
  : java.lang.NumberFormatException: For input string: queue
 {code}
 because  there is (-)  in the queue name 'test-queue', we split the job 
 history file name by (-), and get the ninth item as job start time.
 FileNameIndexUtils.java
 {code}
 private static final int JOB_START_TIME_INDEX = 9;
 {code}
 but there is another potential issue:
 if I also include '-' in the job name(test_one_world in this case), there are 
 all misunderstand.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (MAPREDUCE-5805) Unable to parse launch time from job history file

2014-03-27 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13949168#comment-13949168
 ] 

Hudson commented on MAPREDUCE-5805:
---

SUCCESS: Integrated in Hadoop-Yarn-trunk #522 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk/522/])
MAPREDUCE-5805. Fixed MapReduce JobHistory encoding of queue-name to escape 
hyphens and thus avoid parsing errors. Contributed by Akira Ajisaka. (vinodkv: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1582125)
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/jobhistory/FileNameIndexUtils.java
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/jobhistory/TestFileNameIndexUtils.java


 Unable to parse launch time from job history file
 -

 Key: MAPREDUCE-5805
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5805
 Project: Hadoop Map/Reduce
  Issue Type: Bug
  Components: jobhistoryserver
Affects Versions: 2.3.0
Reporter: Fengdong Yu
Assignee: Akira AJISAKA
 Fix For: 2.4.0

 Attachments: MAPREDUCE-5805.patch


 when job complete, there are WARN complains in the log:
 {code}
 2014-03-19 13:31:10,036 WARN 
 org.apache.hadoop.mapreduce.v2.jobhistory.FileNameIndexUtils: Unable to parse 
 launch time from job history file 
 job_1395204058904_0003-1395206473646-root-test_one_word-1395206966214-4-2-SUCCEEDED-root.test-queue-1395206480070.jhist
  : java.lang.NumberFormatException: For input string: queue
 {code}
 because  there is (-)  in the queue name 'test-queue', we split the job 
 history file name by (-), and get the ninth item as job start time.
 FileNameIndexUtils.java
 {code}
 private static final int JOB_START_TIME_INDEX = 9;
 {code}
 but there is another potential issue:
 if I also include '-' in the job name(test_one_world in this case), there are 
 all misunderstand.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (MAPREDUCE-5805) Unable to parse launch time from job history file

2014-03-27 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13949320#comment-13949320
 ] 

Hudson commented on MAPREDUCE-5805:
---

FAILURE: Integrated in Hadoop-Mapreduce-trunk #1739 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1739/])
MAPREDUCE-5805. Fixed MapReduce JobHistory encoding of queue-name to escape 
hyphens and thus avoid parsing errors. Contributed by Akira Ajisaka. (vinodkv: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1582125)
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/jobhistory/FileNameIndexUtils.java
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/jobhistory/TestFileNameIndexUtils.java


 Unable to parse launch time from job history file
 -

 Key: MAPREDUCE-5805
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5805
 Project: Hadoop Map/Reduce
  Issue Type: Bug
  Components: jobhistoryserver
Affects Versions: 2.3.0
Reporter: Fengdong Yu
Assignee: Akira AJISAKA
 Fix For: 2.4.0

 Attachments: MAPREDUCE-5805.patch


 when job complete, there are WARN complains in the log:
 {code}
 2014-03-19 13:31:10,036 WARN 
 org.apache.hadoop.mapreduce.v2.jobhistory.FileNameIndexUtils: Unable to parse 
 launch time from job history file 
 job_1395204058904_0003-1395206473646-root-test_one_word-1395206966214-4-2-SUCCEEDED-root.test-queue-1395206480070.jhist
  : java.lang.NumberFormatException: For input string: queue
 {code}
 because  there is (-)  in the queue name 'test-queue', we split the job 
 history file name by (-), and get the ninth item as job start time.
 FileNameIndexUtils.java
 {code}
 private static final int JOB_START_TIME_INDEX = 9;
 {code}
 but there is another potential issue:
 if I also include '-' in the job name(test_one_world in this case), there are 
 all misunderstand.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (MAPREDUCE-5805) Unable to parse launch time from job history file

2014-03-27 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13949353#comment-13949353
 ] 

Hudson commented on MAPREDUCE-5805:
---

SUCCESS: Integrated in Hadoop-Hdfs-trunk #1714 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1714/])
MAPREDUCE-5805. Fixed MapReduce JobHistory encoding of queue-name to escape 
hyphens and thus avoid parsing errors. Contributed by Akira Ajisaka. (vinodkv: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1582125)
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/jobhistory/FileNameIndexUtils.java
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/jobhistory/TestFileNameIndexUtils.java


 Unable to parse launch time from job history file
 -

 Key: MAPREDUCE-5805
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5805
 Project: Hadoop Map/Reduce
  Issue Type: Bug
  Components: jobhistoryserver
Affects Versions: 2.3.0
Reporter: Fengdong Yu
Assignee: Akira AJISAKA
 Fix For: 2.4.0

 Attachments: MAPREDUCE-5805.patch


 when job complete, there are WARN complains in the log:
 {code}
 2014-03-19 13:31:10,036 WARN 
 org.apache.hadoop.mapreduce.v2.jobhistory.FileNameIndexUtils: Unable to parse 
 launch time from job history file 
 job_1395204058904_0003-1395206473646-root-test_one_word-1395206966214-4-2-SUCCEEDED-root.test-queue-1395206480070.jhist
  : java.lang.NumberFormatException: For input string: queue
 {code}
 because  there is (-)  in the queue name 'test-queue', we split the job 
 history file name by (-), and get the ninth item as job start time.
 FileNameIndexUtils.java
 {code}
 private static final int JOB_START_TIME_INDEX = 9;
 {code}
 but there is another potential issue:
 if I also include '-' in the job name(test_one_world in this case), there are 
 all misunderstand.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (MAPREDUCE-5805) Unable to parse launch time from job history file

2014-03-26 Thread Vinod Kumar Vavilapalli (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13948657#comment-13948657
 ] 

Vinod Kumar Vavilapalli commented on MAPREDUCE-5805:


Looks good, checking this in.

 Unable to parse launch time from job history file
 -

 Key: MAPREDUCE-5805
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5805
 Project: Hadoop Map/Reduce
  Issue Type: Bug
  Components: jobhistoryserver
Affects Versions: 2.3.0
Reporter: Fengdong Yu
Assignee: Akira AJISAKA
 Attachments: MAPREDUCE-5805.patch


 when job complete, there are WARN complains in the log:
 {code}
 2014-03-19 13:31:10,036 WARN 
 org.apache.hadoop.mapreduce.v2.jobhistory.FileNameIndexUtils: Unable to parse 
 launch time from job history file 
 job_1395204058904_0003-1395206473646-root-test_one_word-1395206966214-4-2-SUCCEEDED-root.test-queue-1395206480070.jhist
  : java.lang.NumberFormatException: For input string: queue
 {code}
 because  there is (-)  in the queue name 'test-queue', we split the job 
 history file name by (-), and get the ninth item as job start time.
 FileNameIndexUtils.java
 {code}
 private static final int JOB_START_TIME_INDEX = 9;
 {code}
 but there is another potential issue:
 if I also include '-' in the job name(test_one_world in this case), there are 
 all misunderstand.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (MAPREDUCE-5805) Unable to parse launch time from job history file

2014-03-26 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13948712#comment-13948712
 ] 

Hudson commented on MAPREDUCE-5805:
---

SUCCESS: Integrated in Hadoop-trunk-Commit #5414 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/5414/])
MAPREDUCE-5805. Fixed MapReduce JobHistory encoding of queue-name to escape 
hyphens and thus avoid parsing errors. Contributed by Akira Ajisaka. (vinodkv: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1582125)
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/jobhistory/FileNameIndexUtils.java
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/jobhistory/TestFileNameIndexUtils.java


 Unable to parse launch time from job history file
 -

 Key: MAPREDUCE-5805
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5805
 Project: Hadoop Map/Reduce
  Issue Type: Bug
  Components: jobhistoryserver
Affects Versions: 2.3.0
Reporter: Fengdong Yu
Assignee: Akira AJISAKA
 Fix For: 2.4.0

 Attachments: MAPREDUCE-5805.patch


 when job complete, there are WARN complains in the log:
 {code}
 2014-03-19 13:31:10,036 WARN 
 org.apache.hadoop.mapreduce.v2.jobhistory.FileNameIndexUtils: Unable to parse 
 launch time from job history file 
 job_1395204058904_0003-1395206473646-root-test_one_word-1395206966214-4-2-SUCCEEDED-root.test-queue-1395206480070.jhist
  : java.lang.NumberFormatException: For input string: queue
 {code}
 because  there is (-)  in the queue name 'test-queue', we split the job 
 history file name by (-), and get the ninth item as job start time.
 FileNameIndexUtils.java
 {code}
 private static final int JOB_START_TIME_INDEX = 9;
 {code}
 but there is another potential issue:
 if I also include '-' in the job name(test_one_world in this case), there are 
 all misunderstand.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (MAPREDUCE-5805) Unable to parse launch time from job history file

2014-03-19 Thread Akira AJISAKA (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13940784#comment-13940784
 ] 

Akira AJISAKA commented on MAPREDUCE-5805:
--

Moved to MapReduce project.

 Unable to parse launch time from job history file
 -

 Key: MAPREDUCE-5805
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5805
 Project: Hadoop Map/Reduce
  Issue Type: Bug
  Components: jobhistoryserver
Affects Versions: 2.3.0
Reporter: Fengdong Yu
Assignee: Akira AJISAKA
Priority: Minor

 when job complete, there are WARN complains in the log:
 {code}
 2014-03-19 13:31:10,036 WARN 
 org.apache.hadoop.mapreduce.v2.jobhistory.FileNameIndexUtils: Unable to parse 
 launch time from job history file 
 job_1395204058904_0003-1395206473646-root-test_one_word-1395206966214-4-2-SUCCEEDED-root.test-queue-1395206480070.jhist
  : java.lang.NumberFormatException: For input string: queue
 {code}
 because  there is (-)  in the queue name 'test-queue', we split the job 
 history file name by (-), and get the ninth item as job start time.
 FileNameIndexUtils.java
 {code}
 private static final int JOB_START_TIME_INDEX = 9;
 {code}
 but there is another potential issue:
 if I also include '-' in the job name(test_one_world in this case), there are 
 all misunderstand.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (MAPREDUCE-5805) Unable to parse launch time from job history file

2014-03-19 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13940859#comment-13940859
 ] 

Hadoop QA commented on MAPREDUCE-5805:
--

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12635609/MAPREDUCE-5805.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4443//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4443//console

This message is automatically generated.

 Unable to parse launch time from job history file
 -

 Key: MAPREDUCE-5805
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5805
 Project: Hadoop Map/Reduce
  Issue Type: Bug
  Components: jobhistoryserver
Affects Versions: 2.3.0
Reporter: Fengdong Yu
Assignee: Akira AJISAKA
 Attachments: MAPREDUCE-5805.patch


 when job complete, there are WARN complains in the log:
 {code}
 2014-03-19 13:31:10,036 WARN 
 org.apache.hadoop.mapreduce.v2.jobhistory.FileNameIndexUtils: Unable to parse 
 launch time from job history file 
 job_1395204058904_0003-1395206473646-root-test_one_word-1395206966214-4-2-SUCCEEDED-root.test-queue-1395206480070.jhist
  : java.lang.NumberFormatException: For input string: queue
 {code}
 because  there is (-)  in the queue name 'test-queue', we split the job 
 history file name by (-), and get the ninth item as job start time.
 FileNameIndexUtils.java
 {code}
 private static final int JOB_START_TIME_INDEX = 9;
 {code}
 but there is another potential issue:
 if I also include '-' in the job name(test_one_world in this case), there are 
 all misunderstand.



--
This message was sent by Atlassian JIRA
(v6.2#6252)