After you start a vSphere Bitfusion server instance, vSphere Bitfusion creates and maintains the servers.conf and bitfusion-limits.conf configuration files on the vSphere Bitfusion clients.

When you deploy the vSphere Bitfusion client VMs on ESXi hosts that are part of the same vCenter Server environment as the vSphere Bitfusion server instance, the configuration files are created after you enable the client by using the vSphere Bitfusion plug-in.

When you deploy the vSphere Bitfusion clients on bare metal machines, Kubernetes clusters, or ESXi hosts that are part of a different vCenter Server environment, the configuration files are created after you copy a client authentication token to the filesystem of the vSphere Bitfusion client.

Servers Configuration File

vSphere Bitfusion creates a high-priority user-specific file in ~/.bitfusion/servers.conf. Alternatively, you can create a system file /etc/bitfusion/servers.conf, which vSphere Bitfusion uses with a lower priority than the user-specific file. You use the cat command to display a server list.

To understand the command use, see the following example.

cat ~/.bitfusion/servers.conf

The servers configuration file lists the IPv4 addresses of all vSphere Bitfusion servers and ports that a vSphere Bitfusion client can access.
servers:
- addresses:
  - 192.168.128.77:56001
  - 10.202.8.77:56001
- addresses:
  - 192.168.128.79:56001
  - 10.202.8.79:56001
- addresses:
  - 192.168.128.80:56001
  - 10.202.8.80:56001
- addresses:
  - 192.168.128.78:56001
  - 10.202.8.78:56001

Limits Configuration File

The following limits apply to members of the vSphere Bitfusion group. Any user of the vSphere Bitfusion client must be a member of the vSphere Bitfusion group.

The bitfusion-limits.conf configuration file is installed on the vSphere Bitfusion client in /etc/security/limits.d/bitfusion-limits.conf by the client package. The file contains the following settings, which you can view and enforce by using the standard Linux utility, ulimit.
  • You can specify the maximum number of open files.
    @bitfusion soft nofile 100000
    @bitfusion hard nofile 100000
  • You can specify the locked-in-memory address space.
    @bitfusion soft memlock unlimited
    @bitfusion hard memlock unlimited
  • You can specify the maximum resident set size.
    @bitfusion soft rss unlimited
    @bitfusion hard rss unlimited
Note:

If the resource limit for open files is too low, vSphere Bitfusion might receive a connection error: Cannot allocate memory error. To resolve this issue, set the open files limit to 4096 or higher by running the ulimit -n 4096 command.