The default is 30 seconds, if it is not enough for jboss start, adjust the limit, but use real jboss startup time, not 10 minutes as rule of thumb.Ģ.) fix the jboss dependency. The docker-compose-cluster example demonstrates how to extend this. it shows CPU Load over mean 2.5 CPU over mean 40 but when I have two nodes(4cpu 8GB Linux) ejabberd cluster, I test 12000 usrs, two ejabberd nodes. When trying to restart slave node its not getting start once it down. Dockerfile to build an ejabberd container image. The issue is when I stop master node: Then no request getting routed to slave. okie and database files from master to slave. it is set to 600 seconds and on error blocks the testing for 10 minutes. I have setup ejabberd clustering, one is master and other is slave as described here. timeout is set to 600 seconds, so the start attempt lasted 11:47-11:58ġ.) reduce jboss start timeout. The purpose of ejabberd cluster is for fault tolerance and scalability, being able to use multiple servers for a single or a small group of large domains. error : ' jboss - status ' failed to start - could not start required services: ' jboss ' error : ' mediator ' failed to start - could not start required services: ' jboss - status ' info : ' mediator ' start action failed error : ' jboss ' failed to start (exit status 1) - /opt/vsd/sysmon/jbossStart.sh: node ' vsd - kmurthy - set1 - node1. Please ensure ejabberd passes and try again. For old access rule and ACL syntax documentation, please refer to configuration document archive. sh debug : JBoss can 't start without Ejabberd. This section describes new ACL syntax introduced in ejabberd 16.06. Info : 'jboss' start : / opt / vsd / sysmon / jbossStart. Its because there is no such thing as clustering with PostgreSQL in ejabberd because the state of the application is still clustered with mnesia.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |