Multinode Configuration
Using Multinode Configuration
Multinode configuration is an advanced feature designed for specific scenarios that require multiple consensus nodes. This configuration demands higher resources and involves more complexity, making it suitable primarily for testing and development environments. Before attempting to use the multinode setup, it's crucial to ensure that the local node operates correctly in the default single-node mode.
Starting Multinode Mode
To start Hedera Local Node in multinode mode, append the --multinode
flag to your start command. For example:
# npm command to start the local network in multinode mode
npm run start -- -d --multinode
# docker command to start the local network in multinode mode
docker compose up -d --multinode
Verify the successful launch of multinode mode by inspecting Docker output of docker ps --format "table {{.Names}}" | grep network
or the Docker Desktop dashboard. You should identify four running nodes:
network-node
network-node-1
network-node-2
network-node-3
📣 Note: In multinode mode, you need at least three healthy nodes for operational network.
Starting and Stopping Nodes
Individual nodes can be started or stopped to test consensus, synchronization, and node selection processes using npm
or docker
management commands:
Alternatively, run docker compose down -v; git clean -xfd; git reset --hard
to stop the local node and reset it to its original state.
Multinode Mode Diagram
The following diagram illustrates the architecture and flow of data in multinode mode.

Last updated
Was this helpful?