[jira] [Commented] (MAPREDUCE-7180) Relaunching Failed Containers
[
https://issues.apache.org/jira/browse/MAPREDUCE-7180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784121#comment-16784121
]
Wilfred Spiegelenburg commented on MAPREDUCE-7180:
--
What I meant is that if an application fails we re-run the application. Any
finished tasks are OK they are recovered, running tasks are killed and
restarted. If they had failed once or more times for the first attempt and we
relaunched them with larger heaps we start the process of increasing the
containers again from scratch, wasting more resources.
I think what Daniel proposed is the simplest most elegant solution. If we have
a task that fails due to exceeding the container we should fail the application
and let the end user and or admin sort it out. Even for an Oozie workflow or in
the Hive case running jobs through beeline you can set the size of the
container etc via the command line.
I think finding the cause is not that difficult but as part of the change to
fail the application we could make it really clear in the diagnostics of the
application what failed and which action to take. The message for the container
exceeding the settings has already been extended via YARN-7580 and should be
clearer in 3.1 and later.
> Relaunching Failed Containers
> -
>
> Key: MAPREDUCE-7180
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7180
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: mrv1, mrv2
>Reporter: David Mollitor
>Priority: Major
>
> In my experience, it is very common that a MR job completely fails because a
> single Mapper/Reducer container is using more memory than has been reserved
> in YARN. The following message is logging the the MapReduce
> ApplicationMaster:
> {code}
> Container [pid=46028,containerID=container_e54_1435155934213_16721_01_003666]
> is running beyond physical memory limits.
> Current usage: 1.0 GB of 1 GB physical memory used; 2.7 GB of 2.1 GB virtual
> memory used. Killing container.
> {code}
> In this case, the container is re-launched on another node, and of course, it
> is killed again for the same reason. This process happens three (maybe
> four?) times before the entire MapReduce job fails. It's often said that the
> definition of insanity is doing the same thing over and over and expecting
> different results.
> For all intents and purposes, the amount of resources requested by Mappers
> and Reducers is a fixed amount; based on the default configuration values.
> Users can set the memory on a per-job basis, but it's a pain, not exact, and
> requires intimate knowledge of the MapReduce framework and its memory usage
> patterns.
> I propose that if the MR ApplicationMaster detects that a container is killed
> because of this specific memory resource constraint, that it requests a
> larger container for the subsequent task attempt.
> For example, increase the requested memory size by 50% each time the
> container fails and the task is retried. This will prevent many Job failures
> and allow for additional memory tuning, per-Job, after the fact, to get
> better performance (v.s. fail/succeed).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-7188) [Clean-up] Remove NULL check before instanceof and fix checkstyle issue in TaskResult
[
https://issues.apache.org/jira/browse/MAPREDUCE-7188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783988#comment-16783988
]
Hadoop QA commented on MAPREDUCE-7188:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
21s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 22m
23s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
24s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
19s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
29s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
12m 1s{color} | {color:green} branch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
45s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
22s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
14s{color} | {color:green} hadoop-mapreduce-project/hadoop-mapreduce-examples:
The patch generated 0 new + 3 unchanged - 11 fixed = 3 total (was 14) {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
13m 6s{color} | {color:green} patch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
46s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
22s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
45s{color} | {color:green} hadoop-mapreduce-examples in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
31s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 54m 17s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:8f97d6f |
| JIRA Issue | MAPREDUCE-7188 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12961082/MAPREDUCE-7188.002.patch
|
| Optional Tests | dupname asflicense compile javac javadoc mvninstall
mvnsite unit shadedclient findbugs checkstyle |
| uname | Linux 36d631451a40 4.4.0-138-generic #164~14.04.1-Ubuntu SMP Fri Oct
5 08:56:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precommit/personality/provided.sh |
| git revision | trunk / 9fcd89a |
| maven | version: Apache Maven 3.3.9 |
| Default Java | 1.8.0_191 |
| findbugs | v3.1.0-RC1 |
| Test Results |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/7591/testReport/ |
| Max. process+thread count | 335 (vs. ulimit of 1) |
| modules | C: hadoop-mapreduce-project/hadoop-mapreduce-examples U:
hadoop-mapreduce-project/hadoop-mapreduce-examples |
| Console output |
[jira] [Comment Edited] (MAPREDUCE-7188) [Clean-up] Remove NULL check before instanceof and fix checkstyle issue in TaskResult
[ https://issues.apache.org/jira/browse/MAPREDUCE-7188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783951#comment-16783951 ] Shweta edited comment on MAPREDUCE-7188 at 3/5/19 1:13 AM: --- Yes, I have asked [~templedf] for access as contributor. Thank you [~adam.antal] for the review. Yes, the default constructor isn't used anywhere as found by code inspection by IntelliJ. I have fixed the checkstyles issues as you mentioned above. Uploaded patch v002. was (Author: shwetayakkali): Thank you [~adam.antal] for the review. Yes, the default constructor isn't used anywhere as found by code inspection by IntelliJ. I have fixed the checkstyles issues as you mentioned above. Uploaded patch v002. > [Clean-up] Remove NULL check before instanceof and fix checkstyle issue in > TaskResult > - > > Key: MAPREDUCE-7188 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7188 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Reporter: Shweta >Priority: Minor > Attachments: MAPREDUCE-7188.001.patch, MAPREDUCE-7188.002.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Updated] (MAPREDUCE-7188) [Clean-up] Remove NULL check before instanceof in TaskResult
[ https://issues.apache.org/jira/browse/MAPREDUCE-7188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shweta updated MAPREDUCE-7188: -- Attachment: MAPREDUCE-7188.002.patch > [Clean-up] Remove NULL check before instanceof in TaskResult > > > Key: MAPREDUCE-7188 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7188 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Reporter: Shweta >Priority: Minor > Attachments: MAPREDUCE-7188.001.patch, MAPREDUCE-7188.002.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-7188) [Clean-up] Remove NULL check before instanceof in TaskResult
[ https://issues.apache.org/jira/browse/MAPREDUCE-7188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783951#comment-16783951 ] Shweta commented on MAPREDUCE-7188: --- Thank you [~adam.antal] for the review. Yes, the default constructor isn't used anywhere as found by code inspection by IntelliJ. I have fixed the checkstyles issues as you mentioned above. Uploaded patch v002. > [Clean-up] Remove NULL check before instanceof in TaskResult > > > Key: MAPREDUCE-7188 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7188 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Reporter: Shweta >Priority: Minor > Attachments: MAPREDUCE-7188.001.patch, MAPREDUCE-7188.002.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Updated] (MAPREDUCE-7188) [Clean-up] Remove NULL check before instanceof and fix checkstyle issue in TaskResult
[ https://issues.apache.org/jira/browse/MAPREDUCE-7188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shweta updated MAPREDUCE-7188: -- Summary: [Clean-up] Remove NULL check before instanceof and fix checkstyle issue in TaskResult (was: [Clean-up] Remove NULL check before instanceof in TaskResult) > [Clean-up] Remove NULL check before instanceof and fix checkstyle issue in > TaskResult > - > > Key: MAPREDUCE-7188 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7188 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Reporter: Shweta >Priority: Minor > Attachments: MAPREDUCE-7188.001.patch, MAPREDUCE-7188.002.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Assigned] (MAPREDUCE-7190) Add SleepJob additional parameter to make paralel runs distinguishable
[ https://issues.apache.org/jira/browse/MAPREDUCE-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Antal reassigned MAPREDUCE-7190: - Assignee: (was: Adam Antal) > Add SleepJob additional parameter to make paralel runs distinguishable > -- > > Key: MAPREDUCE-7190 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7190 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 3.2.0 >Reporter: Adam Antal >Priority: Major > > In our testing framework we use SleepJobs for testing scheduling, and to > check different resource types are assigned properly to containers. Sometimes > we start multiple jobs in parallel, and if one fails, we have to track which > one was that. It is not too hard to find out that information, but would have > been much more convenient, if we it was written in the name of the job. > Proposal: additional parameter to SleepJob, so that its name can be changed > from default "Sleep job." to something like "Sleep job - _additional info_". -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Assigned] (MAPREDUCE-7190) Add SleepJob additional parameter to make paralel runs distinguishable
[ https://issues.apache.org/jira/browse/MAPREDUCE-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Antal reassigned MAPREDUCE-7190: - Assignee: Adam Antal > Add SleepJob additional parameter to make paralel runs distinguishable > -- > > Key: MAPREDUCE-7190 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7190 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 3.2.0 >Reporter: Adam Antal >Assignee: Adam Antal >Priority: Major > > In our testing framework we use SleepJobs for testing scheduling, and to > check different resource types are assigned properly to containers. Sometimes > we start multiple jobs in parallel, and if one fails, we have to track which > one was that. It is not too hard to find out that information, but would have > been much more convenient, if we it was written in the name of the job. > Proposal: additional parameter to SleepJob, so that its name can be changed > from default "Sleep job." to something like "Sleep job - _additional info_". -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Assigned] (MAPREDUCE-7190) Add SleepJob additional parameter to make paralel runs distinguishable
[ https://issues.apache.org/jira/browse/MAPREDUCE-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan reassigned MAPREDUCE-7190: - Assignee: Adam Antal > Add SleepJob additional parameter to make paralel runs distinguishable > -- > > Key: MAPREDUCE-7190 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7190 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 3.2.0 >Reporter: Adam Antal >Assignee: Adam Antal >Priority: Major > > In our testing framework we use SleepJobs for testing scheduling, and to > check different resource types are assigned properly to containers. Sometimes > we start multiple jobs in parallel, and if one fails, we have to track which > one was that. It is not too hard to find out that information, but would have > been much more convenient, if we it was written in the name of the job. > Proposal: additional parameter to SleepJob, so that its name can be changed > from default "Sleep job." to something like "Sleep job - _additional info_". -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (MAPREDUCE-7188) [Clean-up] Remove NULL check before instanceof in TaskResult
[
https://issues.apache.org/jira/browse/MAPREDUCE-7188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783413#comment-16783413
]
Adam Antal edited comment on MAPREDUCE-7188 at 3/4/19 2:23 PM:
---
The patch LGTM (non-binding). Did you think about cleaning up the whole file a
bit?
Three items I would be happy about being done:
* remove default constructor (to me it looks like this is never used, but
needs to be proven)
* checkstyle: there are a few long (>80 char) lines, that could be broken up
(are there other checkstyle issues?)
* adding spaces in the ternary operator in {{combine()}}
was (Author: adam.antal):
The patch LGTM. Did you think about cleaning up the whole file a bit?
Three items I would be happy about being done:
* remove default constructor (to me it looks like this is never used, but
needs to be proven)
* checkstyle: there are a few long (>80 char) lines, that could be broken up
(are there other checkstyle issues?)
* adding spaces in the ternary operator in {{combine()}}
> [Clean-up] Remove NULL check before instanceof in TaskResult
>
>
> Key: MAPREDUCE-7188
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7188
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
>Reporter: Shweta
>Priority: Minor
> Attachments: MAPREDUCE-7188.001.patch
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-7180) Relaunching Failed Containers
[
https://issues.apache.org/jira/browse/MAPREDUCE-7180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783420#comment-16783420
]
BELUGA BEHR commented on MAPREDUCE-7180:
Hey [~wilfreds],
Thanks for the input.
I'm not exactly sure what the 'application re-run' is referring to. My
intention in this JIRA was to address only the Mappers/Reducers. I have
opened [YARN-9260] to discuss the application masters as a separate issue. As
I understand it tough, the AMs are retried one time if they fail, so if the
retry is going to happen anyway, might as well throw some more memory at it.
I think this feature is helpful to have as yet another tool in the toolbox.
One thing I still don't think we're on the same page about is that these
retries, these various scenarios you point out, all valid, and all currently
exist in the YARN framework. There is already a retry capability implemented
that allows for retries at both the application and the worker level. For me,
this is what started this conversation. I noticed that the retry logic was too
naive and would re-launch failed containers that had no hope of succeeding
(because they would OOM every time, or be killed by NM for having too much
overhead, regardless of where they ran). This request is simply an extension
of the retry capability to at least give the containers at least some
opportunity at completing. This ask is in line with standard retry and backoff
strategies.
> Relaunching Failed Containers
> -
>
> Key: MAPREDUCE-7180
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7180
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: mrv1, mrv2
>Reporter: BELUGA BEHR
>Priority: Major
>
> In my experience, it is very common that a MR job completely fails because a
> single Mapper/Reducer container is using more memory than has been reserved
> in YARN. The following message is logging the the MapReduce
> ApplicationMaster:
> {code}
> Container [pid=46028,containerID=container_e54_1435155934213_16721_01_003666]
> is running beyond physical memory limits.
> Current usage: 1.0 GB of 1 GB physical memory used; 2.7 GB of 2.1 GB virtual
> memory used. Killing container.
> {code}
> In this case, the container is re-launched on another node, and of course, it
> is killed again for the same reason. This process happens three (maybe
> four?) times before the entire MapReduce job fails. It's often said that the
> definition of insanity is doing the same thing over and over and expecting
> different results.
> For all intents and purposes, the amount of resources requested by Mappers
> and Reducers is a fixed amount; based on the default configuration values.
> Users can set the memory on a per-job basis, but it's a pain, not exact, and
> requires intimate knowledge of the MapReduce framework and its memory usage
> patterns.
> I propose that if the MR ApplicationMaster detects that a container is killed
> because of this specific memory resource constraint, that it requests a
> larger container for the subsequent task attempt.
> For example, increase the requested memory size by 50% each time the
> container fails and the task is retried. This will prevent many Job failures
> and allow for additional memory tuning, per-Job, after the fact, to get
> better performance (v.s. fail/succeed).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-7188) [Clean-up] Remove NULL check before instanceof in TaskResult
[
https://issues.apache.org/jira/browse/MAPREDUCE-7188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783413#comment-16783413
]
Adam Antal commented on MAPREDUCE-7188:
---
The patch LGTM. Did you think about cleaning up the whole file a bit?
Three items I would be happy about being done:
* remove default constructor (to me it looks like this is never used, but
needs to be proven)
* checkstyle: there are a few long (>80 char) lines, that could be broken up
(are there other checkstyle issues?)
* adding spaces in the ternary operator in {{combine()}}
> [Clean-up] Remove NULL check before instanceof in TaskResult
>
>
> Key: MAPREDUCE-7188
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7188
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
>Reporter: Shweta
>Priority: Minor
> Attachments: MAPREDUCE-7188.001.patch
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-7188) [Clean-up] Remove NULL check before instanceof in TaskResult
[ https://issues.apache.org/jira/browse/MAPREDUCE-7188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783401#comment-16783401 ] Adam Antal commented on MAPREDUCE-7188: --- Hi [~shwetayakkali], Could you assign this issue to yourself? If the option is not there, you probably need to get access to project MAPREDUCE (possibly from a committer). > [Clean-up] Remove NULL check before instanceof in TaskResult > > > Key: MAPREDUCE-7188 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7188 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Reporter: Shweta >Priority: Minor > Attachments: MAPREDUCE-7188.001.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Created] (MAPREDUCE-7190) Add SleepJob additional parameter to make paralel runs distinguishable
Adam Antal created MAPREDUCE-7190: - Summary: Add SleepJob additional parameter to make paralel runs distinguishable Key: MAPREDUCE-7190 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7190 Project: Hadoop Map/Reduce Issue Type: Improvement Affects Versions: 3.2.0 Reporter: Adam Antal In our testing framework we use SleepJobs for testing scheduling, and to check different resource types are assigned properly to containers. Sometimes we start multiple jobs in parallel, and if one fails, we have to track which one was that. It is not too hard to find out that information, but would have been much more convenient, if we it was written in the name of the job. Proposal: additional parameter to SleepJob, so that its name can be changed from default "Sleep job." to something like "Sleep job - _additional info_". -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
