Describe the bug
If I start syncing new blockchain with pruning_horizon lets say 10000 it will start failing on end of syncing kernels stage:
May 04 07:58:25 pool bash[2448518]: 07:58 v5.3.0 mainnet State: Syncing kernels: 5485311/5485311 (100%) from d54542c2b53b9d2d9be839799f (23.79 kernels/s) Latency: 640.00ns Tip: 3060 (Sat, 10 May 2025 04:19:55 +0000) Mempool: 0tx (0g, +/- 0blks) Connections: 11|0 Banned: 2 Messages (last 60s): 81 Rpc: 0/100 ⚡️ 500.20µs
May 04 07:58:29 pool bash[2448518]: 07:58 ERROR Failed to apply DB transaction: ValueNotFound { entity: "utxo_commitment_index", field: "<unknown>", value: "5cc74b77f2cd863854092ca0e37089f1ddb7631bb848eb9aa73a4ff934b4001e" }
May 04 07:58:30 pool bash[2448518]: 07:58 v5.3.0 mainnet State: Syncing kernels: 5485311/5485311 (100%) from d54542c2b53b9d2d9be839799f (23.79 kernels/s) Latency: 640.00ns Tip: 3060 (Sat, 10 May 2025 04:19:55 +0000) Mempool: 0tx (0g, +/- 0blks) Connections: 11|0 Banned: 2 Messages (last 60s): 86 Rpc: 0/100 ⚡️ 500.20µs
May 04 07:58:35 pool bash[2448518]: 07:58 v5.3.0 mainnet State: Syncing kernels: 5485311/5485311 (100%) from d54542c2b53b9d2d9be839799f (23.79 kernels/s) Latency: 640.00ns Tip: 3060 (Sat, 10 May 2025 04:19:55 +0000) Mempool: 0tx (0g, +/- 0blks) Connections: 11|0 Banned: 2 Messages (last 60s): 86 Rpc: 0/100 ⚡️ 507.92µs
May 04 07:58:40 pool bash[2448518]: 07:58 v5.3.0 mainnet State: Syncing kernels: 5485311/5485311 (100%) from d54542c2b53b9d2d9be839799f (23.79 kernels/s) Latency: 640.00ns Tip: 3060 (Sat, 10 May 2025 04:19:55 +0000) Mempool: 0tx (0g, +/- 0blks) Connections: 11|0 Banned: 2 Messages (last 60s): 89 Rpc: 0/100 ⚡️ 507.92µs
May 04 07:58:45 pool bash[2448518]: 07:58 v5.3.0 mainnet State: Syncing kernels: 5485311/5485311 (100%) from d54542c2b53b9d2d9be839799f (23.79 kernels/s) Latency: 640.00ns Tip: 3060 (Sat, 10 May 2025 04:19:55 +0000) Mempool: 0tx (0g, +/- 0blks) Connections: 11|0 Banned: 2 Messages (last 60s): 85 Rpc: 0/100 ⚡️ 507.92µs
May 04 07:58:48 pool bash[2448518]: 07:58 ERROR Failed to apply DB transaction: ValueNotFound { entity: "utxo_commitment_index", field: "<unknown>", value: "5cc74b77f2cd863854092ca0e37089f1ddb7631bb848eb9aa73a4ff934b4001e" }
May 04 07:58:50 pool bash[2448518]: 07:58 v5.3.0 mainnet State: Syncing kernels: 5485311/5485311 (100%) from d54542c2b53b9d2d9be839799f (23.79 kernels/s) Latency: 640.00ns Tip: 3060 (Sat, 10 May 2025 04:19:55 +0000) Mempool: 0tx (0g, +/- 0blks) Connections: 11|0 Banned: 2 Messages (last 60s): 73 Rpc: 0/100 ⚡️ 518.48µs
To Reproduce
Download tari suite and uncomment and set pruning_horizon to some value like 10000. Start tari daemon: .../minotari_node --non-interactive-mode --watch status --disable-splash-screen
Expected behavior
Synced blockchain.
Desktop (please complete the following information):
- Ubuntu Linux 24.04, ARM64
Additional context
Makes pruning_horizon less useful at the moment when it is most needed (when DB id not yet big after full sync). It not working well on old versions like 5.2.1 that I tried as well.
Describe the bug
If I start syncing new blockchain with pruning_horizon lets say 10000 it will start failing on end of syncing kernels stage:
To Reproduce
Download tari suite and uncomment and set pruning_horizon to some value like 10000. Start tari daemon: .../minotari_node --non-interactive-mode --watch status --disable-splash-screen
Expected behavior
Synced blockchain.
Desktop (please complete the following information):
Additional context
Makes pruning_horizon less useful at the moment when it is most needed (when DB id not yet big after full sync). It not working well on old versions like 5.2.1 that I tried as well.