Skip to main content

JBoss Fuse - How to setup cluster of servers in Fabric

Staying in Beijing for a technical enablement, one question I have been ask a lot is how to setup a Fabric in a cluster of servers with JBoss Fuse?

I am going to setup 2 Fuse on 2 different servers, and then join them together to form a fabric cluster.
BUT!!!! In the real world please make it at least 3 servers, as zookeeper needs more then 3 to successfully setup it's ensembles! 


First we need to create a fabric, so unzip the JBoss Fuse zip file in Server1, setup password by editing etc/user.properties.

And please do the same thing to server2. If you are testing, and tries to setup on the same machine, please remember to go to "org.apache.karaf.management.cfg" under etc/ and change the RMI related port.



also there are a few more port you need to adjust,

org.apache.karaf.shell.cfg, change the

  • sshPort

and last inside system.properties

  • org.osgi.service.http.port
  • activemq.port
  • activemq.jmx.url


Now, getting back to setting the cluster of fabric, start up JBoss Fuse by going into bin/ and execute fuse on server one. After it starts up, create a fabric by entering the following command:

fabric:create --wait-for-provisioning

This spins up a fabric on a container call root, now, start up JBoss Fuse on server2 by going to bin/ and execute fuse on server two. And instead of creating a fabric, we are going to join, by entering following command, as fabric:join [options] zookeeperUrl [containerName] .

fabric:join --zookeeper-password admin 192.168.0.1:2181 root1

To find out what the zookeeper URL, go to your fuse command line console in Server1 and type
config:edit io.fabric8.zookeeper
config:proplist

this will give you your zookeeper details

                       JBossFuse:karaf@root> config:proplist
            service.pid = io.fabric8.zookeeper
            zookeeper.password = ZKENC=YWRtaW4=
            zookeeper.url = 192.168.0.1:2181
            fabric.zookeeper.pid = io.fabric8.zookeeper

And now we have successfully created a fabric on 2 servers. If you type in container-list in the command line, you should be able to see we now have 2 working server.

JBossFuse:karaf@root> container-list 
[id]                           [version] [connected] [profiles]                                         [provision status]
root*                          1.0       true        fabric, fabric-ensemble-0000-1, jboss-fuse-full    success
root1                          1.0       true        fabric                            

And if you login to Fuse management console, under Runtime-> Containers you will see the 2 root containers on both servers


To add a new container, click on +Create on top right hand corner of the page, select the parent container so it will run on the server base on the parent container. Then choose the profile you need to install on the container.

And we are done!




Comments

Hi Christina!
Supposing my server1 (root container) goes down, what happens to the profile that I published in it?

Thanks
...or is it a good practice to publish profile on both containers?
Christina Lin said…
Actually, the profile is published to the fabric, not on a single container. so the fabric servers in the ensembles will duplicate these profiles within. So if any of them goes down, the other one will still work.
Hello , First i want to thank you for all the efforts you have done.
I followed all the steps you did on this tutorial.
i'm going to describe what i did exctely , i created a fabric on server1 after i have joined two containers (fabric:join as you did) (once at the same machine , the second from a remote pc at the same lan)
but when i executed the command "fabric:ensemble-add " to add the two containers already created to the ensemble , i had this error message "connection refused to host 192.168.56.1"
but i don't have any device runing with that ip knowing that my ip on lan have this structure 192.168.3.?
i don't why fuse had created a virtual network with that ip adress?
Christina Lin said…
When creating you fabric, try use "--manual-ip" to force setting your desire ip, so zookeeper wont go all over the place to get the IP. See if that works?
Mahran MJ said…
This comment has been removed by the author.
Mahran MJ said…
Hi Christina , Thank you for the tutorials you made , they helped me so much to learn Fuse ,
i Have a question about this tutorial , i did exactly what you did and i successfully created my Fabric Ensemble that contains 3 Fabric Server (that 2 fabric seervers at the same machine and the 3rd at a remote machine at the same lan ), until now i have no problem :)
My question is : if i want to link a profile (contains an application fuse Project web-Service) to a fabric, on which container should i link it? should i link it to one container on each fabric servers ? and what ip address should be called to invoke that webservice? what to do if one of this server goes down ?
i hope that you understand my question,Thanks
kishore said…
hi Christina

thanks a lot for your efforts, i created cluster as you said but when i am trying to stop it its throwing error below

Failed to stop root due to java.lang.UnsupportedOperationException : Container root has not been created using Fabric

Popular posts from this blog

Red Hat Fuse - Announcing Fuse 7 Tech preview 3 release.

Red Hat Fuse 7.0 technical preview three is out today! On the pathway to become one of the best cloud-native integration platform, Fuse gives developer freedom to choose how they want to develop the integration solution, where they want to deploy it and capabilities to address new integration personas that do not have development experience.
By supporting the three major runtime, developer is free to work on the runtime of their choice.By supporting standalone and cloud deployment, it simplifies the complexity to distinguish between these environments, allowing application to deploy freely among the environment of your choice. All levels of developers are welcome, you can either dive deep into creating customize complex integration logic, or using the new low code platform to quickly build a simple integration. In this Tech Preview release you get it all.
Fuse StandaloneSpring-boot for microserviceKaraf 4 for OSGi loverJBoss EAP for JavaEE developersFuse on OpenShiftPlugins for easy co…

JBoss EAP 6 - 效能調校 (一) DataSource 的 Connection Pool

效能沒有什麼Best Practice, 反正能調整的就那些。 通常,一個程式的效能大概有70-80% 都跟程式怎麼寫的其實比較有關係。

最近我最疼愛的小貓Puji 因為膀胱結石開刀的時候過世了,心情很差請原諒我的口氣沒有很好,也沒有心情寫部落格。

Puji R.I.P.

=======================正文=======================

這個題目很多人叫我寫,可是這題目好大,這分明就是整死我咩~
所以我會分幾段慢慢寫。

JBoss 的 SubsystemDatasource WebWeb Service EJB Hibernate JMSJCAJVM 調校OS (作業系統)

先來看一下 DataSource Subsystem, DataSource 的部分主要是針對Connection Pool 做調校。

通常,程式都會需要跟資料庫界接,電腦在本機,尤其是在記憶體的運算很快,但是一旦要外部的資源連接,就是會非常的耗資源。所以現在的應用程式伺服器都會有個Pool 放一些先連接好的 資料庫connection,當程式有需要的時候就可以馬上提供,而不用花那些多餘的資源去連接資料庫。

這就是為什麼要針對Connection Pool 去做調校。

以下會討論到的參數,都是跟效能比較有關係,Datasource 還有很多參數,像是檢核connection 是否正確的,我都不會提到。如果你追求的是非常快速的效能,那我建議你一個檢核都不要加。當然,這樣就會為伺服器上面執行的程式帶來風險。這就是你要在效能與正確,安全性上面的取捨了。 (套句我朋友說的話,不可能又要馬兒好,又要馬兒不吃草的..)

最重要的調校參數就是 Connection 的 Pool 數量。(也就是那個Pool 裡面要放幾條的connection.) 這個參數是每一個應用程式都不一樣的。

min-pool-size 

Connection Pool 最少會存留的connection 數量

max-pool-size 

Connection Pool 最多可以開啓的 connection 數量

prefill

事先將connection pool 裡面建立好min-pool-size 的connection.

我的建議是觀察一下平常程式要用到的量設定為 min-pool-size 。
加上…

Fuse - Contract First API Design with Apicurio and Fuse/Camel - Part One

This is part one of my two-article series that demonstrates the approach of implementing contract-first API design using Apicurioand Red Hat Fuse.

It covers how to create an OpenAPI standard document as the contract between API providers and consumers using Apicurio. It also shows how to quickly create mock tests using Red Hat Fuse.

There are two common approaches of creating these APIs.
Code FirstContract First Coming from a old time ESB developer, these are not new. We have been doing this forever. Before, it was the WSDL that define the contract of the service. we were doing a lot more code first, for me it's simply because it's much easier for me to write couple of Java classes and generate the WSDL for my consumer. 

It's often pretty straightforward if the consumer of your application has finalized how they want the service to be like. But you and I all know this is not often the case. So I had to go back to my code, and make the changes accordingly and pray I did not …