Description
When running Zowe in High Availability, the caching service on the secondary instance incorrectly points to the gateway host of the primary instance. This results in caching workspace directory being created only under the primary, even though the secondary is correctly defined as its own HA instance.
Despite specifying haInstances in the zowe.yaml and adding the environment variable, the runtime does not honor these settings instead this environment variable stays unset ZWE_components_caching_service_storage_infinispan_initialHost this results in both zowe instances pointing to one hostname and only creating one folder under /workspace/caching-service
This is my yaml:
haInstances:
HARS27:
components:
caching-service:
storage:
mode: infinispan
infinispan:
keyExchange:
port: 62601
jgroups:
port: 62600
host: rs27.rocketsoftware.com
initialHosts: HARS23[62600]
persistence:
dataLocation: /proj/mvd/zowe-james/caching-service/data02
indexLocation: /proj/mvd/zowe-james/caching-service/index02
sysname: RS27
hostname: rs27.rocketsoftware.com
HARS23:
components:
caching-service:
storage:
mode: infinispan
infinispan:
keyExchange:
port: 62601
jgroups:
port: 62600
host: rs23.rocketsoftware.com
initialHosts: HARS27[62600]
persistence:
dataLocation: /proj/mvd/zowe-james/caching-service/data01
indexLocation: /proj/mvd/zowe-james/caching-service/index01
sysname: RS23
hostname: rs23.rocketsoftware.comAnd the actual behavior is that rs27 caching-service log show
ZWES1063I Caching Service settings: gateway host 'rs23.rocketsoftware.com', port 62995
and no folder rs27 is created under workspace/caching-service
rs27 appears to route thorough rs23 despite proper haInstances config
Expected behavior
Each HA instance should use its own configured gateway host, Generate its own caching-service workspace folder.
Details
Zowe version: 3.3.0
Java: 17.0.14
Node: 18.18.2
z/OS: RS23 on z/OS 2.5, RS27 on z/OS 3.1