[
https://issues.jboss.org/browse/WFLY-6778?page=com.atlassian.jira.plugin....
]
Paul Ferraro updated WFLY-6778:
-------------------------------
Description:
Undertow exposes a single instance-id for the whole subsystem. This id is used by a load
balancer to uniquely identify the node among other nodes in the load balancing group.
However, this granularity is not correct.
Undertow can define multiple servers, each with a unique set of listeners. From the
perspective of the load balancer, these servers are distinct and thus must use distinct
names. Thus, rather than installing a single SessionIdentifierCodec for the subsystem, we
should install one instance per server.
was:
Currently, Undertow only exposes a single instance-id for the whole subsystem. This id is
used by a load balancer to uniquely identify the node among other nodes in the load
balancing group. However, this granularity is not correct.
Undertow can define multiple servers, each with a unique set of listeners. From the
perspective of the load balancer, these servers are distinct and thus must use distinct
names.
Each Undertow server should expose a distinct SessionIdentifierCodec
--------------------------------------------------------------------
Key: WFLY-6778
URL:
https://issues.jboss.org/browse/WFLY-6778
Project: WildFly
Issue Type: Bug
Components: Clustering, Web (Undertow)
Affects Versions: 10.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Undertow exposes a single instance-id for the whole subsystem. This id is used by a load
balancer to uniquely identify the node among other nodes in the load balancing group.
However, this granularity is not correct.
Undertow can define multiple servers, each with a unique set of listeners. From the
perspective of the load balancer, these servers are distinct and thus must use distinct
names. Thus, rather than installing a single SessionIdentifierCodec for the subsystem, we
should install one instance per server.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)