Performing Post-Deployment Configuration

As of the current release, the Azure network can have some unintended effects on TCP sessions when idle for more than 5 minutes. To overcome this limitation, perform the following action on all Lightbits servers in the cluster after installation is complete.

You can SSH into your Lightbits storage VM using a method described in the Connect to VM section.

1. Open the Duroslight config file for editing.

sudo vi /etc/duroslight/conf.yaml

2. Append the following lines to the file.

tcp_keepalive_idle_secs: '1'

tcp_keepalive_interval_secs: '1'

tcp_keepalive_count: '15'

The file should look like the below example.

replicator:

    peer_connection_count: 1

    peer_connection_retry_ms: '500'

    peer_connection_keepalive_ms: '250'

    peer_inflight_request_queue_count : '1024'

configurator:

    health_state_timeout_ms: '2500'

nvmet:

    iop_limiter_window_ms: '250'

    tcp_keepalive_idle_secs: '1'

    tcp_keepalive_interval_secs: '1'

    tcp_keepalive_count: '15'

3. Save and exit the file.
4. Restart the node-manager service for the changes to take affect.

sudo systemctl stop node-manager

sudo systemctl start node-manager

5. Ensure that node-manager is up and running by using the command lbcli -J=$LIGHTBITS_JWT list nodes on a Lightbits storage VM, using an appropriate JWT taken from the installer node ~/lb_install/lightos_jwt file.
6. Repeat this process for all Lightbits nodes in the cluster.