Skip to main content
Solved

FME Server Fault Tolerant installation - Queues behavior

  • November 20, 2018
  • 6 replies
  • 31 views
lau
Forum|alt.badge.img+3

Hi,

I plan to install a fault tolerant FME Server 2018.1. I would like to install 2 systems that each have 2 engines. A load balancer will manage the requests to these 2 systems (as below)

I have 2 questions:

1/ Is it possible to dedicate one engine to a "message streaming" workflow (WebsocketReceiver/WebsocketSender). Let say the engine1 of the host1.

2/ Is it possible to send "big job" only to the engine1 of the host2? In my comprehension, I will have to duplicate queues on both hosts so it seems not possible to only use one engine...

 

Thank you in advance!

 

Laurent

 

Best answer by jlutherthomas

Hi @lau

 

 

Are you able to share screenshots of your engine management page, and the deployment status page?
View original
Did this help you find an answer to your question?

6 replies

virtualcitymatt
Celebrity
Forum|alt.badge.img+35

In that set up sending a specific job to a specific host would not be considered Fault Tolerant but I think it should be possible.

 

 

When you say 'two engines on each' are you saying that you have four licensed engines? In that case the idea is that when/if one of the servers goes down then the jobs will just be directed to the one server (you will only have two engines).

I think that in the FME Server UI on the engines page you should see both hosts available with the engines, you should be able to control which queues have which engines. The Load Balancer simply directs the requests to (one) the FME Servers. The queue manager will send it the specified engine.

 

If a host is down then those engines will be too and so the queue will just fill up until the engine comes back online.
lau
Forum|alt.badge.img+3
  • lau
  • Author
  • November 20, 2018
virtualcitymatt wrote:

In that set up sending a specific job to a specific host would not be considered Fault Tolerant but I think it should be possible.

 

 

When you say 'two engines on each' are you saying that you have four licensed engines? In that case the idea is that when/if one of the servers goes down then the jobs will just be directed to the one server (you will only have two engines).

I think that in the FME Server UI on the engines page you should see both hosts available with the engines, you should be able to control which queues have which engines. The Load Balancer simply directs the requests to (one) the FME Servers. The queue manager will send it the specified engine.

 

If a host is down then those engines will be too and so the queue will just fill up until the engine comes back online.

Hi @virtualcitymatt,

Thank you for your answer. Here are some precisions:

Yes I will have four licensed engines.

What I am not sure to understand is the fact that the 4 engines are not always available. In the print screen below I read that the load balancer distributes web requests between all of the FME Server environments. I am a bit confused...

J
Forum|alt.badge.img+2
  • jlutherthomas
  • Best Answer
  • November 20, 2018

Hi @lau

 

 

Are you able to share screenshots of your engine management page, and the deployment status page?
lau
Forum|alt.badge.img+3
  • lau
  • Author
  • November 20, 2018
jlutherthomas wrote:

Hi @lau

 

 

Are you able to share screenshots of your engine management page, and the deployment status page?

I have no FME Server installation yet... I am asking these 2 questions because I am not sure to understand exactly what has changed in FME 2018.1.

In the configuration I described, are there 4 engines available? Or only 2 actives + 2 inactives?

richardatsafe
Safer
Forum|alt.badge.img+10
lau wrote:

I have no FME Server installation yet... I am asking these 2 questions because I am not sure to understand exactly what has changed in FME 2018.1.

In the configuration I described, are there 4 engines available? Or only 2 actives + 2 inactives?

Hi @lau,

 

In a 2018.1 Fault tolerance installation there are no passive engines. All engines are active. So you can route jobs to whichever engine you want. If you do have an engine do down its a good idea to have a second queue with a lower priority pointing at an engine on a different host so processing still continues.

https://docs.safe.com/fme/html/FME_Server_Documentation/Content/WebUI/Job-Queues.htm?Highlight=priority

 

This may be of use too.

https://knowledge.safe.com/articles/81263/an-fme-server-20181-installation-scenario.html

In regards to the original question.

 

1) Yes you can route any job

2) The queue is set up on the file share and database so its already shared between servers. No need to duplicate any process.

lau
Forum|alt.badge.img+3
  • lau
  • Author
  • November 20, 2018
richardatsafe wrote:

Hi @lau,

 

In a 2018.1 Fault tolerance installation there are no passive engines. All engines are active. So you can route jobs to whichever engine you want. If you do have an engine do down its a good idea to have a second queue with a lower priority pointing at an engine on a different host so processing still continues.

https://docs.safe.com/fme/html/FME_Server_Documentation/Content/WebUI/Job-Queues.htm?Highlight=priority

 

This may be of use too.

https://knowledge.safe.com/articles/81263/an-fme-server-20181-installation-scenario.html

In regards to the original question.

 

1) Yes you can route any job

2) The queue is set up on the file share and database so its already shared between servers. No need to duplicate any process.

Thank you for your response. It's totally clear now :) And thank your for the link to the different scenarios. It will help me!

Reply


Helpful Members This Week

Community Stats

31,191
Posts
118,244
Replies
38,801
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.