Help Center/
MapReduce Service/
User Guide (Paris Region)/
Troubleshooting/
Using Flume/
Flume Data Collection Is Slow
Updated on 2024-10-11 GMT+08:00
Flume Data Collection Is Slow
Symptom
After Flume is started, it takes a long time for Flume to collect data.
Cause Analysis
- The heap memory of Flume is not properly set. As a result, the Flume process keeps in the GC state. View Flume run logs.
2019-02-26T13:06:20.666+0800: 1085673.512: [Full GC:[CMS: 3849339k->3843458K(3853568K), 2.5817610 secs] 4153654K->3843458K(4160256K), [CMS Perm : 27335K->27335K(45592K),2.5820080 SECS] [Times: user=2.63, sys0.00, real=2.59 secs]
- The deletePolicy policy configured for the Spooldir source is immediate.
Solution
- Increase the size of the heap memory (xmx).
- Change the deletePolicy policy of the Spooldir source to never.
Parent topic: Using Flume
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot