public or private. Whether you want to deploy an OpenStack cloud, a Kubernetes cluster or a 50,000-node render farm, Ubuntu Server delivers the best value scale-out performance available. In this documentation ation-with-docker Container customization with Docker 3 rock-images/multi-node-configuration-with-docker-compose Multi-node configuration with Docker-Compose 2 Software 3 package-management Package management IBM LPAR autoinstall on s390x ROCK Images Introduction Container customization with Docker Multi-node configuration with Docker-Compose Software Package management Upgrade Third party APT repositories

consider spreading your cards. If not at least allocate your memory to the node where the cards reside, for example in a two node all to node #2: -m 0, 2048. You can use the tool lstopo from the package hwloc-nox ovs-vsctl set Open_vSwitch . "other_config:dpdk-lcore-mask=0x1" # Allocate 2G huge pages (not Numa node aware) ovs-vsctl set Open_vSwitch . "other_config:dpdk-alloc-mem=2048" # group/permissions for vhost-user /var/log/openvswitch/ovs- vswitchd.log 2016-01-22T08:58:33.381Z|00003|ovs_numa|INFO|Discovered 12 CPU cores on NUMA node 0 2016-01-22T08:58:33.381Z|00004|ovs_numa|INFO|Discovered 1 NUMA nodes and 12 CPU cores 2016-01-22T08:58:33

status. ha_remove_node=target Remove the high availability (HA) node specified by its name or ID. Note that active/standby nodes cannot be removed. target - name or ID of the node (can be obtained high availability Starting Zabbix server as cluster node Two parameters are required in the server configuration to start a Zabbix server as cluster node: • HANodeName parameter must be specified for each each Zabbix server that will be an HA cluster node. This is a unique node identifier (e.g. zabbix-node-01) that the server will be referred to in agent and proxy configurations. If you do not specify

status. ha_remove_node=target Remove the high availability (HA) node specified by its name or ID. Note that active/standby nodes cannot be removed. target - name or ID of the node (can be obtained availability Starting Zabbix server as cluster node 30 Two parameters are required in the server configuration to start a Zabbix server as cluster node: • HANodeName parameter must be specified for for each Zabbix server that will be an HA cluster node. This is a unique node identifier (e.g. zabbix-node-01) that the server will be referred to in agent and proxy configurations. If you do not specify

status. ha_remove_node=target Remove the high availability (HA) node specified by its name or ID. Note that active/standby nodes cannot be removed. target - name or ID of the node (can be obtained high availability Starting Zabbix server as cluster node Two parameters are required in the server configuration to start a Zabbix server as cluster node: • HANodeName parameter must be specified for each each Zabbix server that will be an HA cluster node. This is a unique node identifier (e.g. zabbix-node-01) that the server will be referred to in agent and proxy configurations. If you do not specify

警报管理器统计信息 lld - LLD 管理器统计信息 locks - 互斥锁列表（在 **BSD 系统 * 上为空） ha_status 记录高可用性 (HA) 集群状态。 ha_remove_node=target 删除由其列出的编号或名称指定的高可用性 (HA) 节 点。 请注意，无法删除活动/备用节点。 target - 列表中的节点编号或名称（可以通过运行 ha_status 获得） • HANodeName 集群中每个 zabbix server 节点名称必须要有且唯一。 28 这是将在 agent 和 proxy 配置中引用 server 的名称 (例如：zabbix-node-01)。如果您没有指定 HANodeName，那么服务器将以 standalone 模式启动。 • NodeAddress 参数必须为每个节点指定。 NodeAddress 参数 (address:port) 的配置中。 对于被动代理，节点名称必须列在 proxy 服务器参数中，以逗号分隔。 Server=zabbix-node-01,zabbix-node-02 对于主动代理，节点名称必须列在 proxy 服务器参数中，以分号分隔。 Server=zabbix-node-01;zabbix-node-02 Agent 配置 Zabbix agent 或者 Zabbix agent 2. 必须将 HA

zabbix_server instances or nodes, where only one node can be active (working) at a time, while other nodes are on standby, ready to take over in case the current node is stopped or fails. See also: High availability now printed to the console. • It is possible to send longer input parameters, such as HA node name instead of node number. Runtime controls on BSD-based OS 15 Previously, Zabbix server and Zabbix proxy CockroachDB by HTTP • Envoy Proxy by HTTP • HashiCorp Consul Cluster by HTTP • HashiCorp Consul Node by HTTP See setup instructions for HTTP templates. You can get these templates: • In Configuration

see setup instructions for HTTP templates. MongoDB • MongoDB cluster by Zabbix agent 2 • MongoDB node by Zabbix agent 2 See setup instructions for Zabbix agent 2 templates. NetApp NetApp AFF A700 by 4 Zabbix 3.0 Zabbix 3.2 Zabbix 3.4 Zabbix 4.0 Zabbix 4.2 Zabbix 4.4 Zabbix 5.0 Zabbix 5.2 Node-based distributed monitoring removed 93 Upgrade from Read full upgrade notes Most important changes MongoDB cluster by Zabbix agent 2 - see setup instructions for Zabbix agent 2 templates; • MongoDB node by Zabbix agent 2 - see setup instructions for Zabbix agent 2 templates; • NetApp AFF A700 by HTTP

HTTP - native template to monitor Elasticsearch. ClickHouse • Template DB ClickHouse - collects node metrics from ClickHouse HTTP interface using HTTP agent. (see description). Memcached • Template instructions for Zabbix agent 2 templates. MongoDB • MongoDB cluster by Zabbix agent 2 • MongoDB node by Zabbix agent 2 See setup instructions for Zabbix agent 2 templates. You can get these templates: database instance or an external one. • Zabbix agent - a Zabbix agent can be deployed on each available node for stability and performance monitoring on remote nodes. It allows to gather metrics with full automation

0 Zabbix 3.2 Zabbix 3.4 Zabbix 4.0 Zabbix 4.2 Zabbix 4.4 Zabbix 5.0 Zabbix 5.2 Zabbix 5.4 Node-based distributed monitoring removed 2.0.x For: Zabbix 2.2 Zabbix 2.4 Zabbix 3.0 Zabbix 3.2 notation. 123 Value referred to by the JSONPath from the input document root node; only definite paths are supported. $.object.name Value referred to with libxml2 support. Method Description XML.query(expression, data) Retrieves node content using XPath. Returns null if node is not found. expression - an XPath expression; data - XML data as a string