Configuring high availability

• a single Developer Portal with embedded ignite is an Ignite server node,
• together they form an Ignite cluster,
• and it is a stateless cluster as Developer Portal does not require persistence for its distributed caches.

• 47500 - 47509. These ports enable the discovery of Ignite nodes.
• 47100 - 47200. These ports enable communication between Ignite nodes. Ensure that these ports are accessible across other nodes.

  If you have blocked the access of the port 47100 by any another application in the system, you need to open up the complete series. You can just open up the 47100 port. For more info refer https://ignite.apache.org/docs/latest/clustering/network-configuration.

• It is recommended that you do not open the following local ports when you system is behind firewall:
  • 10800. Enables communication between the thin client and the Ignite cluster.
  • 11211. Enables communication between the JDBC client and the Ignite database.
  • 47400. Enables node discovery via the UDP port.

#******* @subdomain@Nginx Config ********
events {
    worker_connections  1024;
}
 
http {
 
     
upstream @subdomain@_ui_upstream {
  ip_hash;
  server @node1@:18101;
  server @node2@:18101;
  server @node3@:18101;
}
  
server {
  listen       80;
  listen       [::]:80;
  server_name  @subdomain@;
  
  access_log  /var/log/nginx/access.log;
  
  # DESIGN time should work only in https.
  location /portal {
    proxy_pass              http://@subdomain@_ui_upstream/portal/;
    proxy_set_header        Host $host;
    proxy_set_header        X-Real-IP $remote_addr;
    real_ip_header          X-Real-IP;
    proxy_http_version      1.1;
    proxy_set_header        Connection "";
  }
  
  location /portal/ {
    proxy_pass              http://@subdomain@_ui_upstream/portal/;
    proxy_set_header        Host $host;
    proxy_set_header        X-Real-IP $remote_addr;
    real_ip_header          X-Real-IP;
    proxy_http_version      1.1;
    proxy_set_header        Connection "";
  }
}
 
}