# Load balancing REST API requests across master and coordinator nodes

**URL:** <https://community.dremio.com/t/load-balancing-rest-api-requests-across-master-and-coordinator-nodes/10900>\
**Category:** Dremio University\
**Created:** [August 17, 2023, 4:09pm UTC](https://community.dremio.com/t/load-balancing-rest-api-requests-across-master-and-coordinator-nodes/10900 "2023-08-17T16:09:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kyleahn](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/kyleahn/32/4799_2.png) [@kyleahn](https://community.dremio.com/u/kyleahn)\
**Post date:** [August 17, 2023, 4:09pm UTC](https://community.dremio.com/t/load-balancing-rest-api-requests-across-master-and-coordinator-nodes/10900/1 "2023-08-17T16:09:42Z")

</div>

Hi, team Dremio.

Based on [dremio-coordinator.yaml](https://github.com/dremio/dremio-cloud-tools/blob/d82811a0d25f1b81ff237f856fda151057ce6609/charts/dremio_v2/templates/dremio-coordinator.yaml#L74-L82) helm chart, I am seeing that web port 9047 isn’t in the container port. This implies that the load balancer does not balance REST API requests across master and coordinator nodes, contradicting the deployment architectural diagram.

 ![Untitled](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/2X/c/c3074235b1557be5b9034ee7252134cfe90d8bdb.png)

My use case requires load balancing a heavy load of REST API requests, and thus I did manually update the helm chart to load balance REST API requests across master and coordinator nodes. Is there a reason why this wasn’t the default behaviour?

Thanks!

---

<div class="post-metadata">

**Author:** ![balaji.ramaswamy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/balaji.ramaswamy/32/843_2.png) [@balaji.ramaswamy](https://community.dremio.com/u/balaji.ramaswamy)\
**Post date:** [August 22, 2023, 3:42am UTC](https://community.dremio.com/t/load-balancing-rest-api-requests-across-master-and-coordinator-nodes/10900/2 "2023-08-22T03:42:27Z")

</div>

@kyleahn Scale out coordinator is designed only for JDBC/ODBC requests and not REST/UI queries

---

<div class="post-metadata">

**Author:** ![kyleahn](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/kyleahn/32/4799_2.png) [@kyleahn](https://community.dremio.com/u/kyleahn)\
**Post date:** [August 22, 2023, 4:13am UTC](https://community.dremio.com/t/load-balancing-rest-api-requests-across-master-and-coordinator-nodes/10900/3 "2023-08-22T04:13:16Z")

</div>

In that case, the architectural diagram in the official Dremio website should be updated!

I am also curious how one would be able to force manual refresh of external reflection’s metadata at scale. We have a use case where there are thousands of iceberg tables being updated every minute. 1 pod won’t be sufficient.

---

<div class="post-metadata">

**Author:** ![balaji.ramaswamy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/balaji.ramaswamy/32/843_2.png) [@balaji.ramaswamy](https://community.dremio.com/u/balaji.ramaswamy)\
**Post date:** [August 24, 2023, 5:17am UTC](https://community.dremio.com/t/load-balancing-rest-api-requests-across-master-and-coordinator-nodes/10900/4 "2023-08-24T05:17:16Z")

</div>

@kyleahn

We are coming with concept of seamless metadata refresh for Iceberg Tables. We should soon have something. This should eliminate the need for metadata refresh for Native Iceberg tables

Thanks  
Bali