{"componentChunkName":"component---src-templates-blog-post-js","path":"/running-clustering-tests-for-wso2-mb","result":{"data":{"markdownRemark":{"html":"

A cluster is a group of nodes each running an instance of a product. This cluster of nodes act as a single instance,\ndividing up the work among the nodes, improving performance and reliability.

\n

\"wso21\"

\n

In this post, let us setup a cluster of two nodes running WSO2 Message Broker 3.0.0 and run clustering tests on them.\nThese steps can be used to set up a cluster of MB 3.2.0 as well.

\n

You can get the WSO2 Message Broker installer from here. However, to run\nthe tests, you will need to checkout the GitHub repository. You will\nrequire at least two instances running MB to create a cluster with two nodes. You can use one of these MB nodes\nto run the test case suite.

\n

Setting up the MB cluster

\n

Following configurations need to be done in all nodes in the cluster.

\n

1. Configuring broker.xml

\n

Configure the <MB_HOME>/repository/conf/broker.xml file as described in steps 2 and 3 in WSO2 documentation here.

\n

When modifying the thrift related configurations in each node, use the IP of the node as the thriftServerHost:

\n
<coordination>\n    <nodeID>default</nodeID>\n    <thriftServerHost>x.x.x.x</thriftServerHost>\n    <thriftServerPort>7611</thriftServerPort>\n</coordination>
\n

2. Creating the message store for the cluster

\n

Create the MySql database to be used as the message store for MB. Although MB supports various database systems\nsuch as MySql, MSSQL, and Oracle, currently only MySql databases are supported for cluster testing.

\n\n
sudo apt install mysql-server
\n\n

3. Setting up the cluster databases

\n

Every WSO2 product uses a database to store information such as user management and registry data.\nIn addition to this database, a cluster should have a central database for config and governance registry mounts.\nYou can follow WSO2 documentation here and\ncreate the required databases. You can create these databases in the server or node in which you created the\nMySql database in the previous step.

\n

4. Configuring registry.xml

\n

Add the details of registry database created in the previous step in the <MB_HOME> /repository/conf/registry.xml\nfile as mentioned in the documentation.

\n

5. Configure axis2.xml and qpid-config.xml files

\n

Configure <MB_HOME>/repository/conf/axis2/axis2.xml and <MB_HOME> /repository/conf/advanced/qpi-config.xml files\nas mentioned in the documentation.

\n

6. Time sync all broker nodes

\n

Use the following command to time sync the nodes.

\n
$ sudo apt-get install ntpdate;\n$ sudo ntpdate pool.ntp.org
\n

Starting the cluster

\n

Now the cluster is configured. Start each node using the following command in <MB_HOME>/bin.\nTo create the required tables in the MySql message store database which we created in step 2, run the starting\ncommand with the flag -Dsetup.

\n
./wso2server.sh start -Dsetup
\n

After starting all nodes, observe the logs using the command tailf command as below, and verify that the\nnodes are added to the cluster and are connected with each other.

\n
tailf ../repository/logs/ wso2carbon.log
\n

Running clustering tests

\n

We can use one of the above nodes to run clustering tests. Configure the following in the node you wish\nto run the tests.

\n
    \n
  1. Add the nodes of the cluster in automation.xml.
    2. \n
\n
<platform>\n    <!--\n        cluster instance details to be used to platform test execution. \n        One node is to be a compression enabled node, and the other node is to be without compression.\n    -->\n    <productGroup name=\"MB_Cluster\" clusteringEnabled=\"false\" default=\"true\">\n        <instance name=\"mb002\" type=\"standalone\" nonBlockingTransportEnabled=\"false\">\n            <hosts>\n                <host type=\"default\">192.168.1.3</host>\n            </hosts>\n            <ports>\n                <port type=\"http\">9763</port>\n                <port type=\"https\">9443</port>\n                <port type=\"amqp\">5672</port>\n                <port type=\"mqtt\">1883</port>\n            </ports>\n            <properties>\n\n            </properties>\n        </instance>\n        <instance name=\"mb003\" type=\"standalone\" nonBlockingTransportEnabled=\"false\">\n            <hosts>\n                <host type=\"default\">192.168.1.4</host>\n            </hosts>\n            <ports>\n                <port type=\"http\">9764</port>\n                <port type=\"https\">9444</port>\n                <port type=\"amqp\">5673</port>\n                <port type=\"mqtt\">1884</port>\n            </ports>\n            <properties>\n         \n            </properties>\n        </instance>\n    </productGroup>\n</platform>
\n
    \n
  1. Add the MySql message store you created earlier to automation.xml.
    2. \n
\n
<datasources>\n    <datasource name=\"mbCluster\">\n        <url>jdbc:mysql://localhost/WSO2_MB</url>\n        <username>root</username>\n        <password>root</password>\n        <driverClassName>com.mysql.jdbc.Driver</driverClassName>\n    </datasource>\n</datasources>
\n
    \n
  1. Enable running tests by setting the value of skipPlatformTests in pom.xml to false.
    2. \n
\n
<properties>\n    <skipPlatformTests>true</skipPlatformTests>\n</properties>
\n
    \n
  1. Now run the clustering tests by executing the command mvn clean install.
    2. \n
","frontmatter":{"date":"October 08, 2019","path":"/running-clustering-tests-for-wso2-mb","title":"Running Clustering Tests for WSO2 Message Broker","tags":["Message Broker","WSO2"]}}},"pageContext":{}},"staticQueryHashes":["3649515864"]}