Help Center/
MapReduce Service/
User Guide (Paris Region)/
Troubleshooting/
Using HDFS/
After dfs.blocksize Is Configured and Data Is Put, Block Size Remains Unchanged
Updated on 2024-10-11 GMT+08:00
After dfs.blocksize Is Configured and Data Is Put, Block Size Remains Unchanged
Symptom
After dfs.blocksize is set to 268435456 on the interface and data is put, the original block size keeps unchanged.
Cause Analysis
The dfs.blocksize value in the hdfs-site.xml file of the client is not changed, and the value prevails.
Solution
- Ensure that the dfs.blocksize value is a multiple of 512.
- Download a client or modify the client configuration.
- dfs.blocksize is configured on the client and is subject to the client. Otherwise, the value configured on the server prevails.
Parent topic: Using HDFS
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