Is there an existing issue?
- I have searched the existing issues
Experiencing problems? Have you tried our Stack Exchange first?
- This is not a support question.
Description of bug
I tried running a statemine archive node using the parity/polkadot-parachain:1.1.0 Docker image. However, I noticed that when the node synchronizes to a certain number of blocks, the memory usage increases dramatically until it is forcefully terminated. Even after restarting, the node gets terminated due to high memory usage. Below is the command I used to run the node:
docker run -d parity/polkadot-parachain:1.1.0 --base-path=/substrate-base --name="test" --rpc-external --rpc-cors=all --prometheus-external --chain=statemine --rpc-methods=Unsafe --rpc-max-connections=1000 --pruning=archive --execution=wasm
This is the log of the node container getting stuck and being killed after restart:
CLI parameter `--execution` has no effect anymore and will be removed in the future!
2023-09-21 11:11:28 Polkadot parachain
2023-09-21 11:11:28 ✌️ version 1.1.0-783579b4a49
2023-09-21 11:11:28 ❤️ by Parity Technologies <admin@parity.io>, 2017-2023
2023-09-21 11:11:28 � Chain specification: Kusama Asset Hub
2023-09-21 11:11:28 � Node name: "Subscan Explorer Hosted"
2023-09-21 11:11:28 � Role: FULL
2023-09-21 11:11:28 � Database: RocksDb at /substrate-base/chains/asset-hub-kusama/db/full
2023-09-21 11:11:30 Parachain id: Id(1000)
2023-09-21 11:11:30 Parachain Account: 5Ec4AhPZk8STuex8Wsi9TwDtJQxKqzPJRCH7348Xtcs9vZLJ
2023-09-21 11:11:30 Is collating: no
This is the resource information occupied by the node at runtime:

Steps to reproduce
- Run Node
docker run -d parity/polkadot-parachain:1.1.0 --base-path=/substrate-base --name="test" --rpc-external --rpc-cors=all --prometheus-external --chain=statemine --rpc-methods=Unsafe --rpc-max-connections=1000 --pruning=archive --execution=wasm
Wait for a significant increase in memory usage. Currently, the exact time point when memory usage will increase rapidly cannot be predicted.