cassandra java driver 3.6版本，当请求发生OverloadedException异常时，发现有重试机制。未显示配置重试策略。
对于默认重试策略，java driver的重试机制和重试次数分别是什么？其他语言的driver(python, go等)的重试机制和java的相同吗？不同的话重试次数和机制分别是什么
Bringing together the Apache Cassandra experts from the community and DataStax.
Want to learn? Have a question? Want to share your expertise? You are in the right place!
Not sure where to begin? Getting Started
When the driver runs a query, the configured load balancing policy computes a query plan (a list of nodes to connect to). The driver tries each of the hosts in the query plan based on the retry policy.
If a coordinator can't be reached or returns an error, the driver will either:
In the case where the coordinator returns an
OverloadedException, the DefaultRetryPolicy will retry the request on the next node in the query plan.
The number of retries isn't fixed since it depends on the outcome of each attempt.
In general, the retry mechanism is the same for DataStax drivers but I can't comment on other drivers such as GoCQL since it is not maintained by DataStax.
For more details, see the Java driver 3.6 Retry Policy. Cheers!
6 People are following this question.