-
Enhancement
-
Resolution: Done
-
Blocker
-
EAPCD 14.0.GA
-
CLOUD Maintenance Sprint 27
With current EAP builds (EAP CD, EAP 7.2) When scaling up (under load), the time it takes the new node to join the cluster seems to be significantly higher that it is with jboss-eap-7/eap71-openshift:1.3.
More imporantly, in our test scenario, the new pod is ready before it joins the cluster (so it is receiving traffic) and the sessions such initiated are lost when the node joins the rest of the cluster.
Scenario: simple <distributable/> servlet, storing an integer counter into session
scaling from 2 to 3 under load (256 clients with random 0-20s delay before each request), no encryption, openshift.DNS_PING
- is blocked by
-
CLOUD-3029 [EAP] - Update openshift-ping to 1.2.3-Final
- Closed
- is caused by
-
CLOUD-3022 Drop use_ip_addrs="true" workaround
- Closed
- is cloned by
-
CLOUD-3028 [EAP][CD][7.2] OS / K8S DNS and JGroups
- New
- is related to
-
JGRP-2313 Promote GMS message "[...] creating cluster as first member" to INFO level
- Resolved
-
CLOUD-3017 [7.2]Update EAP templates to use publishNotReadyAddresses: true
- Closed
-
CLOUD-3026 [CD]Update EAP templates to use publishNotReadyAddresses: true
- Closed
- relates to
-
JGRP-2314 DNS_PING: port_range is ignored
- Resolved
-
CLOUD-3023 OpenshiftPing#sendMcastDiscoveryRequest reuses jgroups messages
- Closed