Help Center/
MapReduce Service/
Component Operation Guide (LTS)/
Using MapReduce/
Common Issues About MapReduce/
Why Does a MapReduce Task Stay Unchanged for a Long Time?
Updated on 2022-11-18 GMT+08:00
Why Does a MapReduce Task Stay Unchanged for a Long Time?
Question
MapReduce job is not progressing for long time
Answer
This is because of less memory. When the memory is less, the time taken by the job to copy the map output increases significantly.
In order to reduce the waiting time, increase the heap memory.
The job configuration should be tuned according to number of mappers and data size processed by each mapper. Based on the input data size, tune the following configurations accordingly for feasible performance.
- mapreduce.reduce.memory.mb
- mapreduce.reduce.java.opts
Example: If the data size is 5 GB with 10 mappers, then the ideal heap memory would be 1.5 GB. Increase the heap memory size according with the increase in data size.
Parent topic: Common Issues About MapReduce
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
