github.com/smintz/nomad@v0.8.3/website/source/docs/enterprise/autopilot/index.html.md (about) 1 --- 2 layout: "docs" 3 page_title: "Nomad Enterprise Advanced Autopilot" 4 sidebar_current: "docs-enterprise-autopilot" 5 description: |- 6 Nomad Enterprise supports Advanced Autopilot capabilities which enable fully 7 automated server upgrades, higher throughput for reads and scheduling, and hot 8 server failover on a per availability zone basis. 9 --- 10 11 # Nomad Enterprise Advanced Autopilot 12 13 Nomad Enterprise supports Advanced Autopilot capabilities which enable fully 14 automated server upgrades, higher throughput for reads and scheduling, and hot 15 server failover on a per availability zone basis. See the sections below for 16 additional details on each of these capabilities. 17 18 * **Automated Upgrades:** Advanced Autopilot enables an upgrade pattern that 19 allows operators to deploy a complete cluster of new servers and then simply wait 20 for the upgrade to complete. As the new servers join the cluster, server 21 introduction logic checks the version of each Nomad server. If the version is 22 higher than the version on the current set of voters, it will avoid promoting 23 the new servers to voters until the number of new servers matches the number of 24 existing servers at the previous version. Once the numbers match, Autopilot will 25 begin to promote new servers and demote old ones. 26 27 * **Enhanced Read Scalability:** With Advanced Autopilot, servers can be 28 explicitly marked as non-voters. Non-voters will receive the replication stream 29 but will not take part in quorum (required by the leader before log entries can 30 be committed). Adding explicit non-voters will scale reads and scheduling without 31 impacting write latency. 32 33 * **Redundancy Zones:** Advanced Autopilot redundancy zones make it possible to 34 have more servers than availability zones. For example, in an environment with 35 three availability zones it's now possible to run one voter and one non-voter in 36 each availability zone, for a total of six servers. If an availability zone is 37 completely lost, only one voter will be lost, so the cluster remains available. 38 If a voter is lost in an availability zone, Autopilot will promote the non-voter 39 to voter automatically, putting the hot standby server into service quickly. 40 41 See the [Nomad Autopilot Guide](https://www.nomadproject.io/guides/cluster/autopilot.html) 42 for a comprehensive overview of Nomad's open source and enterprise Autopilot features.