Skip to main content

Why we need atleast 2 WKMs for WSO2 Product cluster

Assume we have an ELB cluster with 2 nodes connected to AS and ESB clusters. (Here the well known members are 2 ELBs) All nodes are connected and working fine (members joined the cluster).
Let’s say, if both ELBs were down and then restarted, the ASs and ESBs also have to be restarted to join the cluster again.


This is a known issue in Hazelcast. If all WK members fail, the entire cluster has to be restarted. Thats why they have recommend to have two WKs members at minimum.
To avoid this situation you can configure the AS and ESB management nodes also as well-known members. Clustering details can found on AS[2] and ESB[3] links.


To configure AS & ESB mgt nodes as WK members, follow the following steps
- Update the AS mgt node axis2.xml file with WK member details as follows (do the same for ESB as well)
<members>
   <member>
       <hostName>xxx.xxx.xxx.
206</hostName> <!-- this should be the ELB details -->
       <port>4500</port>
   </member>
   <member>
       <hostName>(its own ip)</hostName>
       <port>(AS mgt node localmember port)</port>
   </member>
</members>
- Next you have to add the WK member details to the loadbalancer.conf file in ELBS
esb {
      domains{
         wso2.esb.domain {
              tenant_range *;
              group_mgt_port 4500;
              members <ip-of-mgt-node>:<local-port-of-mgt-node>;
              members 192.168.8.126:4010;
              
         mgt {
              hosts mgt.esb480.wso2.com;
         }
         worker {
              hosts wkr.esb480.wso2.com;
         }
     }
  }
Labels:

Comments

Post a Comment

Popular posts from this blog

How to generate random unique number in SOAP UI request

eg 1: ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} eg 2: ${=java.util.UUID.randomUUID()} ${=java.util.UUID.randomUUID()} ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} - See more at: http://tryitnw.blogspot.com/2014/03/generating-random-unique-number-in-soap.html#sthash.m2S4tUFu.dpuf ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} - See more at: http://tryitnw.blogspot.com/2014/03/generating-random-unique-number-in-soap.html#sthash.m2S4tUFu.dpuf ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} - See more at: http://tryitnw.blogspot.com/2014/03/generating-random-unique-number-in-soap.html#sthash.m2S4tUFu.dpuf
Post a Comment
Read more

Tips on using environment variables in WSO2 Integration Cloud

Environment variables allow you to change an application's internal configuration without changing its source code. Let’s say you want to deploy the same application in development, testing  and production environments. Then database related configs and some other internal configurations may change from one environment to another. If we can define these configurations as an environment variables we can easily set those without changing the source code of that application. When you deploy your application in WSO2 Integration Cloud, it lets you define environment variables via the UI. Whenever you change the values of environment variables, you just need to redeploy the application for the changes to take effect. Predefined environment variables Key Concepts - Environment Variables   provides you some predefined set of environment variables which will be useful when deploying applications in WSO2 Integration Cloud. Sample on how to use environment variables ...
Post a Comment
Read more

WSO2 ESB communication with WSO2 ESB Analytics

This blog post is about how & what ports involved when connecting from WSO2 ESB to WSO2 ESB Analytics. How to configure: This document explains how to configure it https://docs.wso2.com/display/ESB500/Prerequisites+to+Publish+Statistics Let's say we have WSO2 ESB  and WSO2 ESB Analytics packs we want to run in same physical machine, then we have to offset one instance.  But we don't want to do that since WSO2 ESB Analytics by default come with the offset. So WSO2ESB will run on 9443 port, WSO2 ESB Analytics will run on 9444 port WSO2 ESB publish data to the WSO2 ESB Analytics via thrift. By default thrift port is 7611 and corresponding ssl thrift port is 7711 (7611+100), check the data-bridge-config.xml file which is in analytics server config directory .  Since we are shipping analytics products with offset 1 then thrift ports are 7612 and ssl port is 7712. Here, ssl port (7712) is used for initial authentication purposes of data publisher ...
Post a Comment
Read more