Get right most child

[areshand]

Description

When restoring sharded db is in progress, we may haven't write the root node of the sharded JMT when being interrupted.
we still want to get the rightmost child in this case to continue restoring.

How Has This Been Tested?

added unit test

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]

⏱️ 4h 30m total CI duration on this PR

Slowest 15 Jobs	Cumulative Duration	Recent Runs
execution-performance / single-node-performance	1h 9m	🟩 🟩 🟥
rust-cargo-deny	24m	🟩 🟩 🟩 🟩 🟩 (+11 more)
check-dynamic-deps	17m	🟩 🟩 🟩 🟩 🟩 (+11 more)
test-target-determinator	15m	🟩 🟩 🟩
execution-performance / test-target-determinator	14m	🟩 🟩 🟩
check	11m	🟩 🟩 🟩
rust-move-tests	10m	🟩
rust-move-tests	10m	🟩
rust-move-tests	10m	🟩
rust-move-tests	10m	🟩
rust-move-tests	9m	🟩
rust-move-tests	9m	🟩
rust-move-tests	9m	🟩
general-lints	7m	🟩 🟩 🟩 🟩 🟩 (+11 more)
semgrep/ci	6m	🟩 🟩 🟩 🟩 🟩 (+11 more)

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

Job	Duration	vs 7d avg	Delta
test-target-determinator	6m	4m

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

[msmouse]

remove? (we generally don't commit these)

[github-actions]

✅ Forge suite realistic_env_max_load success on c6b9b28210348ce5140cffe30afcfef29d84aefb

two traffics test: inner traffic : committed: 13305.91 txn/s, latency: 2986.68 ms, (p50: 2700 ms, p70: 3000, p90: 3300 ms, p99: 7400 ms), latency samples: 5059220
two traffics test : committed: 99.97 txn/s, latency: 2547.55 ms, (p50: 2500 ms, p70: 2600, p90: 2700 ms, p99: 8600 ms), latency samples: 1740
Latency breakdown for phase 0: ["QsBatchToPos: max: 0.242, avg: 0.222", "QsPosToProposal: max: 0.602, avg: 0.316", "ConsensusProposalToOrdered: max: 0.331, avg: 0.307", "ConsensusOrderedToCommit: max: 0.512, avg: 0.459", "ConsensusProposalToCommit: max: 0.814, avg: 0.767"]
Max non-epoch-change gap was: 1 rounds at version 3096313 (avg 0.00) [limit 4], 1.90s no progress at version 3107876 (avg 0.21s) [limit 15].
Max epoch-change gap was: 0 rounds at version 0 (avg 0.00) [limit 4], 8.14s no progress at version 1851932 (avg 7.41s) [limit 15].
Test Ok

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

[github-actions]

✅ Forge suite framework_upgrade success on 46bf19eb4f132b9d8fc19eff3f3334cdf9aa1775 ==> c6b9b28210348ce5140cffe30afcfef29d84aefb

Compatibility test results for 46bf19eb4f132b9d8fc19eff3f3334cdf9aa1775 ==> c6b9b28210348ce5140cffe30afcfef29d84aefb (PR)
Upgrade the nodes to version: c6b9b28210348ce5140cffe30afcfef29d84aefb
framework_upgrade::framework-upgrade::full-framework-upgrade : committed: 1090.85 txn/s, submitted: 1092.27 txn/s, failed submission: 1.42 txn/s, expired: 1.42 txn/s, latency: 3270.57 ms, (p50: 2400 ms, p70: 3200, p90: 5400 ms, p99: 14200 ms), latency samples: 92160
framework_upgrade::framework-upgrade::full-framework-upgrade : committed: 1114.75 txn/s, submitted: 1118.82 txn/s, failed submission: 4.06 txn/s, expired: 4.06 txn/s, latency: 2707.43 ms, (p50: 2400 ms, p70: 3000, p90: 4600 ms, p99: 5700 ms), latency samples: 98760
5. check swarm health
Compatibility test for 46bf19eb4f132b9d8fc19eff3f3334cdf9aa1775 ==> c6b9b28210348ce5140cffe30afcfef29d84aefb passed
Upgrade the remaining nodes to version: c6b9b28210348ce5140cffe30afcfef29d84aefb
framework_upgrade::framework-upgrade::full-framework-upgrade : committed: 1227.11 txn/s, submitted: 1229.34 txn/s, failed submission: 2.24 txn/s, expired: 2.24 txn/s, latency: 2600.79 ms, (p50: 2400 ms, p70: 2700, p90: 4200 ms, p99: 5800 ms), latency samples: 109700
Test Ok

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

[github-actions]

✅ Forge suite compat success on 46bf19eb4f132b9d8fc19eff3f3334cdf9aa1775 ==> c6b9b28210348ce5140cffe30afcfef29d84aefb

Compatibility test results for 46bf19eb4f132b9d8fc19eff3f3334cdf9aa1775 ==> c6b9b28210348ce5140cffe30afcfef29d84aefb (PR)
1. Check liveness of validators at old version: 46bf19eb4f132b9d8fc19eff3f3334cdf9aa1775
compatibility::simple-validator-upgrade::liveness-check : committed: 12472.73 txn/s, latency: 2726.87 ms, (p50: 1800 ms, p70: 1900, p90: 3200 ms, p99: 27300 ms), latency samples: 478640
2. Upgrading first Validator to new version: c6b9b28210348ce5140cffe30afcfef29d84aefb
compatibility::simple-validator-upgrade::single-validator-upgrading : committed: 7274.23 txn/s, latency: 3817.49 ms, (p50: 4000 ms, p70: 4300, p90: 5300 ms, p99: 5700 ms), latency samples: 136080
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 7188.01 txn/s, latency: 4483.97 ms, (p50: 4700 ms, p70: 4900, p90: 6200 ms, p99: 6700 ms), latency samples: 242100
3. Upgrading rest of first batch to new version: c6b9b28210348ce5140cffe30afcfef29d84aefb
compatibility::simple-validator-upgrade::half-validator-upgrading : committed: 7190.23 txn/s, latency: 3818.16 ms, (p50: 4200 ms, p70: 4600, p90: 4800 ms, p99: 4900 ms), latency samples: 128940
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 7505.94 txn/s, latency: 4252.86 ms, (p50: 4400 ms, p70: 4800, p90: 6000 ms, p99: 6300 ms), latency samples: 250220
4. upgrading second batch to new version: c6b9b28210348ce5140cffe30afcfef29d84aefb
compatibility::simple-validator-upgrade::rest-validator-upgrading : committed: 4565.41 txn/s, latency: 4488.82 ms, (p50: 2200 ms, p70: 6100, p90: 13200 ms, p99: 14800 ms), latency samples: 127220
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 10137.59 txn/s, latency: 3099.53 ms, (p50: 2700 ms, p70: 3000, p90: 5900 ms, p99: 7300 ms), latency samples: 355340
5. check swarm health
Compatibility test for 46bf19eb4f132b9d8fc19eff3f3334cdf9aa1775 ==> c6b9b28210348ce5140cffe30afcfef29d84aefb passed
Test Ok

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

[github-actions]

💚 All backports created successfully

Status	Branch	Result
✅	aptos-release-v1.21

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details