[jboss-jira] [JBoss JIRA] (WFLY-11750) Allow cluster to use DNS addresses instead of IP addresses

[Tomasz Adamski (Jira)]

     [ https://issues.jboss.org/browse/WFLY-11750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomasz Adamski updated WFLY-11750:
----------------------------------
    Description: 
We would need a configuration that would allow for the cluster to use DNS addresses instead of IP addresses. The reason is that OpenShift guarantees the node identity under DNS address and not under IP address.

Sample scenario that may currently fail when application are deployed in OpenShift:
A (application)
B (clustered application)

1. A calls transactional invocation on B
2. as a result of discovery process A obtains a cluster topology from B and uses one of obtained IP addresses for the connection
3. as the invocation is transactional the object-store records are written in A's persistent object store; those records are based on the data obtained from the cluster => subordinate node is identified by the IP address from point two
4. B node fails
5. OpenShift restarts node B on another IP address
6. A attempts recovery and persistently fails

OTOH OpenShift guarantees node identity under DNS address. As a result, at point 5 node is guaranteed to restart on established DNS address so if the cluster used this address instead of physical addresses the scenario above will finish with A being able to recover the transaction.

  was:
We would need a configuration that would allow for the cluster to use DNS addresses instead of IP addresses. The reason is that OpenShift guarantees the node identity under DNS address and not under IP address.

Sample scenario that may currently fails when application are deployed in OpenShift:
A (application)
B (clustered application)

1. A calls transactional invocation on B
2. as a result of discovery process A obtains a cluster topology from B and uses one of obtained IP addresses for the connection
3. as the invocation is transactional the object-store records are written in A's persistent object store; those records are based on the data obtained from the cluster => subordinate node is identified by the IP address from point two
4. B node fails
5. OpenShift restarts node B on another IP address
6. A attempts recovery and persistently fails

OTOH OpenShift guarantees node identity under DNS address. As a result, at point 5 node is guaranteed to restart on established DNS address so if the cluster used this address instead of physical addresses the scenario above will finish with A being able to recover the transaction.



> Allow cluster to use DNS addresses instead of IP addresses
> ----------------------------------------------------------
>
>                 Key: WFLY-11750
>                 URL: https://issues.jboss.org/browse/WFLY-11750
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Clustering
>    Affects Versions: 16.0.0.Beta1
>            Reporter: Tomasz Adamski
>            Assignee: Paul Ferraro
>            Priority: Major
>
> We would need a configuration that would allow for the cluster to use DNS addresses instead of IP addresses. The reason is that OpenShift guarantees the node identity under DNS address and not under IP address.
> Sample scenario that may currently fail when application are deployed in OpenShift:
> A (application)
> B (clustered application)
> 1. A calls transactional invocation on B
> 2. as a result of discovery process A obtains a cluster topology from B and uses one of obtained IP addresses for the connection
> 3. as the invocation is transactional the object-store records are written in A's persistent object store; those records are based on the data obtained from the cluster => subordinate node is identified by the IP address from point two
> 4. B node fails
> 5. OpenShift restarts node B on another IP address
> 6. A attempts recovery and persistently fails
> OTOH OpenShift guarantees node identity under DNS address. As a result, at point 5 node is guaranteed to restart on established DNS address so if the cluster used this address instead of physical addresses the scenario above will finish with A being able to recover the transaction.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)