ray: [Bug] Ray 1.7 and 1.8 ray.init hangs when some versions of Python gRPC library is used due to global symbol export

Search before asking

• I searched the issues and found no similar issues.

Ray Component

Ray Core

What happened + What you expected to happen

This is not a contribution.

After upgrading to Ray 1.7, we noticed that when we import pybinded C++ code that uses a different version of grpc than comes with ray, we consistently get segfaults.

Turns out this is due to Ray exporting its grpc symbols so they are global and available to things like _streaming.so. This seems to have been added in https://github.com/ray-project/ray/pull/18490

When I comment out *grpc*; at https://github.com/ray-project/ray/blob/2367a2cb9033913b68b1230316496ae273c25b54/src/ray/ray_version_script.lds#L43 (so the symbols are not exported) and build ray 1.7.0 locally, our code does not segfault.

Looking at https://github.com/ray-project/ray/pull/18870, it seems like *absl*; caused a similar issue and has already been removed, but @ashione mentions in https://github.com/ray-project/ray/pull/18870#issuecomment-926701935 that *grpc*; might be needed for some ray/streaming tests to pass.

Would it be possible for someone to look into this and remove grpc; ? I think it would be preferable to not export global symbols for commonly used libs like grpc and absl, to avoid causing issues for anyone using ray alongside C extensions built with other versions of these libs.

This is currently blocking my team from upgrading to ray 1.7+.

Thanks!

Versions / Dependencies

ray==1.7.0

Reproduction script

N/A

Anything else

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!