Trick to skip chunk revalidation on restart?

[biofreeze]

I saw somewhere that there is a way to get Cardano Node to skip revalidation on restart..

2024-03-17 19:47:18 [7d750c31:cardano.node.ChainDB:Info:5] [2024-03-17 23:47:18.36 UTC] Validating chunk no. 2995 out of 5514. Progress: 54.31%
2024-03-17 19:47:19 [7d750c31:cardano.node.ChainDB:Info:5] [2024-03-17 23:47:19.21 UTC] Validated chunk no. 2995 out of 5514. Progress: 54.32%
2024-03-17 19:47:19 [7d750c31:cardano.node.ChainDB:Info:5] [2024-03-17 23:47:19.21 UTC] Validating chunk no. 2996 out of 5514. Progress: 54.32%
2024-03-17 19:47:19 [7d750c31:cardano.node.ChainDB:Info:5] [2024-03-17 23:47:19.73 UTC] Validated chunk no. 2996 out of 5514. Progress: 54.34%
2024-03-17 19:47:19 [7d750c31:cardano.node.ChainDB:Info:5] [2024-03-17 23:47:19.73 UTC] Validating chunk no. 2997 out of 5514. Progress: 54.34%
2024-03-17 19:47:20 [7d750c31:cardano.node.ChainDB:Info:5] [2024-03-17 23:47:20.10 UTC] Validated chunk no. 2997 out of 5514. Progress: 54.36%
2024-03-17 19:47:20 [7d750c31:cardano.node.ChainDB:Info:5] [2024-03-17 23:47:20.10 UTC] Validating chunk no. 2998 out of 5514. Progress: 54.36%
2024-03-17 19:47:20 [7d750c31:cardano.node.ChainDB:Info:5] [2024-03-17 23:47:20.63 UTC] Validated chunk no. 2998 out of 5514. Progress: 54.38%
2024-03-17 19:47:20 [7d750c31:cardano.node.ChainDB:Info:5] [2024-03-17 23:47:20.63 UTC] Validating chunk no. 2999 out of 5514. Progress: 54.38%
2024-03-17 19:47:21 [7d750c31:cardano.node.ChainDB:Info:5] [2024-03-17 23:47:21.28 UTC] Validated chunk no. 2999 out of 5514. Progress: 54.40%
2024-03-17 19:47:21 [7d750c31:cardano.node.ChainDB:Info:5] [2024-03-17 23:47:21.28 UTC] Validating chunk no. 3000 out of 5514. Progress: 54.40%

This stuff ^

I can't for the life of me find that original article/documentation however. Does anyone know how to do it? I'm running Cardano Node in Docker and it's super annoying to have to wait for it to finish before the node finishes.

Thank you!

[wolf31o2]

That's not a good idea for integrity.

What's possibly happening (especially on mainnet) is the application isn't shutting down in the default 30s that Docker gives as a grace period. Increasing this timeout will allow the node to shutdown cleanly.