How severe does this issue affect your experience of using Ray?
Medium: It contributes to significant difficulty to complete my task, but I can work around it.
Hi Team, I have been using ray for a while (never in production though) and love the ecosystem. I have been developping as a personal project a library on top of ray to write with a DSL parametrized dags, which can be deployed as APIs easily. I am using ray as a backend option and it is working on local. However, I find it difficult to understand some aspects of the API. The libary I am writing needs to be installed on the cluster, which I did with the yaml file. I have been able to easily up a cluster on aws BUT:
The cluster is using python 3.9 and my package needs python3.11>
I first tried to use init to specify the cluster address, names… but the cluster is never found.
I tried to upload the script using the job api but still did not work. The entry point of the job (which is not directly python, but an installed entrypoint) is not recognized. Here is my command approximately:
poetry run ray job submit --working-dir ./ -- fpipe run ./dag.cr --config-file ./config.yaml --input-data "{'user': {'name': 'mtoldat'}}"
Fpipe is the name of my package.
Do you have some recommendations do the things I want (leverage my package on a specific ray cluster).
I think you’ll need to post more specific information here.
For example:
The cluster is using python 3.9 and my package needs python3.11
What does that have to do with Ray? Upgrading the cluster environment to 3.11 is not an option? Ray supports Python 3.9 to 3.12 at the moment afaik.
I first tried to use init to specify the cluster address, names… but the cluster is never found.
This can have lots of reasons. If there was a single answer to each situation where one is not able to connect to the Ray cluster, I think the answer would have been given before many times. Please detail your own investigation so far, the shape of your cluster, settings etc so that it becomes possible to narrow this problem down.
I tried to upload the script using the job api but still did not work. The entry point of the job (which is not directly python, but an installed entrypoint) is not recognized.
What do you mean by “the entry point is not recognized”? Can this be narrowed down to a reproducible example?
Do you have some recommendations do the things I want (leverage my package on a specific ray cluster).
Hello Arturn, thanks for the reply. Let me answer your remarks
What does that have to do with Ray? Upgrading the cluster environment to 3.11 is not an option? Ray supports Python 3.9 to 3.12 at the moment afaik.
To my best knowledge, the documentation do not specify how to change the python version of the package
This can have lots of reasons. If there was a single answer to each situation where one is not able to connect to the Ray cluster, I think the answer would have been given before many times. Please detail your own investigation so far, the shape of your cluster, settings etc so that it becomes possible to narrow this problem down.
Do you have a ressource to help me do things right ?
What do you mean by “the entry point is not recognized”? Can this be narrowed down to a reproducible example?
I am not sure how you can reproduce this as this package is not released, but the error is the following
poetry run ray job submit --working-dir ./ -- fpipe run ./dag.cr --config-file ./config.yaml --input-data "{'user': {'name': 'mtoldat'}}"
Usage: ray job submit [OPTIONS] ENTRYPOINT...
Try 'ray job submit --help' for help.
Error: No such option: --config-file
It seems that the command entrypoint cannot be recognized when it is too complex and have some options itself.
My question is not specific as I am wondering what is the best way to achieve what I want to do (run y specific package on the cluster) as:
running with init from local fails (for unknown reason)
job cannot be launched for the reason stated before
Depending on the Python version that you install, package manager pick the right releases for you. You can install versions of Python as you wish.
Do you have a ressource to help me do things right ?
I’m afraid not. Do you have an error message at least?
I am not sure how you can reproduce this as this package is not released, but the error is the following
poetry run ray job submit --working-dir ./ -- fpipe run ./dag.cr --config-file ./config.yaml --input-data "{'user': {'name': 'mtoldat'}}"
Usage: ray job submit [OPTIONS] ENTRYPOINT...
Try 'ray job submit --help' for help.
Error: No such option: --config-file
It seems that the command entrypoint cannot be recognized when it is too complex and have some options itself.
To resolve the error message that you posted, type ray job submit --help to get some help on what the command accepts. It does not accept --config-file.