cluster about wildfly

[jeryma]

Question1:

Today,I want to set a wildfly cluster with one master controller and two slave. It works well with one master and one slave, but when I want to add another slave1 to my wildfly cluster ,and I find it can't start with error below:

[Host Controller] 14:44:16,867 ERROR [org.jboss.remoting.remote.connection] (Remoting "htdserver:MANAGEMENT" I/O-1) JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed

[Host Controller] 14:44:16,876 WARN  [org.jboss.as.host.controller] (Controller Boot Thread) JBAS016535: Could not connect to master. No domain controller discovery options left. Error was: java.lang.IllegalStateException: JBAS010942: Unable to connect due to authentication failure.

[Host Controller] 14:44:16,877 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010901: Could not connect to master. Aborting. Error was: java.lang.IllegalStateException: JBAS016519: Tried all domain controller discovery option(s) but unable to connect

[Host Controller] 14:44:16,905 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015950: WildFly 8.0.0.Alpha4 "WildFly" stopped in 17ms

It seems slave'host name with slave  work well, but name with slave1 can't.

<host name="slave1" xmlns="urn:jboss:domain:2.0">   ERRO

<host name="slave" xmlns="urn:jboss:domain:2.0">    WORK WELL

what should I do if I want to add another slave for my wildfly cluster? how to define the "<host name="slave" xmlns="urn:jboss:domain:2.0">"?

Question 2:

IF my domain conntroller failed , slave can't work well for my modcluster beacause of I configure modcluster only on the domain controller's domain.xml.

In this situation, what  can I do for  my domain controller faileover?

starksm64

@Tomaz Cerar

[rhusar]

I am not sure you are using the terms right, surely its a bit confusing:

• domain is only about management, provisioning, etc.
• clustering is about session replication, ie. http and ejb sfsb state replicate in between the nodes so that harware failure doesn't result in an outage
• mod_cluster is an apache module that works as load balancer (mod_jk replacement) and a part of AS that registers with the load balancer automatically

So Q1 has nothing to do with clustering, and Q2 modcluster has nothing to do with domain controller.

[jeryma]

thanks for your reply,But I know what you say about modcluster founction.

About Q1:

If I want to add annother slave,

in this situation I  will have one domain controller and two slave with it ,how should I configure the <host name="???" xmlns="urn:jboss:domain:2.0"> in host.xml ?

that is to say "domian controller can only have one slave ?"

About Q2:

In Production environment, If domain controller doesn't wrok, modcluster in httpdserver can send client request to slave ? in this situation,how to realise the failover about domain controller?

(domain controller have 3 servers in 10.19.182.2, slave have 3 servers in 10.19.181.3,httpd with modcluster in 10.19.182.4)

[wdfink]

Q1:

A domain controller can have many slaves. Each slave need to have a unique name, you might set "hc1, hc2 ..." or any unique name you want.

The error during HC start is because of the secured managment connection. You need to set a management user at the domain configuration and add the passwort base64 encoded to the HC security realm. If the HC is at the same machine this is not necessary as the domain contoller will accept the local slave by default.

The user name is the specified name for the host-element, but you might override it by the domain controller configuration in the slave's host.xml.

Q2:

modcluster will not sent requests to the 'slave' HC.

The slave starts one or more server instances which are responsible to handle the application load.

Domain controller, host controller and the process controller (only seen as java process) are only management instances and not handling any applicaition response.

The servers are continue handle applicaiton requests. Only the host controller will log periodical a message that there is no domain controller available.

It will reconnect to the domain if it is up again.

There is no automatic domain-controller failover mechanism implemented.

[jeryma]

thank you very much! That's  what I want