Missing Trie Node
kidneyweakx opened this issue · comments
ISSUE
說明 (Description)
Blockscout (-32000) missing trie node logs
種類 (Issue Type)
- Feature Request
- Report Bug
- Other
通報問題 (Report Bug)
重現步驟 (Steps to Reproduce)
- Block already garbage collection (gc)
- Blockscout restart as new
測試環境 (Environment):
- OS: macOS
- NodeJS Version: 16.13
- NPM Version:
- Docker Version: 20.10.17
應呈現結果 (Expected Behavior)
No error
Please describe the bahavior expected.
實際呈現結果 (Resulted Behavior)
0x21e2aba9ac09c64c0e6f5e02b6f7ae11e4db8b8f@m: (-32000) missing trie node c3888f465bb0d17b8977bca602a1a99897d7c8643e8b2d6b4323b07ca031249f (path )
0x6a275bd5d12d1eea671b7b98e7ffda16b67b51ca@p: (-32000) missing trie node d72aa08d8f55320061f35962e7b7e39f02fb6d07ee1e35be171c6769ed7469bd (path )
0x507143aeac6f0d1bd70909b01c676e1e6c61bee4@l: (-32000) missing trie node b9bdd258d62841cb2ab5d396e6d9317c1e4cc99aefe3f1925a440fbfb5888b33 (path )
0x420f4de35b90c160e7d3161e39371b7763125505@k: (-32000) missing trie node c05aea93665af82a933f8699307eeaab14d1d7b44f6f6ea5a2c603e856de88a6 (path )
0x0c3b00533f967379354ad93486771f81a42f4bc8@p: (-32000) missing trie node d72aa08d8f55320061f35962e7b7e39f02fb6d07ee1e35be171c6769ed7469bd (path )
0x02f74263d1b3ef715f751b6726e18c6ec383d43a@n: (-32000) missing trie node 5d9e12b050bc204a2a84b1480748fa70cd1b21b3b1391a75f3aa0bf95385c711 (path )
0x26c03677cb820ad86b85e47b95d05b5cdab1d066@n: (-32000) missing trie node 5d9e12b050bc204a2a84b1480748fa70cd1b21b3b1391a75f3aa0bf95385c711 (path )
0xa2e182cf01e0d2cb8226a41197d57aebdb58c1bd@o: (-32000) missing trie node 38927c2718411631d444d136f9fdc2780dd4e956dcaa36877aec28ac402760e3 (path )
0x9aa5ccb5d0d52404d2b8efd4c74dcb4eee01f749@o: (-32000) missing trie node 38927c2718411631d444d136f9fdc2780dd4e956dcaa36877aec28ac402760e3 (path )
0x6d743f45324a40033a2297d494da45395adb2ecf@l: (-32000) missing trie node b9bdd258d62841cb2ab5d396e6d9317c1e4cc99aefe3f1925a440fbfb5888b33 (path )
0x50bc55b6800df95718f733be6ef2648a42f68d63@n: (-32000) missing trie node 5d9e12b050bc204a2a84b1480748fa70cd1b21b3b1391a75f3aa0bf95385c711 (path )
0x8f92801950858911046be2d01c49b4e822cb3029@l: (-32000) missing trie node b9bdd258d62841cb2ab5d396e6d9317c1e4cc99aefe3f1925a440fbfb5888b33 (path )
0x9a276bc878ff08cdabb2d37b7710c68ae6ba205d@k: (-32000) missing trie node c05aea93665af82a933f8699307eeaab14d1d7b44f6f6ea5a2c603e856de88a6 (path )
0x7991c05c0a675d05e3e0c30ba4edf72e131e1baa@k: (-32000) missing trie node c05aea93665af82a933f8699307eeaab14d1d7b44f6f6ea5a2c603e856de88a6 (path )
0xe9cd36d5e0d84fd6e9d3de177e5ecd5d58dd96a5@p: (-32000) missing trie node d72aa08d8f55320061f35962e7b7e39f02fb6d07ee1e35be171c6769ed7469bd (path )
0x5e8a5e850b23469574be3ce4899a5e5cfd5c7080@m: (-32000) missing trie node c3888f465bb0d17b8977bca602a1a99897d7c8643e8b2d6b4323b07ca031249f (path )
0xf56f9a5b8a2f8e370c8ab58ae046d871151882c3@m: (-32000) missing trie node c3888f465bb0d17b8977bca602a1a99897d7c8643e8b2d6b4323b07ca031249f (path )
0x9e0e79272e11550102475f1e5c2db517db916035@o: (-32000) missing trie node 38927c2718411631d444d136f9fdc2780dd4e956dcaa36877aec28ac402760e3 (path )
0x74068fe63abce328900f58bffa71fb58a335042a@p: (-32000) missing trie node d72aa08d8f55320061f35962e7b7e39f02fb6d07ee1e35be171c6769ed7469bd (path )
0xed3f194f094447cf400119e0356bfdd835faf16a@p: (-32000) missing trie node d72aa08d8f55320061f35962e7b7e39f02fb6d07ee1e35be171c6769ed7469bd (path )
0x6f831597ff804e1e38fc884e8ca64120887d69aa@k: (-32000) missing trie node c05aea93665af82a933f8699307eeaab14d1d7b44f6f6ea5a2c603e856de88a6 (path )
0x464003bd696c14d2fc434fa10ed1cdd8df944090@l: (-32000) missing trie node b9bdd258d62841cb2ab5d396e6d9317c1e4cc99aefe3f1925a440fbfb5888b33 (path )
0xd273936075ea0187d8bd959a4fb53f624e6b37f5@k: (-32000) missing trie node c05aea93665af82a933f8699307eeaab14d1d7b44f6f6ea5a2c603e856de88a6 (path )
Please describe the behavior that actually occurred.
其他說明 (Additional Context)
可能修復解法：加入--gcmode archive 在 validator-docker-compose.yaml
Node should be archive node and fully sync to blockchain.
Therefore, if blockscout exist on the node. This node must be archive node (whatever it is validator / member)
We have 2 prefer solutions:
- force add an archive node in validator0 (it is option), and only start blockscout on this machine
- start a new member archive node and start in this machine
@Pianochicken which one is better?
I think there might be another solution is that:
Add a new interacting question when executing bdk quorum network create -i. Let users multi-select the validators or members they want to become archive node.
@kidneyweakx What do you think?