[RPC Gateway] Enable auto fallback and recovery on Sepolia #625
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @rollingtumbling and the rest of your teammates on |
rollingtumbling
force-pushed
the
0423_sepolia_auto_fallback_recover
branch
from
355743b to
0707a08
Compare
rollingtumbling
force-pushed
the
0423_sepolia_auto_fallback_recover
branch
from
0707a08 to
fa30c1b
Compare
jsy1218
approved these changes
Apr 24, 2024
rollingtumbling
force-pushed
the
0423_sepolia_auto_fallback_recover
branch
from
fa30c1b to
53c093f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After the deployment of #583 and #629, we are ready to test auto fallback and recover in production.
The first chain we want to test is Sepolia because it's a testnet with small but meaningful amount of traffic. Even if we bring it down, the cost is still acceptable.
According to the prod alarm data, if we enable it for Sepolia, this is the only alarm that will possibly trigger: The latency alarm for Alchemy-Sepolia pair (Showing data from the last 24h, https://us-east-2.console.aws.amazon.com/cloudwatch/home?region=us-east-2#metricsV2?graph=~(metrics~(~(~(id~'expr_1~expression~'p50Latency))~(~'Uniswap~'RPC_GATEWAY_11155111_ALCHEMY_evaluated_latency_getBlockNumber~'Service~'RoutingAPI~(stat~'p50~id~'p50Latency~visible~false~unit~'None)))~view~'timeSeries~stacked~false~start~'-PT24H~end~'P0D~period~300~region~'us-east-2~title~'RoutingAPI-RpcGateway-LatencyAlarm-ChainId-11155111-Provider-ALCHEMY~annotations~(horizontal~(~(label~'expr_1*20*3e*3d*20150*20for*201*20datapoints*20within*205*20minutes~value~150)))))))
So this flip of alarm should make the provider switch between Alchemy (primary provider) and Infura (backup). We should be able to observe it from the "Provider selection for sepolia" graph in dashboard
There is a small concern that Alchemy couldn't handle the doubled traffic caused by this PR (50% => 100%, because of it becoming primary). However since the quote traffic on Sepolia is indeed very small, we don't really expect an issue there.