A customer would like to specify the particular node in a Gluster cluster a client uses for data reads. This has financial implications when using AWS availability zones.
The original problem was with an OCS cluster. The customer placed the three gluster nodes in three different AZs. The expectation was that when a worker pod was rescheduled to a different AZ, the pod would use the gluster node in the new AZ as the source for its data reads. A shockingly high communication bill showed the worker pod continued to communicate with the gluster node in the previous AZ.
An independent Gluster cluster or an OCS cluster in AWS where the nodes are placed in different availability zones.
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.