Exception Handling

Last Updated：2020-07-20

Server Exception Handling

Exception in uploading to BOS through multiple steps

When the last part of the multiupload uploaded to BOS is completed, the finishUpload is called; due to multi-threading, multiple parts of the same file may not be completed before the last part completes, and may fail before finishUpload is called. The strategy to deal with this problem is: To redo for 5 times, with the interval of 20 seconds each time, and abort the parts that have been completed after you redo for 5 times and fail.

Suggestions: When you redo for 5 times but fail, you can adjust the blockSize as large as possible to reduce the total number of the parts.

When the server is not available, the client can immediately find that it is not available on the first attempt to send the migration request to the server, and records such request as unsent, and marks the server as unavailable, and the subsequent requests are not sent to such server. If the server is determined to be fixed, you can touch the configuration file client.properties of client, and trigger to reload the client configuration; you are recommended to set a crontab to touch the configuration file client.properties regularly.
When the client reaches the limit of the number of fd (socket fd) distributed by the system, check if filesPerrequet is too small; if it is determined that this is the cause, it needs to be increased appropriately, kill all servers (or make all servers "out of contact" with client), and then touch the configuration file of client again after most of the socket fd occupied are released.