# Pyarrow read timeout always 15 seconds bug?

**URL:** <https://community.dremio.com/t/pyarrow-read-timeout-always-15-seconds-bug/8779>\
**Category:** Uncategorized\
**Created:** [February 22, 2022, 12:08pm UTC](https://community.dremio.com/t/pyarrow-read-timeout-always-15-seconds-bug/8779 "2022-02-22T12:08:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![xieyonggang](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/xieyonggang/32/3976_2.png) [@xieyonggang](https://community.dremio.com/u/xieyonggang)\
**Post date:** [February 22, 2022, 12:08pm UTC](https://community.dremio.com/t/pyarrow-read-timeout-always-15-seconds-bug/8779/1 "2022-02-22T12:08:23Z")

</div>

Hi Dremio Team,

i am using the python client to connect to dremio via pyarrow’s flight protocol.

i follow the pyarrow example and do the following :

options = flight.FlightCallOptions(timeout=600000, headers=headers)  
flight\_info = cls.\_\_client.get\_flight\_info(flight.FlightDescriptor.for\_command(sqlquery), options)  
reader = cls.\_\_client.do\_get(flight\_info.endpoints[0].ticket, options)  
reader.read\_pandas()

what i realise is that every time i read execute the sqlquery, if the query exceeds 15 seconds, i got an timeout error even though i set the timeout in the FlightCallOption to be 6000000, the exact exception is below:

Exception: FlightUnavailableError(‘gRPC returned unavailable error, with message: upstream request timeout. Client context: IOError: Server never sent a data message. Detail: Internal. gRPC client debug context: {“created”:"@1645525023.713203665",“description”:“Error received from peer ipv4:172.29.123.223:8000”,“file”:"/opt/vcpkg/buildtrees/grpc/src/17cc203898-db2679e7f2.clean/src/core/lib/surface/call.cc",“file\_line”:1067,“grpc\_message”:“upstream request timeout”,“grpc\_status”:14}’)

do you know why?

---

<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:** [March 2, 2022, 5:04pm UTC](https://community.dremio.com/t/pyarrow-read-timeout-always-15-seconds-bug/8779/2 "2022-03-02T17:04:52Z")

</div>

@xieyonggang There seems to be an open feature request to support this, let me confirm and get back to you

---

<div class="post-metadata">

**Author:** ![xieyonggang](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/xieyonggang/32/3976_2.png) [@xieyonggang](https://community.dremio.com/u/xieyonggang)\
**Post date:** [March 3, 2022, 3:53pm UTC](https://community.dremio.com/t/pyarrow-read-timeout-always-15-seconds-bug/8779/3 "2022-03-03T15:53:56Z")

</div>

Thanks, let me know if you found it and any work around now ?

---

<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:** [March 4, 2022, 1:57am UTC](https://community.dremio.com/t/pyarrow-read-timeout-always-15-seconds-bug/8779/4 "2022-03-04T01:57:37Z")

</div>

@xieyonggang We are discussing prioritization of this and will keep you posted

---

<div class="post-metadata">

**Author:** ![n-a-sz](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/n-a-sz/32/3758_2.png) [@n-a-sz](https://community.dremio.com/u/n-a-sz)\
**Post date:** [August 5, 2022, 7:04am UTC](https://community.dremio.com/t/pyarrow-read-timeout-always-15-seconds-bug/8779/5 "2022-08-05T07:04:16Z")

</div>

Hi, is there any news on this topic? I’m facing the same problem.  
There are queries that I don’t want to accelerate but still want to do it through Dremio and expected to be slow.