For security reasons, the Mender client does not require any open ports on the embedded device. Therefore, all communication between the Mender client and the server is always initiated by the client and it is important to configure the client so that the frequency of sending various requests to the server is reasonable for a given setup.
There are two client configuration parameters that allow controlling the frequency of communication between the client and the server:
UpdatePollIntervalSeconds sets the frequency the client will send an update check request to the server.
Default value: 1800 seconds (30 minutes).
InventoryPollIntervalSeconds sets the frequency for periodically sending inventory data.
Inventory data is always sent after each boot of the device, and after a new update has been
correctly applied and committed by the device in addition to this periodic interval.
Default value: 28800 seconds (8 hours).
The Mender client is more responsive with higher frequency intervals. Meaning that the client inventory data updates more frequently. The client also polls for updates at a smaller interval, leading to faster deployments.
But there is a trade-off; higher polling frequencies results in more server load. If one server has many clients connected, a high frequency will require more resources server-side to keep the environment responsive.
If you are using the Mender client in demo mode, either by selecting it when running
mender setup, or by using the meta-mender-demo layer, the Mender client has more aggressive polling intervals to simplify testing. The defaults noted above do not apply to demo mode and you will see extra network traffic in demo mode.
Both parameters are stored in the configuration file
© 2024 Northern.tech AS