[jira] [Commented] (MAPREDUCE-6850) Shuffle Handler keep-alive connections are closed from the server side
[ https://issues.apache.org/jira/browse/MAPREDUCE-6850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884074#comment-15884074 ] Rajesh Balamohan commented on MAPREDUCE-6850: - Patch looks good to me. I would need more time for checking in cluster. Got DFSOutputStream timeout exception in the cluster I was trying out (which is not related to this jira) > Shuffle Handler keep-alive connections are closed from the server side > -- > > Key: MAPREDUCE-6850 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6850 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles > Attachments: MAPREDUCE-6850.1.patch, MAPREDUCE-6850.2.patch, > MAPREDUCE-6850.3.patch > > > When performance testing tez shuffle handler (TEZ-3334), it was noticed the > keep-alive connections are closed from the server-side. The client silently > recovers and logs the connection as keep-alive, despite reestablishing a > connection. This jira aims to remove the close from the server side, fixing > the bug preventing keep-alive connections. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-6841) Fix dead link in MapReduce tutorial document
[
https://issues.apache.org/jira/browse/MAPREDUCE-6841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883659#comment-15883659
]
Hadoop QA commented on MAPREDUCE-6841:
--
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 12s
{color} | {color:blue} Docker mode activated. {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} mvninstall {color} | {color:green} 11m
51s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 26s
{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 25s
{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} asflicense {color} | {color:green} 0m
15s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 13m 21s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:a9ad5d6 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12854591/MAPREDUCE-6841.001.patch
|
| JIRA Issue | MAPREDUCE-6841 |
| Optional Tests | asflicense mvnsite |
| uname | Linux 8156a3d71617 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/hadoop/patchprocess/precommit/personality/provided.sh
|
| git revision | trunk / 289bc50 |
| modules | C:
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core
U:
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core |
| Console output |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/6904/console |
| Powered by | Apache Yetus 0.3.0 http://yetus.apache.org |
This message was automatically generated.
> Fix dead link in MapReduce tutorial document
>
>
> Key: MAPREDUCE-6841
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6841
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: documentation
>Reporter: Akira Ajisaka
>Assignee: Victor Nee
>Priority: Minor
> Labels: newbie
> Attachments: MAPREDUCE-6841.001.patch
>
>
> {noformat:title=MapReduceTutorial.md}
> ([FileOutputFormat.setOutputPath(Path)](../../api/org/apache/hadoop/mapreduce/lib/input/FileOutputFormat.html)).
> {noformat}
> input should be output.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Updated] (MAPREDUCE-6841) Fix dead link in MapReduce tutorial document
[
https://issues.apache.org/jira/browse/MAPREDUCE-6841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Victor Nee updated MAPREDUCE-6841:
--
Status: Patch Available (was: Open)
> Fix dead link in MapReduce tutorial document
>
>
> Key: MAPREDUCE-6841
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6841
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: documentation
>Reporter: Akira Ajisaka
>Assignee: Victor Nee
>Priority: Minor
> Labels: newbie
> Attachments: MAPREDUCE-6841.001.patch
>
>
> {noformat:title=MapReduceTutorial.md}
> ([FileOutputFormat.setOutputPath(Path)](../../api/org/apache/hadoop/mapreduce/lib/input/FileOutputFormat.html)).
> {noformat}
> input should be output.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Updated] (MAPREDUCE-6841) Fix dead link in MapReduce tutorial document
[
https://issues.apache.org/jira/browse/MAPREDUCE-6841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Victor Nee updated MAPREDUCE-6841:
--
Attachment: MAPREDUCE-6841.001.patch
> Fix dead link in MapReduce tutorial document
>
>
> Key: MAPREDUCE-6841
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6841
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: documentation
>Reporter: Akira Ajisaka
>Assignee: Victor Nee
>Priority: Minor
> Labels: newbie
> Attachments: MAPREDUCE-6841.001.patch
>
>
> {noformat:title=MapReduceTutorial.md}
> ([FileOutputFormat.setOutputPath(Path)](../../api/org/apache/hadoop/mapreduce/lib/input/FileOutputFormat.html)).
> {noformat}
> input should be output.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-6201) TestNetworkedJob fails on trunk
[
https://issues.apache.org/jira/browse/MAPREDUCE-6201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883610#comment-15883610
]
Robert Kanter commented on MAPREDUCE-6201:
--
I think part of the problem, and this is what we saw in Oozie too, is that
disks are much bigger than they used to be, so a percentage check on disk space
doesn't work as well. For instance, on a 500GB drive, 99% full would mean that
there's 5GB free. While you should probably do some cleanup with only 5GB
free, it should be more than enough space for anything a unit test is going to
do.
Anyway, I think 100 would be best here. If the disk if full, you'll hit all
kinds of other problems first anyway.
> TestNetworkedJob fails on trunk
> ---
>
> Key: MAPREDUCE-6201
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6201
> Project: Hadoop Map/Reduce
> Issue Type: Bug
>Reporter: Robert Kanter
>Assignee: Peter Bacsko
> Attachments: MAPREDUCE-6201-001.patch, MAPREDUCE-6201-002.patch,
> MAPREDUCE-6201-003.patch
>
>
> Currently, {{TestNetworkedJob}} is failing on trunk:
> {noformat}
> Running org.apache.hadoop.mapred.TestNetworkedJob
> Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 215.01 sec
> <<< FAILURE! - in org.apache.hadoop.mapred.TestNetworkedJob
> testNetworkedJob(org.apache.hadoop.mapred.TestNetworkedJob) Time elapsed:
> 67.363 sec <<< FAILURE!
> java.lang.AssertionError: expected:<0> but was:<2>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at
> org.apache.hadoop.mapred.TestNetworkedJob.testNetworkedJob(TestNetworkedJob.java:195)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-6201) TestNetworkedJob fails on trunk
[
https://issues.apache.org/jira/browse/MAPREDUCE-6201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883447#comment-15883447
]
Peter Bacsko commented on MAPREDUCE-6201:
-
I took the value "99" from Oozie, where the disk health check can also cause
hard to debug problems.
What if we set it to 100? Could that help? If the disk is totally full, then it
doesn't really matter anyway.
> TestNetworkedJob fails on trunk
> ---
>
> Key: MAPREDUCE-6201
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6201
> Project: Hadoop Map/Reduce
> Issue Type: Bug
>Reporter: Robert Kanter
>Assignee: Peter Bacsko
> Attachments: MAPREDUCE-6201-001.patch, MAPREDUCE-6201-002.patch,
> MAPREDUCE-6201-003.patch
>
>
> Currently, {{TestNetworkedJob}} is failing on trunk:
> {noformat}
> Running org.apache.hadoop.mapred.TestNetworkedJob
> Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 215.01 sec
> <<< FAILURE! - in org.apache.hadoop.mapred.TestNetworkedJob
> testNetworkedJob(org.apache.hadoop.mapred.TestNetworkedJob) Time elapsed:
> 67.363 sec <<< FAILURE!
> java.lang.AssertionError: expected:<0> but was:<2>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at
> org.apache.hadoop.mapred.TestNetworkedJob.testNetworkedJob(TestNetworkedJob.java:195)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-6201) TestNetworkedJob fails on trunk
[
https://issues.apache.org/jira/browse/MAPREDUCE-6201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883389#comment-15883389
]
Haibo Chen commented on MAPREDUCE-6201:
---
Thanks [~pbacsko] for your patch! While increasing
NM_MAX_PER_DISK_UTILIZATION_PERCENTAGE would definitely make the test less
likely to fail because of NM disks going nearly full, it does not eliminate the
issue completely. I suppose it is a general issue for any test that uses
MiniYarnCluster. I wonder if we can add some message in the assert statements
to make it more explicit to diagnose.
> TestNetworkedJob fails on trunk
> ---
>
> Key: MAPREDUCE-6201
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6201
> Project: Hadoop Map/Reduce
> Issue Type: Bug
>Reporter: Robert Kanter
>Assignee: Peter Bacsko
> Attachments: MAPREDUCE-6201-001.patch, MAPREDUCE-6201-002.patch,
> MAPREDUCE-6201-003.patch
>
>
> Currently, {{TestNetworkedJob}} is failing on trunk:
> {noformat}
> Running org.apache.hadoop.mapred.TestNetworkedJob
> Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 215.01 sec
> <<< FAILURE! - in org.apache.hadoop.mapred.TestNetworkedJob
> testNetworkedJob(org.apache.hadoop.mapred.TestNetworkedJob) Time elapsed:
> 67.363 sec <<< FAILURE!
> java.lang.AssertionError: expected:<0> but was:<2>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at
> org.apache.hadoop.mapred.TestNetworkedJob.testNetworkedJob(TestNetworkedJob.java:195)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Created] (MAPREDUCE-6851) Terasort does not work with S3 FileSystem
Haibo Chen created MAPREDUCE-6851: - Summary: Terasort does not work with S3 FileSystem Key: MAPREDUCE-6851 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6851 Project: Hadoop Map/Reduce Issue Type: Bug Components: examples Affects Versions: 3.0.0-alpha2 Reporter: Haibo Chen Terasort currently writes a partition list file in the output directory and add it to distributed cache. If a S3 bucket is used as the output directory, the job may fail because the partition list file will be localized by NMs which may not have the s3 credentials. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-6814) mapred's FileAlreadyExistsException should be deprecated in favor of hadoop-common's one.
[ https://issues.apache.org/jira/browse/MAPREDUCE-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15882968#comment-15882968 ] Andras Bokor commented on MAPREDUCE-6814: - Hi [~djp], I thought it should be deprecated because in MAPREDUCE-963 the community had a consensus and it was deprecated. Later on another patch (MAPREDUCE-1735/MAPREDUCE-3771) un-deprecated it by *mistake*. MAPREDUCE-963 is a fixed ticket which is not true since the change was "reverted" *accidentally*. Actually MAPREDUCE-963 should have been reopened but I had no reopen option. Mapred's FileAlreadyExistsException has the same functionality as common's one (like duplicated classes). That is why it was deprecated originally. > mapred's FileAlreadyExistsException should be deprecated in favor of > hadoop-common's one. > - > > Key: MAPREDUCE-6814 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6814 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Reporter: Andras Bokor >Assignee: Andras Bokor >Priority: Minor > > Mapred's FileAlreadyExistsException was deprecated with MAPREDUCE-963 but > later on it was un-deprecate with MAPREDUCE-1735/MAPREDUCE-3771 accidentally. > It think it was un-deprecate by mistake: > # MAPREDUCE-963 deprecate FAEE > # Later on the whole Mapreduce 1 API was deprecated > # By MAPREDUCE-1735/MAPREDUCE-3771 Mapred 1 API (including FAEE) was > un-deprecated. > Since FAEE was deprecated regardless of point 2 it shouldn't have been > un-deprecated. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-963) mapred's FileAlreadyExistsException should be deprecated in favor of hadoop-common's one.
[ https://issues.apache.org/jira/browse/MAPREDUCE-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15882971#comment-15882971 ] Andras Bokor commented on MAPREDUCE-963: Unfortunately, MAPREDUCE-1735/MAPREDUCE-3771 undone this change accidentally so mapred's FAEE is no longer deprecated. Pls check MAPREDUCE-6814 for the details. > mapred's FileAlreadyExistsException should be deprecated in favor of > hadoop-common's one. > - > > Key: MAPREDUCE-963 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-963 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 0.21.0 >Reporter: Boris Shkolnik >Assignee: Boris Shkolnik > Fix For: 0.21.0 > > Attachments: MAPREDUCE-963.patch, MAPREDUCE-963.patch > > > We should use org.apache.hadoop.fs.FileAlreadyExistsException instead of > org.apache.hadoop.mapred.FileAlreadyExistsException. > Mapred's one should be deprecated. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Updated] (MAPREDUCE-6814) mapred's FileAlreadyExistsException should be deprecated in favor of hadoop-common's one.
[ https://issues.apache.org/jira/browse/MAPREDUCE-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Bokor updated MAPREDUCE-6814: Description: Mapred's FileAlreadyExistsException was deprecated with MAPREDUCE-963 but later on it was un-deprecate with MAPREDUCE-1735/MAPREDUCE-3771 accidentally. It think it was un-deprecate by mistake: # MAPREDUCE-963 deprecate FAEE # Later on the whole Mapreduce 1 API was deprecated # By MAPREDUCE-1735/MAPREDUCE-3771 Mapred 1 API (including FAEE) was un-deprecated. Since FAEE was deprecated regardless of point 2 it shouldn't have been un-deprecated. was: Mapred's FileAlreadyExistsException was deprecated with MAPREDUCE-963 but later on it was un-deprecate with MAPREDUCE-1735/MAPREDUCE-3771. It think it was un-deprecate by mistake: # MAPREDUCE-963 deprecate FAEE # Later on the whole Mapreduce 1 API was deprecated # By MAPREDUCE-1735/MAPREDUCE-3771 Mapred 1 API (including FAEE) was un-deprecated. Since FAEE was deprecated regardless of point 2 it shouldn't have been un-deprecated. > mapred's FileAlreadyExistsException should be deprecated in favor of > hadoop-common's one. > - > > Key: MAPREDUCE-6814 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6814 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Reporter: Andras Bokor >Assignee: Andras Bokor >Priority: Minor > > Mapred's FileAlreadyExistsException was deprecated with MAPREDUCE-963 but > later on it was un-deprecate with MAPREDUCE-1735/MAPREDUCE-3771 accidentally. > It think it was un-deprecate by mistake: > # MAPREDUCE-963 deprecate FAEE > # Later on the whole Mapreduce 1 API was deprecated > # By MAPREDUCE-1735/MAPREDUCE-3771 Mapred 1 API (including FAEE) was > un-deprecated. > Since FAEE was deprecated regardless of point 2 it shouldn't have been > un-deprecated. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Updated] (MAPREDUCE-6814) mapred's FileAlreadyExistsException should be deprecated in favor of hadoop-common's one.
[ https://issues.apache.org/jira/browse/MAPREDUCE-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Bokor updated MAPREDUCE-6814: Description: Mapred's FileAlreadyExistsException was deprecated with MAPREDUCE-963 but later on it was un-deprecate with MAPREDUCE-1735/MAPREDUCE-3771. It think it was un-deprecate by mistake: # MAPREDUCE-963 deprecate FAEE # Later on the whole Mapreduce 1 API was deprecated # By MAPREDUCE-1735/MAPREDUCE-3771 Mapred 1 API (including FAEE) was un-deprecated. Since FAEE was deprecated regardless of point 2 it shouldn't have been un-deprecated. was: Mapred's FileAlreadyExistsException was deprecated with MAPREDUCE-963 but later on it was un-deprecate with MAPREDUCE-1735/MAPREDUCE-3771. It think it was un-deprecate by mistake: # MAPREDUCE-963 un-deprecate FAEE # Later on the whole Mapreduce 1 API was deprecated # By MAPREDUCE-1735/MAPREDUCE-3771 Mapred 1 API (including FAEE) was un-deprecated. Since FAEE was deprecated regardless of point 2 it shouldn't have been un-deprecated. > mapred's FileAlreadyExistsException should be deprecated in favor of > hadoop-common's one. > - > > Key: MAPREDUCE-6814 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6814 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Reporter: Andras Bokor >Assignee: Andras Bokor >Priority: Minor > > Mapred's FileAlreadyExistsException was deprecated with MAPREDUCE-963 but > later on it was un-deprecate with MAPREDUCE-1735/MAPREDUCE-3771. > It think it was un-deprecate by mistake: > # MAPREDUCE-963 deprecate FAEE > # Later on the whole Mapreduce 1 API was deprecated > # By MAPREDUCE-1735/MAPREDUCE-3771 Mapred 1 API (including FAEE) was > un-deprecated. > Since FAEE was deprecated regardless of point 2 it shouldn't have been > un-deprecated. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-6850) Shuffle Handler keep-alive connections are closed from the server side
[ https://issues.apache.org/jira/browse/MAPREDUCE-6850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15882248#comment-15882248 ] Rajesh Balamohan commented on MAPREDUCE-6850: - Thanks for the patch [~jeagles]. I am getting a small cluster today/tomorrow. I will check the patch and will update. > Shuffle Handler keep-alive connections are closed from the server side > -- > > Key: MAPREDUCE-6850 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6850 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles > Attachments: MAPREDUCE-6850.1.patch, MAPREDUCE-6850.2.patch, > MAPREDUCE-6850.3.patch > > > When performance testing tez shuffle handler (TEZ-3334), it was noticed the > keep-alive connections are closed from the server-side. The client silently > recovers and logs the connection as keep-alive, despite reestablishing a > connection. This jira aims to remove the close from the server side, fixing > the bug preventing keep-alive connections. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
