HDDS-1909. Use new HA code for Non-HA in OM.#1225
HDDS-1909. Use new HA code for Non-HA in OM.#1225bharatviswa504 merged 4 commits intoapache:trunkfrom
Conversation
76af6ab to
6169be1
Compare
c18a1e0 to
5ebb33f
Compare
|
/retest |
|
/retest |
338776d to
a425167
Compare
|
/retest |
There was a problem hiding this comment.
The only potential issue is if we update the cache but fail to update RocksDB. In that case self-terminate is likely the best option. Since Ratis is not enabled the request is not persistent.
There was a problem hiding this comment.
So, terminate OM here?
There was a problem hiding this comment.
Yes I would err on the side of safety and self-terminate the OM here.
4db799d to
476407f
Compare
|
Thank You @arp7 for the review. |
|
/retest |
476407f to
9a74db9
Compare
|
Fixed s3 test failure. |
|
/retest |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
Thanks @bharatviswa504. The patch looks pretty good to me. +1 One remaining point was to self-terminate the OM in the RocksDB update failure path. It can be done in a separate jira. |
|
+1 to commit assuming the integration test failures are unrelated. |
|
Thank You @arp7 for the review. |
|
Opened jira's HDDS-2078 and HDDS-2079 for secure cluster test failures. |
No description provided.