get progress from right db

[areshand]

Description

after sharding enabled, we need to get the progress from right db to resume restoring

How Has This Been Tested?

Key Areas to Review

Type of Change

• New feature
• Bug fix
• Breaking change
• Performance improvement
• Refactoring
• Dependency update
• Documentation update
• Tests

Which Components or Systems Does This Change Impact?

• Validator Node
• Full Node (API, Indexer, etc.)
• Move/Aptos Virtual Machine
• Aptos Framework
• Aptos CLI/SDK
• Developer Infrastructure
• Move Compiler
• Other (specify)

Checklist

• I have read and followed the CONTRIBUTING doc
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I identified and added all stakeholders and component owners affected by this change as reviewers
• I tested both happy and unhappy path of the functionality
• I have made corresponding changes to the documentation

[trunk-io]

⏱️ 1h 46m total CI duration on this PR

Slowest 15 Jobs	Cumulative Duration	Recent Runs
execution-performance / single-node-performance	32m	🟥 🟩
rust-move-tests	13m	🟩
rust-move-tests	13m	🟩
rust-move-tests	12m	🟩
check-dynamic-deps	7m	🟩 🟩 🟩
rust-doc-tests	5m	🟩
rust-cargo-deny	5m	🟩 🟩 🟩
execution-performance / test-target-determinator	5m	🟩
test-target-determinator	4m	🟩
check	4m	🟩
general-lints	2m	🟩 🟩 🟩
semgrep/ci	1m	🟩 🟩 🟩
fetch-last-released-docker-image-tag	1m	🟥
file_change_determinator	33s	🟩 🟩 🟩
file_change_determinator	10s	🟩

🚨 1 job on the last run was significantly faster/slower than expected

Job	Duration	vs 7d avg	Delta
execution-performance / single-node-performance	26m	17m

_{settings ⋅ feedback ⋅ docs ⋅ learn more about trunk.io}

[github-actions]

✅ Forge suite realistic_env_max_load success on a3583cac74df750f55797bdcff66d3d1385be9d1

two traffics test: inner traffic : committed: 14143.73 txn/s, latency: 2808.92 ms, (p50: 2700 ms, p70: 2700, p90: 3000 ms, p99: 5200 ms), latency samples: 5377740
two traffics test : committed: 99.96 txn/s, latency: 2284.93 ms, (p50: 2000 ms, p70: 2100, p90: 2400 ms, p99: 16100 ms), latency samples: 1800
Latency breakdown for phase 0: ["MempoolToBlockCreation: max: 2.191, avg: 1.248", "ConsensusProposalToOrdered: max: 0.324, avg: 0.292", "ConsensusOrderedToCommit: max: 0.377, avg: 0.364", "ConsensusProposalToCommit: max: 0.665, avg: 0.657"]
Max non-epoch-change gap was: 0 rounds at version 0 (avg 0.00) [limit 4], 0.60s no progress at version 2095996 (avg 0.20s) [limit 15].
Max epoch-change gap was: 0 rounds at version 0 (avg 0.00) [limit 4], 15.62s no progress at version 2095994 (avg 14.24s) [limit 16].
Test Ok

• Grafana dashboard
• Humio Logs
• Axiom Logs
• Validator CPU Profile
• Fullnode CPU Profile
• Test runner output
• Test run is land-blocking