aaronbuchwald

Note: AvalancheGo uses LevelDB by default, which guarantees durability after a process failure, but not a machine failure according to its documentation here: https://github.com/syndtr/goleveldb/blob/126854af5e6d8295ef8e8bee3040dd8380ae72e8/leveldb/opt/options.go#L731

We could alternatively implement this in one place in either the consensus engine or ProposerVM

Discussed with @StephenButtolph and decided on an implementation path here: 1. Separate this out to be implemented by the VM (up to the VM to implement this in memory or...

What branch of AvalancheGo can this be tested with?

What branch of avalanchego can I test this with? Once I can QA manually, I think this is good to merge to dev.

This is a great start, but we should probably be revamping the APIs used in avash to use the client in AvalancheGo instead. Ex. https://github.com/ava-labs/avalanchego/blob/master/vms/avm/client.go.

Following up here, are you still running into this issue? We've fixed a few bugs since this was last updated, please comment if this is still impacting you otherwise will...

Can you share the full logs directory of your node during shutdown?

Thanks for sharing, I see the interesting logs here: ``` Aug 28 18:57:49 systemd[1]: Stopping AVAX Node... Aug 28 18:57:49 avax[1559572]: [08-28|18:57:49.034] INFO node/node.go:1490 shutting down node {"exitCode": 0} Aug...

This was fixed in #853 . Please let us know if you see a similar issue and thanks for reporting!