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

Creating the configuration files

  • 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 activate 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. You can create an alternative system file in /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:
- reachable: 172.16.31.167:56001
  addresses:
  - 172.16.31.167:56001
- reachable: 172.16.31.162:56001
  addresses:
  - 172.16.31.162:56001
- reachable: 172.16.31.177:56001
  addresses:
  - 172.16.31.177:56001
  - 192.168.30.230:56001

Limits configuration file

The limits configuration file is installed on the vSphere Bitfusion client, as a part of the client package, in /etc/security/limits.d/bitfusion-client-limits.conf. The limits in the file apply to all members of the vSphere Bitfusion Linux user group, bitfusion. Any user of the vSphere Bitfusion client must be a member of the vSphere Bitfusion Linux user group. The bitfusion-client-limits.conf file contains the following settings and default values, which you can view or change, if needed, by using the standard Linux utility, ulimit.

  • The maximum number of open files is set to 10000.
    bitfusion soft nofile 100000
bitfusion hard nofile 100000
  • The locked-in-memory address space is set to unlimited.
    bitfusion soft memlock unlimited
bitfusion hard memlock unlimited
  • The maximum resident set size is set to unlimited.
    bitfusion soft rss unlimited
bitfusion hard rss unlimited
Note:

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