ARSN-495: KMIP retries#2397
Conversation
BourgoisMickael
commented
May 19, 2025
- Retry internally for thales session token revoked
- Blacklist unhealthy hosts (hosts that return error) and add retry mechanism in kmip cluster
Hello bourgoismickael,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command: Alternatively, the |
571f461 to
7f10726
Compare
anurag4DSB
left a comment
There was a problem hiding this comment.
Should we add a blacklist mechanism so for an unhealthy node further requests are not forwarded.
anurag4DSB
left a comment
There was a problem hiding this comment.
Approving but some comments improvement is needed for context.
7f10726 to
3503526
Compare
|
/approve |
ConflictA conflict has been raised during the creation of I have not created the integration branch. Here are the steps to resolve this conflict: $ git fetch
$ git checkout -B w/8.1/improvement/ARSN-495-kmip-retry origin/development/8.1
$ git merge origin/improvement/ARSN-495-kmip-retry
$ # <intense conflict resolution>
$ git commit
$ git push -u origin w/8.1/improvement/ARSN-495-kmip-retryThe following options are set: approve |
ConflictA conflict has been raised during the creation of I have not created the integration branch. Here are the steps to resolve this conflict: $ git fetch
$ git checkout -B w/8.2/improvement/ARSN-495-kmip-retry origin/development/8.2
$ git merge origin/w/8.1/improvement/ARSN-495-kmip-retry
$ # <intense conflict resolution>
$ git commit
$ git push -u origin w/8.2/improvement/ARSN-495-kmip-retryThe following options are set: approve |
Build failedThe build for commit did not succeed in branch w/8.2/improvement/ARSN-495-kmip-retry The following options are set: approve |
To avoid logging all debug and trace on cluster retry if one host is unhealthy
3503526 to
0ef69d3
Compare
History mismatchMerge commit #89a4a1d801a0be07eea2188f0d13909a8f7d14ba on the integration branch It is likely due to a rebase of the branch Please use the The following options are set: approve |
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue ARSN-495. Goodbye bourgoismickael. The following options are set: approve |