Skip to main content
Close announcements banner

Upgrades and maintenance

In terms of ease of operations, automated upgrades are the most impactful feature of Forts. Automatic upgrades comes with several benefits:

  • Keeps Forts up to date every day with the latest and greatest.

  • Delivering critical patches and/or diagnostic builds for troubleshooting purposes can be done in an extremely reactive manner.

  • Updates apply to all aspects of a fort, from the operating system to the services running on it.

Automatic upgrades are run every day on a fort, early in the morning of the local time zone. It's fair to ask whether a fort updating that often won’t result in a lot of downtime when it is upgrading. Only around 10% of fort updates require downtime, and when they do, the downtime is only the amount of time that it takes to reboot a fort.

You may also ask, if the upgrade introduces an error in my environment that Qlik didn’t predict, and the fort cannot restart, how will it be recovered? This is why the fort has both Active and Passive partitions. See the following diagram and description.

Minor and major updates of Forts

How minor and major updates are performed with active and passive partitions

When the fort applies a minor update, the Active partition uses a connection to Mender to do things like upgrading microservices, which do not require the fort to be rebooted, and also doesn’t interfere with user sessions.

When the fort applies a major update, a reboot is required. In this case, the Passive partition is updated, and the fort is rebooted. After the reboot, the fort runs health checks to determine if it is functioning properly. If so, the Passive partition becomes active. If not, the Passive partition is rolled back, and the current Active partition is used.