for 2 hrs. till
the time it was manually killed? If it wasn’t killed it would have
continued for much longer.
Why did AM not stop trying after x number of tries? Is there any max
attempt properties for application master?
Why did AM not spin out another map task to compensate for this problematic
t
I am getting an issue on a production cluster where Mapreduce Job taking
long time in reduce phase while running a Hive query, approximately 2 hrs
for one reduce task.
Hardware specification of the cluster :
Number of nodes:22
Number of Master nodes4
Number of data nodes:18
Core per nodes:24
