[IOTDB-6336] Add configuration to control max retry count and whether to rety for unknown errors

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Core/Engine
• Labels: pull-request-available
• Assignee: Yuan Tian Assign to me
• Reporter: Yuan Tian
• Created: 03/Jun/24 03:12
• Updated: 04/Jun/24 09:10

Description

Now when encountering dispatch error while sending write request to a remote datanode, we will retry while receiving the following TSStatusCode

However, for some unknown errors like 301 and 305, we may not need to retry for it in some case.

 

And previously we use the max retry count which is always 10(hard code) to control the retry limit but for user, a changable max retry time duration may be more friendly.

 

And we want both the above two new added confiugration can be hot loaded. 

Issue Links

• links to: GitHub Pull Request #12638
• links to: https://github.com/apache/iotdb/pull/12638