[jira] [Commented] (MAPREDUCE-7053) Timed out tasks can fail to produce thread dump
[
https://issues.apache.org/jira/browse/MAPREDUCE-7053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16366430#comment-16366430
]
Hadoop QA commented on MAPREDUCE-7053:
--
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 20m
31s{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:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 2 new or modified test
files. {color} |
|| || || || {color:brown} branch-2 Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 13m
13s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
29s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
20s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
37s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
51s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
23s{color} | {color:green} branch-2 passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
30s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
26s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
26s{color} | {color:green} the patch passed {color} |
| {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange}
0m 14s{color} | {color:orange}
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app:
The patch generated 1 new + 26 unchanged - 1 fixed = 27 total (was 27) {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
30s{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} findbugs {color} | {color:green} 0m
58s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
18s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 8m
58s{color} | {color:green} hadoop-mapreduce-client-app in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
24s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 49m 49s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:17213a0 |
| JIRA Issue | MAPREDUCE-7053 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12910809/MAPREDUCE-7053-branch-2.001.patch
|
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit shadedclient findbugs checkstyle |
| uname | Linux 8b2acb9175d7 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precommit/personality/provided.sh |
| git revision | branch-2 / fe044e6 |
| maven | version: Apache Maven 3.3.9
(bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T16:41:47+00:00) |
| Default Java | 1.7.0_151 |
| findbugs | v3.0.0 |
| checkstyle |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/7344/artifact/out/diff-checkstyle-hadoop-mapreduce-project_hadoop-mapreduce-client_hadoop-mapreduce-client-app.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/7344/testReport/ |
| Max. process+thread count | 481 (vs. ulimit of 5500) |
| modules | C:
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app U:
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app |
| Console output |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/7344/console |
| Powered by | Apache Yetus 0.8.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
[jira] [Commented] (MAPREDUCE-7052) TestFixedLengthInputFormat#testFormatCompressedIn is flaky
[
https://issues.apache.org/jira/browse/MAPREDUCE-7052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16366406#comment-16366406
]
Hudson commented on MAPREDUCE-7052:
---
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13666 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/13666/])
MAPREDUCE-7052. TestFixedLengthInputFormat#testFormatCompressedIn is (jlowe:
rev a53d62ab26e170a0338f93e228718da52e9196e4)
* (edit)
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/TestFixedLengthInputFormat.java
> TestFixedLengthInputFormat#testFormatCompressedIn is flaky
> --
>
> Key: MAPREDUCE-7052
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7052
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client, test
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Fix For: 3.1.0, 3.0.1, 2.10.0, 2.9.1, 2.8.4, 2.7.6
>
> Attachments: MAPREDUCE-7052-001.patch, MAPREDUCE-7052-002.patch
>
>
> Sometimes the test case TestFixedLengthInputFormat#testFormatCompressedIn can
> fail with the following error:
> {noformat}
> java.lang.OutOfMemoryError: Requested array size exceeds VM limit
> at
> org.apache.hadoop.mapred.TestFixedLengthInputFormat.runRandomTests(TestFixedLengthInputFormat.java:322)
> at
> org.apache.hadoop.mapred.TestFixedLengthInputFormat.testFormatCompressedIn(TestFixedLengthInputFormat.java:90)
> {noformat}
> *Root cause:* under special circumstances, the following line can return a
> huge number:
> {noformat}
> // Test a split size that is less than record len
> numSplits = (int)(fileSize/Math.floor(recordLength/2));
> {noformat}
> For example, let {{seed}} be 2026428718. This causes {{recordLength}} to be 1
> at iteration 19. {{Math.floor()}} returns negative Infinity, which becomes
> positve infinity after the divison. Casting it to {{int}} yields
> {{Integer.MAX_VALUE}}. Eventually we get an OOME because the test wants to
> create a huge {{InputSplit}} array.
--
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-7053) Timed out tasks can fail to produce thread dump
[ https://issues.apache.org/jira/browse/MAPREDUCE-7053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated MAPREDUCE-7053: -- Affects Version/s: (was: 2.7.6) Target Version/s: 3.1.0, 3.0.1, 2.10.0, 2.9.1, 2.8.4 (was: 3.1.0, 3.0.1, 2.10.0, 2.9.1, 2.8.4, 2.7.6) Actually I don't think this is needed for branch-2.7. MAPREDUCE-5044 which added the thread dump support on timeout didn't appear until 2.8. > Timed out tasks can fail to produce thread dump > --- > > Key: MAPREDUCE-7053 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7053 > Project: Hadoop Map/Reduce > Issue Type: Bug >Affects Versions: 3.1.0, 3.0.1, 2.10.0, 2.9.1, 2.8.4 >Reporter: Jason Lowe >Assignee: Jason Lowe >Priority: Major > Attachments: MAPREDUCE-7053-branch-2.001.patch, > MAPREDUCE-7053.001.patch > > > TestMRJobs#testThreadDumpOnTaskTimeout has been failing sporadically > recently. When the AM times out a task it immediately removes it from the > list of known tasks and then connects to the NM to request a thread dump > followed by a kill. If the task heartbeats in after the task has been > removed from the list of known tasks but before the thread dump signal > arrives then the task can exit with a "org.apache.hadoop.mapred.Task: Parent > died." message and no thread dump. -- 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-7052) TestFixedLengthInputFormat#testFormatCompressedIn is flaky
[
https://issues.apache.org/jira/browse/MAPREDUCE-7052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe updated MAPREDUCE-7052:
--
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.7.6
2.8.4
2.9.1
2.10.0
3.0.1
3.1.0
Status: Resolved (was: Patch Available)
Thanks, [~pbacsko]! I committed this to trunk, branch-3.1, branch-3.0,
branch-3.0.1, branch-2, branch-2.9, branch-2.8, and branch-2.7.
> TestFixedLengthInputFormat#testFormatCompressedIn is flaky
> --
>
> Key: MAPREDUCE-7052
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7052
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client, test
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Fix For: 3.1.0, 3.0.1, 2.10.0, 2.9.1, 2.8.4, 2.7.6
>
> Attachments: MAPREDUCE-7052-001.patch, MAPREDUCE-7052-002.patch
>
>
> Sometimes the test case TestFixedLengthInputFormat#testFormatCompressedIn can
> fail with the following error:
> {noformat}
> java.lang.OutOfMemoryError: Requested array size exceeds VM limit
> at
> org.apache.hadoop.mapred.TestFixedLengthInputFormat.runRandomTests(TestFixedLengthInputFormat.java:322)
> at
> org.apache.hadoop.mapred.TestFixedLengthInputFormat.testFormatCompressedIn(TestFixedLengthInputFormat.java:90)
> {noformat}
> *Root cause:* under special circumstances, the following line can return a
> huge number:
> {noformat}
> // Test a split size that is less than record len
> numSplits = (int)(fileSize/Math.floor(recordLength/2));
> {noformat}
> For example, let {{seed}} be 2026428718. This causes {{recordLength}} to be 1
> at iteration 19. {{Math.floor()}} returns negative Infinity, which becomes
> positve infinity after the divison. Casting it to {{int}} yields
> {{Integer.MAX_VALUE}}. Eventually we get an OOME because the test wants to
> create a huge {{InputSplit}} array.
--
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-7053) Timed out tasks can fail to produce thread dump
[ https://issues.apache.org/jira/browse/MAPREDUCE-7053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16366266#comment-16366266 ] Jason Lowe commented on MAPREDUCE-7053: --- Thanks for the reviews! Here's the equivalent patch for branch-2. There needs to be a separate one for branch-2.7 as well. > Timed out tasks can fail to produce thread dump > --- > > Key: MAPREDUCE-7053 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7053 > Project: Hadoop Map/Reduce > Issue Type: Bug >Affects Versions: 3.1.0, 3.0.1, 2.10.0, 2.9.1, 2.8.4, 2.7.6 >Reporter: Jason Lowe >Assignee: Jason Lowe >Priority: Major > Attachments: MAPREDUCE-7053-branch-2.001.patch, > MAPREDUCE-7053.001.patch > > > TestMRJobs#testThreadDumpOnTaskTimeout has been failing sporadically > recently. When the AM times out a task it immediately removes it from the > list of known tasks and then connects to the NM to request a thread dump > followed by a kill. If the task heartbeats in after the task has been > removed from the list of known tasks but before the thread dump signal > arrives then the task can exit with a "org.apache.hadoop.mapred.Task: Parent > died." message and no thread dump. -- 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-7053) Timed out tasks can fail to produce thread dump
[ https://issues.apache.org/jira/browse/MAPREDUCE-7053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated MAPREDUCE-7053: -- Attachment: MAPREDUCE-7053-branch-2.001.patch > Timed out tasks can fail to produce thread dump > --- > > Key: MAPREDUCE-7053 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7053 > Project: Hadoop Map/Reduce > Issue Type: Bug >Affects Versions: 3.1.0, 3.0.1, 2.10.0, 2.9.1, 2.8.4, 2.7.6 >Reporter: Jason Lowe >Assignee: Jason Lowe >Priority: Major > Attachments: MAPREDUCE-7053-branch-2.001.patch, > MAPREDUCE-7053.001.patch > > > TestMRJobs#testThreadDumpOnTaskTimeout has been failing sporadically > recently. When the AM times out a task it immediately removes it from the > list of known tasks and then connects to the NM to request a thread dump > followed by a kill. If the task heartbeats in after the task has been > removed from the list of known tasks but before the thread dump signal > arrives then the task can exit with a "org.apache.hadoop.mapred.Task: Parent > died." message and no thread dump. -- 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-7053) Timed out tasks can fail to produce thread dump
[ https://issues.apache.org/jira/browse/MAPREDUCE-7053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16366263#comment-16366263 ] Eric Payne commented on MAPREDUCE-7053: --- Thanks [~jlowe] for fixing this problem, and thanks [~pbacsko] for the review. +1. The patch LGTM. > Timed out tasks can fail to produce thread dump > --- > > Key: MAPREDUCE-7053 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7053 > Project: Hadoop Map/Reduce > Issue Type: Bug >Affects Versions: 3.1.0, 3.0.1, 2.10.0, 2.9.1, 2.8.4, 2.7.6 >Reporter: Jason Lowe >Assignee: Jason Lowe >Priority: Major > Attachments: MAPREDUCE-7053.001.patch > > > TestMRJobs#testThreadDumpOnTaskTimeout has been failing sporadically > recently. When the AM times out a task it immediately removes it from the > list of known tasks and then connects to the NM to request a thread dump > followed by a kill. If the task heartbeats in after the task has been > removed from the list of known tasks but before the thread dump signal > arrives then the task can exit with a "org.apache.hadoop.mapred.Task: Parent > died." message and no thread dump. -- 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-7052) TestFixedLengthInputFormat#testFormatCompressedIn is flaky
[
https://issues.apache.org/jira/browse/MAPREDUCE-7052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16366242#comment-16366242
]
Jason Lowe commented on MAPREDUCE-7052:
---
Thanks for updating the patch! I agree this is a much simpler fix. The unit
test failure is unrelated and tracked by MAPREDUCE-7053.
+1 lgtm. Committing this.
> TestFixedLengthInputFormat#testFormatCompressedIn is flaky
> --
>
> Key: MAPREDUCE-7052
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7052
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client, test
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: MAPREDUCE-7052-001.patch, MAPREDUCE-7052-002.patch
>
>
> Sometimes the test case TestFixedLengthInputFormat#testFormatCompressedIn can
> fail with the following error:
> {noformat}
> java.lang.OutOfMemoryError: Requested array size exceeds VM limit
> at
> org.apache.hadoop.mapred.TestFixedLengthInputFormat.runRandomTests(TestFixedLengthInputFormat.java:322)
> at
> org.apache.hadoop.mapred.TestFixedLengthInputFormat.testFormatCompressedIn(TestFixedLengthInputFormat.java:90)
> {noformat}
> *Root cause:* under special circumstances, the following line can return a
> huge number:
> {noformat}
> // Test a split size that is less than record len
> numSplits = (int)(fileSize/Math.floor(recordLength/2));
> {noformat}
> For example, let {{seed}} be 2026428718. This causes {{recordLength}} to be 1
> at iteration 19. {{Math.floor()}} returns negative Infinity, which becomes
> positve infinity after the divison. Casting it to {{int}} yields
> {{Integer.MAX_VALUE}}. Eventually we get an OOME because the test wants to
> create a huge {{InputSplit}} array.
--
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-7054) Configurable task attempt listener bind port range
[ https://issues.apache.org/jira/browse/MAPREDUCE-7054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated MAPREDUCE-7054: -- Summary: Configurable task attempt listener bind port range (was: Yarn task attempt listener bind port range) Moved this to the MAPREDUCE project since this is specific to the MapReduce ApplicationMaster behavior. > Configurable task attempt listener bind port range > -- > > Key: MAPREDUCE-7054 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7054 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: mr-am >Affects Versions: 2.7.5 >Reporter: David Johnson >Priority: Minor > > Currently, the Yarn task attempt listener binds to a random hight port > ".setPort(0)" > For highly locked down environments, this can require a large number of > opened ports between systems, which is troublesome. > > I'd recommend either creating a new configuration item, or tying it to the > MR_AM_JOB_CLIENT_PORT_RANGE. -- 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] [Moved] (MAPREDUCE-7054) Yarn task attempt listener bind port range
[ https://issues.apache.org/jira/browse/MAPREDUCE-7054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe moved YARN-7938 to MAPREDUCE-7054: - Affects Version/s: (was: 2.7.5) 2.7.5 Component/s: (was: yarn) mr-am Key: MAPREDUCE-7054 (was: YARN-7938) Project: Hadoop Map/Reduce (was: Hadoop YARN) > Yarn task attempt listener bind port range > -- > > Key: MAPREDUCE-7054 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7054 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: mr-am >Affects Versions: 2.7.5 >Reporter: David Johnson >Priority: Minor > > Currently, the Yarn task attempt listener binds to a random hight port > ".setPort(0)" > For highly locked down environments, this can require a large number of > opened ports between systems, which is troublesome. > > I'd recommend either creating a new configuration item, or tying it to the > MR_AM_JOB_CLIENT_PORT_RANGE. -- 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-7052) TestFixedLengthInputFormat#testFormatCompressedIn is flaky
[
https://issues.apache.org/jira/browse/MAPREDUCE-7052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16366208#comment-16366208
]
Hadoop QA commented on MAPREDUCE-7052:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
16s{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:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 16m
28s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
26s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
17s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
28s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
9m 40s{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
25s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
15s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
32s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
27s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
27s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
17s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
26s{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}
10m 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
33s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
14s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}132m 23s{color}
| {color:red} hadoop-mapreduce-client-jobclient in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
25s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}173m 45s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.mapreduce.v2.TestMRJobs |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:5b98639 |
| JIRA Issue | MAPREDUCE-7052 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12910774/MAPREDUCE-7052-002.patch
|
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit shadedclient findbugs checkstyle |
| uname | Linux 5b165979d0a6 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precommit/personality/provided.sh |
| git revision | trunk / da59acd |
| maven | version: Apache Maven 3.3.9 |
| Default Java | 1.8.0_151 |
| findbugs | v3.1.0-RC1 |
| unit |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/7343/artifact/out/patch-unit-hadoop-mapreduce-project_hadoop-mapreduce-client_hadoop-mapreduce-client-jobclient.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/7343/testReport/ |
| Max. process+thread count | 1362 (vs. ulimit of 5500) |
| modules | C:
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient
U:
[jira] [Updated] (MAPREDUCE-7052) TestFixedLengthInputFormat#testFormatCompressedIn is flaky
[
https://issues.apache.org/jira/browse/MAPREDUCE-7052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Bacsko updated MAPREDUCE-7052:
Attachment: MAPREDUCE-7052-002.patch
> TestFixedLengthInputFormat#testFormatCompressedIn is flaky
> --
>
> Key: MAPREDUCE-7052
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7052
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client, test
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: MAPREDUCE-7052-001.patch, MAPREDUCE-7052-002.patch
>
>
> Sometimes the test case TestFixedLengthInputFormat#testFormatCompressedIn can
> fail with the following error:
> {noformat}
> java.lang.OutOfMemoryError: Requested array size exceeds VM limit
> at
> org.apache.hadoop.mapred.TestFixedLengthInputFormat.runRandomTests(TestFixedLengthInputFormat.java:322)
> at
> org.apache.hadoop.mapred.TestFixedLengthInputFormat.testFormatCompressedIn(TestFixedLengthInputFormat.java:90)
> {noformat}
> *Root cause:* under special circumstances, the following line can return a
> huge number:
> {noformat}
> // Test a split size that is less than record len
> numSplits = (int)(fileSize/Math.floor(recordLength/2));
> {noformat}
> For example, let {{seed}} be 2026428718. This causes {{recordLength}} to be 1
> at iteration 19. {{Math.floor()}} returns negative Infinity, which becomes
> positve infinity after the divison. Casting it to {{int}} yields
> {{Integer.MAX_VALUE}}. Eventually we get an OOME because the test wants to
> create a huge {{InputSplit}} array.
--
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-7052) TestFixedLengthInputFormat#testFormatCompressedIn is flaky
[
https://issues.apache.org/jira/browse/MAPREDUCE-7052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16365968#comment-16365968
]
Peter Bacsko commented on MAPREDUCE-7052:
-
I updated the patch. This is much simpler - we just have to make sure that we
don't divide by 0.
> TestFixedLengthInputFormat#testFormatCompressedIn is flaky
> --
>
> Key: MAPREDUCE-7052
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7052
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client, test
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: MAPREDUCE-7052-001.patch, MAPREDUCE-7052-002.patch
>
>
> Sometimes the test case TestFixedLengthInputFormat#testFormatCompressedIn can
> fail with the following error:
> {noformat}
> java.lang.OutOfMemoryError: Requested array size exceeds VM limit
> at
> org.apache.hadoop.mapred.TestFixedLengthInputFormat.runRandomTests(TestFixedLengthInputFormat.java:322)
> at
> org.apache.hadoop.mapred.TestFixedLengthInputFormat.testFormatCompressedIn(TestFixedLengthInputFormat.java:90)
> {noformat}
> *Root cause:* under special circumstances, the following line can return a
> huge number:
> {noformat}
> // Test a split size that is less than record len
> numSplits = (int)(fileSize/Math.floor(recordLength/2));
> {noformat}
> For example, let {{seed}} be 2026428718. This causes {{recordLength}} to be 1
> at iteration 19. {{Math.floor()}} returns negative Infinity, which becomes
> positve infinity after the divison. Casting it to {{int}} yields
> {{Integer.MAX_VALUE}}. Eventually we get an OOME because the test wants to
> create a huge {{InputSplit}} array.
--
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-7053) Timed out tasks can fail to produce thread dump
[ https://issues.apache.org/jira/browse/MAPREDUCE-7053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16365521#comment-16365521 ] Peter Bacsko commented on MAPREDUCE-7053: - Patch looks good to me. +1 (non-binding) > Timed out tasks can fail to produce thread dump > --- > > Key: MAPREDUCE-7053 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7053 > Project: Hadoop Map/Reduce > Issue Type: Bug >Affects Versions: 3.1.0, 3.0.1, 2.10.0, 2.9.1, 2.8.4, 2.7.6 >Reporter: Jason Lowe >Assignee: Jason Lowe >Priority: Major > Attachments: MAPREDUCE-7053.001.patch > > > TestMRJobs#testThreadDumpOnTaskTimeout has been failing sporadically > recently. When the AM times out a task it immediately removes it from the > list of known tasks and then connects to the NM to request a thread dump > followed by a kill. If the task heartbeats in after the task has been > removed from the list of known tasks but before the thread dump signal > arrives then the task can exit with a "org.apache.hadoop.mapred.Task: Parent > died." message and no thread dump. -- 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
