You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently only have one standby archival node in the event that the mobile infrastructure needs to failover.
Should the primary archival node fail, we wont have another node to failover to and this shouldn't be the case.
Solution
Add an additional standby archival node that will serve as a failover for the primary archival node for mobile global infrastructure.
Dependencies
Acceptance criteria
Test that the primary archival node can failover to the secondary (created in this ticket) without any issues and confirm the failover time.
Urgency
The text was updated successfully, but these errors were encountered:
Maybe needs a little bit of clarification. Our archival node is currently on the kubernetes cluster. Where do we plan to set up the standby archival node?
Problem
We currently only have one standby archival node in the event that the mobile infrastructure needs to failover.
Should the primary archival node fail, we wont have another node to failover to and this shouldn't be the case.
Solution
Add an additional standby archival node that will serve as a failover for the primary archival node for mobile global infrastructure.
Dependencies
Acceptance criteria
Test that the primary archival node can failover to the secondary (created in this ticket) without any issues and confirm the failover time.
Urgency
The text was updated successfully, but these errors were encountered: