https://docs.mitigator.ru/v26.04/en/tags/cluster/ Recent content in Cluster on BIFIT Mitigator Hugo -- gohugo.io en https://docs.mitigator.ru/v26.04/en/install/multi/vpn/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.04/en/install/multi/vpn/ Principle of Operation The following steps assume that an instance of MITIGATOR has already been installed. Otherwise, perform installation using one of the following methods. Interaction between instances is arranged through Wireguard. A virtual network (VPN) is created between instances. Each instance has a key pair: a private key and a public key. The private key is stored only on its instance in vpn-private.conf. The public keys of all instances are listed in vpn-public. https://docs.mitigator.ru/v26.04/en/install/multi/workers/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.04/en/install/multi/workers/ The following steps assume that an instance of MITIGATOR has already been installed. Otherwise, perform the installation using one of the following methods. Before setting up a cluster, you must set up a virtual network (VPN). It needs network connectivity between instances to work. Detailed information on setting up and the necessary access are described at the link. Common databases for all MITIGATOR instances are physically stored on the server of one of them. https://docs.mitigator.ru/v26.04/en/install/multi/failover/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.04/en/install/multi/failover/ The following steps assume that an instance of MITIGATOR has already been installed. Otherwise, perform installation using one of the following methods. Before configuring a cluster, you must configure Virtual network(VPN). It needs network connectivity between instances to work. Detailed information on setting up and the necessary access are described at the link. For fault tolerance, synchronized copies of the database must be physically stored on different servers (replicated). With this scheme, database replicas are stored on the same servers where MITIGATOR instances are running. https://docs.mitigator.ru/v26.04/en/install/multi/custom/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.04/en/install/multi/custom/ The following steps assume that an instance of MITIGATOR has already been installed. Otherwise, install it using one of the following methods first. Before configuring a cluster, you must configure virtual network (VPN). It needs network connectivity between instances to work. Detailed information on setting up and necessary accesses are described by the link. This deployment scheme implies the physical storage of databases common to all MITIGATOR instances on an external server. https://docs.mitigator.ru/v26.04/en/install/multi/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.04/en/install/multi/ In cluster mode, several instances of the MITIGATOR system use common databases and are centrally managed. By adding additional instances, the system allows unlimited scaling. Cluster mode allows you to process traffic independently on each instance, but manage them from a single interface. In the event of a planned or emergency shutdown of any instance, the ability to manage the rest remains. Deployment Virtual network (VPN) is configured between instances. It needs network connectivity between instances to work. https://docs.mitigator.ru/v26.04/en/install/multi/hybrid/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.04/en/install/multi/hybrid/ deployment schemes can be combined when building a cluster. Example: Failover Storage with Additional Filtering Nodes With this implementation scheme, database copies are stored on different servers (replicated), but the number of database replicas is less than the number of MITIGATOR instances in the cluster. Some instances access remote databases via TCP ports: 8888, 2003, 3080, 5432. In this example, the graphite and logan are included as external modules. For correct system operation all packet processors must have the same amount of system resources available. https://docs.mitigator.ru/v26.04/en/price/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.04/en/price/ MITIGATOR is distributed on fixed-term and perpetual licenses. The minimum validity period for a term license is 1 month. The number of instances in a cluster is licensed additionally. The number of non-clustered instances is not limited by the license. The license limits the rate of the traffic entering the system. The license limiter accounts both attack traffic and legitimate traffic. The minimum licensed bandwidth available for purchase is 100 Mbps. https://docs.mitigator.ru/v26.04/en/kb/pgfailover/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.04/en/kb/pgfailover/ pgfailover monitors the state of a PostgreSQL cluster and acts as a TCP proxy for clients, directing them to the current Primary. When the Primary changes, pgfailover terminates client connections, and they must reconnect. Connection parameters are specified via environment variables with the PGFAILOVER_ prefix: export PGFAILOVER_BIND_ADDRESS=":5432" export PGFAILOVER_SERVERS="postgres://repuser@pg0.example.com/database?sslmode=disable&connect_timeout=5 postgres://repuser@pg1.example.com/database?sslmode=disable&connect_timeout=5" ./pgfailover The server role (Primary/Standby) is checked using pg_is_in_recovery(), by default every 5 seconds (PGFAILOVER_INTERVAL), with the number of connection attempts controlled by the PGFAILOVER_ATTEMPTS environment variable (default: 1).