Memory depletion during the synchronization of the Shiden network node

[TomaszWaszczyk]

Description

I try to make a fully sync of Shiden network, but I am not able to do it.

Steps to Reproduce

All made according to documentation with and without wrap mode with and without -- --wrap flag.

Expected vs. Actual Behavior

Obtain fully sync node.

Environment

Describe the environment in which you encountered this bug. Use the list below as a starting point and add additional information if you think it's relevant.

• Operating system: GNU Debian 12.2
• Project version/tag: v5.28.0 but I was trying also with a few last versions, too.

Additional Information

Initially, I attempted to synchronize with 32GB of RAM and 32GB of swap, contemplating whether expanding the swap to 64GB could alleviate the issue. Regrettably, even with an additional 64GB of swap, the problem persisted. Out of memory occurs around after ~40hrs of synchronization.

[ashutoshvarma]

Can you share the logs and the full command used to start the node?

[TomaszWaszczyk]

Commands like:

./astar-collator \
  --collator \
  --name 'test-name' \
  --chain shiden \
  --base-path /var/lib/astar \
  --pruning archive \
  --trie-cache-size 0 \
  --telemetry-url 'wss://telemetry.polkadot.io/submit/ 0'

or

./astar-collator \
  --collator \
  --name 'test-name' \
  --chain shiden \
  --base-path /var/lib/astar \
  --trie-cache-size 0 \
  --telemetry-url 'wss://telemetry.polkadot.io/submit/ 0' \
  -- \
  --warp

or

ExecStart=/home/collator/astar-collator \
			--chain 'shiden' \
			--rpc-cors all \
                        --base-path '/home/shiden/' \
                        --name 'name' \
                        --rpc-port 9933 \
			--state-pruning archive \
			--blocks-pruning archive \
			--prometheus-external \
                        --telemetry-url 'wss://telemetry.polkadot.io/submit/ 0' \
			-- --sync warp

Unfortunately, I don't have logs as I've removed them. I try sync next time, and if I have logs, I'll update the issue.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions]

This issue was closed because it has been stalled for 7 days with no activity.