Доброго дня,

 

Ви можете налаштувати Creatio web farm використовуючи базову інструкцію, яка надана в Академії. Посилання: https://academy.creatio.com/docs/user/on_site_deployment/deployment_add…

I think I’ve managed to solve this problem. In some applications we need to ensure that the user must be connected to the same server during the whole session. So, to allow this I changed the Load Balance Algorithm to source.

frontend front
     maxconn 10000
     #Using these ports for binding
     bind *:80
     bind *:443
     #Convert cookies to be secure
     rspirep ^(set-cookie:.*)  \1;\ Secure
     default_backend creatio
 
backend creatio
     #set balance type
     balance source       
     server node_1 nodeserver1:80 check weight 2
     server node_2 nodeserver2:80 check weight 1

The problem was solved, but I don't know if this is the correct way to solve it. I would like to hear some feedback. Thank you.

Best Regards,

Pedro Pinheiro

Hi Pedro, 



We generally recommend using round-robin, as it's optimal in most cases, but the "source" algorithm is working as well. 

As for why the log-in issue happened: it's hard to say definitely, but on of the options is if the machinekey is different on different nodes - it won't let you log in. 

Best regards,

Yurii.

Hi Yurii Sokil,

I moved this infrastructure to a Linux server. In this server I have the same two instances but with different ports instead of docker containers. How can I generate this "machinekey”?

The documentation only explains how to generate them on windows servers, through  PowerShell.

Best Regards,

Pedro Pinheiro

Hello,

Such an option is not available for fault-tolerant installation. 

Fault-tolerant architecture implies that when one node fails, users will be able to work with the neighbouring one. If two neighbouring nodes are different, then this is no longer a fault-tolerant architecture, but two different applications.

Best regards,

Angela