# Calling actor.remote() from a pythonic thread

**URL:** <https://discuss.ray.io/t/calling-actor-remote-from-a-pythonic-thread/10260>\
**Category:** Ray Core\
**Created:** [April 17, 2023, 9:15am UTC](https://discuss.ray.io/t/calling-actor-remote-from-a-pythonic-thread/10260 "2023-04-17T09:15:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![eladgm](https://avatars.discourse-cdn.com/v4/letter/e/ec9cab/32.png) [@eladgm](https://discuss.ray.io/u/eladgm)\
**Post date:** [April 17, 2023, 9:15am UTC](https://discuss.ray.io/t/calling-actor-remote-from-a-pythonic-thread/10260/1 "2023-04-17T09:15:50Z")

</div>

Is it generally supported making ray calls (actor.method.remote(), ray.wait(), ray.get(), etc…) from a (non main) pythonic thread? (ray 1.8.0)

Practically, on heavy workloads we’re always encountering the known issue of forever blocking remote() call (after a few hours of successful operation). Similar issue has been previously reported here [Ray actor.remote() call blocks forever](https://discuss.ray.io/t/ray-actor-remote-call-blocks-forever/6820/). However, we’re suspecting that the fact we’re making these calls from a non-main thread is the cause for this issue in our case. Conducting the same calls from the main thread of an actor doesn’t seem to fail in the same fashion.

The question: Is conducting ray calls from a non-main thread generally not recommended (especially for ray 1.8.0)?

Thanks

---

<div class="post-metadata">

**Author:** ![rickyyx](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/rickyyx/32/2671_2.png) [@rickyyx](https://discuss.ray.io/u/rickyyx)\
**Post date:** [April 19, 2023, 9:11pm UTC](https://discuss.ray.io/t/calling-actor-remote-from-a-pythonic-thread/10260/2 "2023-04-19T21:11:37Z")

</div>

Hey @eladgm - calling ray methods from another thread is expected to work.

If you run into some issues, would appreciate if you have a minimal repro script so we could take a look.

Also, issues you linked seems to be fixed in a recent ray releases last year.

I would highly recommend upgrading to a newer version of ray (i.e. 2.0) if it’s possible.