[jira] [Commented] (MAPREDUCE-695) MiniMRCluster while shutting down should not wait for currently running jobs to finish

2015-05-01 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on MAPREDUCE-695:
-

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch |   0m  0s | The patch command could not apply 
the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | 
http://issues.apache.org/jira/secure/attachment/12412383/mapreduce-695.patch |
| Optional Tests | javac unit findbugs checkstyle |
| git revision | trunk / f1a152c |
| Console output | 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5499/console |


This message was automatically generated.

 MiniMRCluster while shutting down should not wait for currently running jobs 
 to finish
 --

 Key: MAPREDUCE-695
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-695
 Project: Hadoop Map/Reduce
  Issue Type: Bug
  Components: test
Affects Versions: 1.0.3
Reporter: Sreekanth Ramakrishnan
Priority: Minor
 Attachments: mapreduce-695.patch


 Currently in {{org.apache.hadoop.mapred.MiniMRCluster.shutdown()}} we do a 
 {{waitTaskTrackers()}} which can cause {{MiniMRCluster}} to hang indefinitely 
 when used in conjunction with Controlled jobs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MAPREDUCE-695) MiniMRCluster while shutting down should not wait for currently running jobs to finish

2012-10-09 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on MAPREDUCE-695:
-

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12412383/mapreduce-695.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-MAPREDUCE-Build/2920//console

This message is automatically generated.

 MiniMRCluster while shutting down should not wait for currently running jobs 
 to finish
 --

 Key: MAPREDUCE-695
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-695
 Project: Hadoop Map/Reduce
  Issue Type: Bug
  Components: test
Affects Versions: 1.0.3
Reporter: Sreekanth Ramakrishnan
Priority: Minor
 Attachments: mapreduce-695.patch


 Currently in {{org.apache.hadoop.mapred.MiniMRCluster.shutdown()}} we do a 
 {{waitTaskTrackers()}} which can cause {{MiniMRCluster}} to hang indefinitely 
 when used in conjunction with Controlled jobs.

--
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

[jira] [Commented] (MAPREDUCE-695) MiniMRCluster while shutting down should not wait for currently running jobs to finish

2012-10-09 Thread Steve Loughran (JIRA) 

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

Steve Loughran commented on MAPREDUCE-695:
--

Although this doesn't apply to trunk, it does work on branch 1. It is testable 
though -the patch really needs it to catch regressions.

 MiniMRCluster while shutting down should not wait for currently running jobs 
 to finish
 --

 Key: MAPREDUCE-695
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-695
 Project: Hadoop Map/Reduce
  Issue Type: Bug
  Components: test
Affects Versions: 1.0.3
Reporter: Sreekanth Ramakrishnan
Priority: Minor
 Attachments: mapreduce-695.patch


 Currently in {{org.apache.hadoop.mapred.MiniMRCluster.shutdown()}} we do a 
 {{waitTaskTrackers()}} which can cause {{MiniMRCluster}} to hang indefinitely 
 when used in conjunction with Controlled jobs.

--
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