[jira] [Commented] (MAPREDUCE-3919) Redirecting to job history server takes hours
[ https://issues.apache.org/jira/browse/MAPREDUCE-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14742323#comment-14742323 ] mingleizhang commented on MAPREDUCE-3919: - I have the same question. How do you solve it ? > Redirecting to job history server takes hours > - > > Key: MAPREDUCE-3919 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3919 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 >Affects Versions: 0.23.0 >Reporter: Daniel Dai >Priority: Critical > > Saw the following message happening regularly, the job end up success, but > reconnecting job history server takes a long time (>10 hours sometimes). > 2012-02-24 03:49:05,226 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: hrt11n31.cc1.ygridcore.net/98.137.234.159:44716. Already > tried 0 time(s). > 2012-02-24 03:49:05,229 [main] INFO > org.apache.hadoop.mapred.ClientServiceDelegate - Application state is > completed. FinalApplicationStatus=SUCCEEDED. Redirecting to job history server > 2012-02-24 03:49:06,233 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 0 time(s). > 2012-02-24 03:49:07,236 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 1 time(s). > 2012-02-24 03:49:08,239 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 2 time(s). > 2012-02-24 03:49:09,242 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 3 time(s). > 2012-02-24 03:49:10,245 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 4 time(s). > 2012-02-24 03:49:11,248 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 5 time(s). > 2012-02-24 03:49:12,251 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 6 time(s). > 2012-02-24 03:49:13,254 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 7 time(s). > 2012-02-24 03:49:14,257 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 8 time(s). > 2012-02-24 03:49:15,260 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 9 time(s). > .. > 2012-02-24 18:10:35,711 [main] INFO > org.apache.hadoop.mapred.ClientServiceDelegate - Application state is > completed. FinalApplicationStatus=SUCCEEDED. Redirecting to job history server > 2012-02-24 18:10:36,714 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 0 time(s). > 2012-02-24 18:10:37,717 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 1 time(s).2012-02-24 > 18:10:38,784 [main] INFO org.apache.hadoop.ipc.Client - Retrying connect to > server: 0.0.0.0/0.0.0.0:10020. Already tried 2 time(s).2012-02-24 > 18:10:39,787 [main] INFO org.apache.hadoop.ipc.Client - Retrying connect to > server: 0.0.0.0/0.0.0.0:10020. Already tried 3 time(s). > 2012-02-24 18:10:40,791 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 4 time(s). > 2012-02-24 18:10:41,793 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 5 time(s).2012-02-24 > 18:10:42,796 [main] INFO org.apache.hadoop.ipc.Client - Retrying connect to > server: 0.0.0.0/0.0.0.0:10020. Already tried 6 time(s).2012-02-24 > 18:10:43,799 [main] INFO org.apache.hadoop.ipc.Client - Retrying connect to > server: 0.0.0.0/0.0.0.0:10020. Already tried 7 time(s). > 2012-02-24 18:10:44,802 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 8 time(s). > 2012-02-24 18:10:45,805 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 9 time(s). > 2012-02-24 18:10:45,808 [main] INFO > org.apache.hadoop.mapred.ClientServiceDelegate - Application state is > completed. FinalApplicationStatus=SUCCEEDED. Redirecting to job history server > 2012-02-24 18:10:46,810 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 0 time(s).2012-02-24 > 18:10:47,813 [main] INFO org.apache.hadoop.ipc.Client - Retrying connect to > server: 0.0.0.0/0.0.0.0:10020. Already tried 1 time(s).2012-02-24 > 18:10:48,815 [main] INFO org.apache.hadoop.ipc.Client - Retrying c
[jira] [Commented] (MAPREDUCE-3919) Redirecting to job history server takes hours
[ https://issues.apache.org/jira/browse/MAPREDUCE-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14742324#comment-14742324 ] mingleizhang commented on MAPREDUCE-3919: - I have the same question. How do you solve it ? > Redirecting to job history server takes hours > - > > Key: MAPREDUCE-3919 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3919 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 >Affects Versions: 0.23.0 >Reporter: Daniel Dai >Priority: Critical > > Saw the following message happening regularly, the job end up success, but > reconnecting job history server takes a long time (>10 hours sometimes). > 2012-02-24 03:49:05,226 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: hrt11n31.cc1.ygridcore.net/98.137.234.159:44716. Already > tried 0 time(s). > 2012-02-24 03:49:05,229 [main] INFO > org.apache.hadoop.mapred.ClientServiceDelegate - Application state is > completed. FinalApplicationStatus=SUCCEEDED. Redirecting to job history server > 2012-02-24 03:49:06,233 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 0 time(s). > 2012-02-24 03:49:07,236 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 1 time(s). > 2012-02-24 03:49:08,239 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 2 time(s). > 2012-02-24 03:49:09,242 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 3 time(s). > 2012-02-24 03:49:10,245 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 4 time(s). > 2012-02-24 03:49:11,248 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 5 time(s). > 2012-02-24 03:49:12,251 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 6 time(s). > 2012-02-24 03:49:13,254 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 7 time(s). > 2012-02-24 03:49:14,257 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 8 time(s). > 2012-02-24 03:49:15,260 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 9 time(s). > .. > 2012-02-24 18:10:35,711 [main] INFO > org.apache.hadoop.mapred.ClientServiceDelegate - Application state is > completed. FinalApplicationStatus=SUCCEEDED. Redirecting to job history server > 2012-02-24 18:10:36,714 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 0 time(s). > 2012-02-24 18:10:37,717 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 1 time(s).2012-02-24 > 18:10:38,784 [main] INFO org.apache.hadoop.ipc.Client - Retrying connect to > server: 0.0.0.0/0.0.0.0:10020. Already tried 2 time(s).2012-02-24 > 18:10:39,787 [main] INFO org.apache.hadoop.ipc.Client - Retrying connect to > server: 0.0.0.0/0.0.0.0:10020. Already tried 3 time(s). > 2012-02-24 18:10:40,791 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 4 time(s). > 2012-02-24 18:10:41,793 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 5 time(s).2012-02-24 > 18:10:42,796 [main] INFO org.apache.hadoop.ipc.Client - Retrying connect to > server: 0.0.0.0/0.0.0.0:10020. Already tried 6 time(s).2012-02-24 > 18:10:43,799 [main] INFO org.apache.hadoop.ipc.Client - Retrying connect to > server: 0.0.0.0/0.0.0.0:10020. Already tried 7 time(s). > 2012-02-24 18:10:44,802 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 8 time(s). > 2012-02-24 18:10:45,805 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 9 time(s). > 2012-02-24 18:10:45,808 [main] INFO > org.apache.hadoop.mapred.ClientServiceDelegate - Application state is > completed. FinalApplicationStatus=SUCCEEDED. Redirecting to job history server > 2012-02-24 18:10:46,810 [main] INFO org.apache.hadoop.ipc.Client - Retrying > connect to server: 0.0.0.0/0.0.0.0:10020. Already tried 0 time(s).2012-02-24 > 18:10:47,813 [main] INFO org.apache.hadoop.ipc.Client - Retrying connect to > server: 0.0.0.0/0.0.0.0:10020. Already tried 1 time(s).2012-02-24 > 18:10:48,815 [main] INFO org.apache.hadoop.ipc.Client - Retrying c
[jira] [Commented] (MAPREDUCE-6471) Document distcp incremental copy
[
https://issues.apache.org/jira/browse/MAPREDUCE-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14742297#comment-14742297
]
Neelesh Srinivas Salian commented on MAPREDUCE-6471:
I would like to work on this JIRA.
Could you please assign it to me?
Thank you.
> Document distcp incremental copy
> -
>
> Key: MAPREDUCE-6471
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6471
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: distcp
>Affects Versions: 2.7.1
>Reporter: Arpit Agarwal
>Assignee: nijel
> Labels: newbie
>
> MAPREDUCE-5899 added distcp support for incremental copy with a new
> {{append}} flag.
> It should be documented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6423) MapOutput Sampler
[ https://issues.apache.org/jira/browse/MAPREDUCE-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14742215#comment-14742215 ] Ram Manohar Bheemana commented on MAPREDUCE-6423: - Sorry for delay in response, will try to generate the patch as suggested. > MapOutput Sampler > - > > Key: MAPREDUCE-6423 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6423 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Reporter: Ram Manohar Bheemana >Assignee: Ram Manohar Bheemana >Priority: Minor > Attachments: MapOutputSampler.java > > > Need a sampler based on the MapOutput Keys. Current InputSampler > implementation has a major drawback which is input and output of a mapper > should be same, generally this isn't the case. > approach: > 1. Create a Sampler which samples the data based on the input. > 2. Run a small map reduce in uber task mode using the original job mapper and > identity reducer to generate required MapOutputSample keys > 3. Optionally, we can input the input file to be sample. For example inputs > files A, B; we should be able to specify to use only file A for sampling. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
