# FATAL: GetTableSchemaRpc time out after deadline expired

**URL:** <https://forum.yugabyte.com/t/fatal-gettableschemarpc-time-out-after-deadline-expired/2621>\
**Category:** General\
**Created:** [April 24, 2024, 5:04pm UTC](https://forum.yugabyte.com/t/fatal-gettableschemarpc-time-out-after-deadline-expired/2621 "2024-04-24T17:04:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![parvez](https://avatars.discourse-cdn.com/v4/letter/p/49beb7/32.png) [@parvez](https://forum.yugabyte.com/u/parvez)\
**Post date:** [April 24, 2024, 5:04pm UTC](https://forum.yugabyte.com/t/fatal-gettableschemarpc-time-out-after-deadline-expired/2621/1 "2024-04-24T17:04:09Z")

</div>

[New to YB]  
I have a YB deployed on 3 nodes. all of them have master and Tserver services running, A couple of nodes are complaining about the below error when I run ysqlsh. Can someone help me understand this below error

ysqlsh: FATAL: GetTableSchemaRpc(table\_identifier: table\_id: “000033bd000030008000000000001f64”, num\_attempts: 5) timed out after deadline expired, passed 137.123s of 120.000s

---

<div class="post-metadata">

**Author:** ![dorian\_yugabyte](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.yugabyte.com/dorian_yugabyte/32/206_2.png) [@dorian\_yugabyte](https://forum.yugabyte.com/u/dorian_yugabyte)\
**Post date:** [April 25, 2024, 6:28am UTC](https://forum.yugabyte.com/t/fatal-gettableschemarpc-time-out-after-deadline-expired/2621/2 "2024-04-25T06:28:12Z")

</div>

Does this happen only when you open it? Or run some query?

Can you post more logs from these yb-tservers? You can upload zipped in google driver or smth and link here.

---

<div class="post-metadata">

**Author:** ![parvez](https://avatars.discourse-cdn.com/v4/letter/p/49beb7/32.png) [@parvez](https://forum.yugabyte.com/u/parvez)\
**Post date:** [May 8, 2024, 4:18am UTC](https://forum.yugabyte.com/t/fatal-gettableschemarpc-time-out-after-deadline-expired/2621/3 "2024-05-08T04:18:39Z")

</div>

Hi @dorian_yugabyte, ysql port got stuck due to network blips. DB operations were working. Rolling-Restart of yugabyted service fixed the connectivity issue. Thank you for your response!