-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Add Incremental Snapshot support to RPC #19559
Conversation
Is there a reason to have three methods here? It seems like just Aside: I don't love the name |
Good point. I this will likely come down to desired usage. I can see two use cases:
Use-case 1 may not be all that valuable though. If a node OK, I'm on board with just having a single RPC function!
Yeah, the name sucks. How about one of these:
I'm in favor of |
How about: |
Oh, also lets turn the response from |
Codecov Report
@@ Coverage Diff @@
## master #19559 +/- ##
=======================================
Coverage 82.6% 82.7%
=======================================
Files 461 461
Lines 131212 131249 +37
=======================================
+ Hits 108483 108557 +74
+ Misses 22729 22692 -37 |
#### Problem There's no way to get incremental snapshot information from RPC. #### Summary of Changes - Add new RPC method, `getHighestSnapshotSlot` that returns a `SnapshotSlotInfo`, which contains both the highest full snapshot slot, and the highest incremental snapshot slot _based on_ the full snapshot. - Deprecate old RPC method, `getSnapshotSlot` - Update API docs Fixes solana-labs#19579
#### Problem There's no way to get incremental snapshot information from RPC. #### Summary of Changes - Add new RPC method, `getHighestSnapshotSlot` that returns a `SnapshotSlotInfo`, which contains both the highest full snapshot slot, and the highest incremental snapshot slot _based on_ the full snapshot. - Deprecate old RPC method, `getSnapshotSlot` - Update API docs Fixes solana-labs#19579
This reverts commit 07edc59.
Problem
There's no way to get incremental snapshot information from RPC.
Summary of Changes
getHighestSnapshotSlot
that returns aSnapshotSlotInfo
, which contains both the highest full snapshot slot, and the highest incremental snapshot slot based on the full snapshot.getSnapshotSlot
Fixes #19579