SKALE Supernode Swap Limit Fix

Introduction

This guide provides instructions for SKALE validators to fix swap limit issues on their supernodes. We need to enable swap limiting capability so SKALE Chain containers can use swap properly.

Background

Swap memory is limited by default if memory for the container is limited. For each SKALE Chain container, 2.6GB of RAM is allocated on the machine, which means an additional 2.6GB will be allocated for swap. For more details, refer to the Docker documentation on resource constraints.

Checking Current Setup (Optional)

You can check the current memory allocation for your SKALE Chain containers (if your supernode has SKALE Chains) using the following command:

docker inspect skale_schain_[SKALE Chain-NAME] | grep Memory

A correct setup should look similar to this:

"Memory": 2678032302,
"MemoryReservation": 0,
"MemorySwap": 5356064604,
"MemorySwappiness": null,

MemorySwap should be x2 of Memory value.

Identifying the Issue

The issue occurs when the swap limit capability is disabled in the kernel. To check if this is the case, run:

docker info

If you see the following line at the end of the output, it means the swap limiting capability is disabled:

WARNING: No swap limit support

Fixing the Swap Limit Issue

If you will encounter with any issues during the following steps, please stop and contact SKALE team.

If your supernode is running on Google Cloud, commands may differ. Please check discussions on Stack Exchange or contact SKALE team.

Follow these steps to enable swap limiting capability:

Hardware Requirements Upgrade to v5.0.0

Validators

Network Releases

Passive Nodes

Node CLI

Validator CLI

Watchdog

Introduction

Background

Checking Current Setup (Optional)

Identifying the Issue

Fixing the Swap Limit Issue

​Introduction

​Background

​Checking Current Setup (Optional)

​Identifying the Issue

​Fixing the Swap Limit Issue

Introduction

Background

Checking Current Setup (Optional)

Identifying the Issue

Fixing the Swap Limit Issue