Moreover, the IP 10.224.174.71 is a different node, not the one executing
the reduce task. Why did that happen?
On Fri, Oct 20, 2017 at 3:37 PM, Daniel Bruce <dbse...@gmail.com> wrote:
> OK, more updates. Today I was running the query with Yarn and also turned
> on DEBUG logging. H
value #10
2017-10-20 13:43:36,165 DEBUG [communication thread]
org.apache.hadoop.ipc.RPC: Call: ping 1
...
...
On Thu, Oct 19, 2017 at 11:35 PM, Daniel Bruce <dbse...@gmail.com> wrote:
> Hi Gopal,
>
> Thanks for your input! In my case I'm using MapReduce not Tez. I figured
>
Hi Gopal,
Thanks for your input! In my case I'm using MapReduce not Tez. I figured
I'd better be more specific so as to provide you more details.
For this job there are 298 maps and 74 reduces. All the maps completed real
fast within 1 minute, and 73 reduces completed in about 2 minutes.
Now
Hi Feng,
I've seen exactly same problem with one of my queries. There is one reducer
hanging forever. I didn't see data skew for that reducer. It has similar
amount of REDUCE_INPUT_RECORDS as other reducers. But this number stopped
changing any more and just hanging..
Does anybody else know
