# How rpServiceResolver works?

**URL:** <https://community.temporal.io/t/how-rpserviceresolver-works/8622>\
**Category:** Community Support\
**Created:** [June 23, 2023, 4:53am UTC](https://community.temporal.io/t/how-rpserviceresolver-works/8622 "2023-06-23T04:53:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![JerryHu](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/jerryhu/32/2609_2.png) [@JerryHu](https://community.temporal.io/u/JerryHu)\
**Post date:** [June 23, 2023, 4:53am UTC](https://community.temporal.io/t/how-rpserviceresolver-works/8622/1 "2023-06-23T04:53:59Z")

</div>

Hi all,

We are experiencing a strange issue. We have our temporal cluster deployed on AWS EKS. The frontend service has 4 nodes but in the log, we found in the discovery log

{“level”:“info”,“ts”:“2023-06-23T04:03:07.021Z”,“msg”:“Current reachable members”,“service”:“history”,“component”:“service-resolver”,“service”:“frontend”,“addresses”:[\<6 nodes in total\>],“logging-call-at”:“rpServiceResolver.go:266”}

It contains 6 nodes. And turned out to be 2 frontend nodes of another temporal cluster. Wonder how the service resolver determines reachable members?

Best,  
JH

---

<div class="post-metadata">

**Author:** ![jwatkins](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/jwatkins/32/2581_2.png) [@jwatkins](https://community.temporal.io/u/jwatkins)\
**Post date:** [July 4, 2023, 4:43pm UTC](https://community.temporal.io/t/how-rpserviceresolver-works/8622/2 "2023-07-04T16:43:29Z")

</div>

Which version of Temporal server are you running? I believe that since Temporal Server 1.19, membership from distinct clusters should not combine. If you want to keep running older Temporal Servers, then you will need to use different membership ports for each Temporal cluster.

You can find more about this in [this KB article](https://docs.temporal.io/kb/legacy-oss-prod-deploy#faq-multiple-deployments-on-a-single-cluster).