RetryPolicy

How often a client sends a request again that a peer answered with a problem a retry may get past, each time after the Retry-After the peer answered with, else after backoff doubled at each attempt:

• a 429 (wow.command.busy, wow.query.busy), when its Retry-After is at most maxRetryAfter; a peer that asks for a longer wait is not retried, its problem is the caller's;

• a command's problem that keeps the request id (wow.command.unknown, wow.storage.unavailable, wow.node.closing, wow.command.contended, ...): sent again with the same Wow-Request-Id, so the peer answers a command that did commit as the duplicate it is;

• a connection that could not be made: nothing was sent.

Never a 504 (wow.wait.timeout, whose command may have committed and goes on; wow.query.timeout), nor any other problem. At most maxAttempts attempts in all; 1 never retries (NONE).