Help Center/ MapReduce Service/ Component Operation Guide (LTS)/ Using CarbonData/ Common Issues About CarbonData/ Why Data Load Performance Decreases due to Bad Records?

Updated on 2024-12-13 GMT+08:00

View PDF

Why Data Load Performance Decreases due to Bad Records?

Question

Why data load performance decreases due to bad records?

Answer

The loaded data contains Bad Records, and the value of BAD_RECORDS_LOGGER_ENABLE is true or BAD_RECORDS_ACTION is redirect.

Data load performance degrades due to additional I/O overhead caused by writing failure causes to the log file or redirecting Bad Records to the original CSV file.

Parent topic: Common Issues About CarbonData

Previous topic: Why Is the Data Logged in Bad Records Different from the Original Input Data with Escape Characters?

Next topic: Why Data loading Fails During off heap?

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank 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.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.