Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[core][experimental] Throw exceptions for unsupported multi-node accelerated DAG cases #45603

Open
stephanie-wang opened this issue May 28, 2024 · 1 comment · May be fixed by #46283
Open

[core][experimental] Throw exceptions for unsupported multi-node accelerated DAG cases #45603

stephanie-wang opened this issue May 28, 2024 · 1 comment · May be fixed by #46283
Assignees
Labels
accelerated-dag enhancement Request for new feature and/or capability P1 Issue that should be fixed within a few weeks

Comments

@stephanie-wang
Copy link
Contributor

stephanie-wang commented May 28, 2024

Description

Not all multi-node cases are currently supported:

We should document these cases and throw the appropriate errors if the case occurs.

Use case

No response

@stephanie-wang stephanie-wang added enhancement Request for new feature and/or capability triage Needs triage (eg: priority, bug/not-bug, and owning component) labels May 28, 2024
@stephanie-wang stephanie-wang added accelerated-dag P1 Issue that should be fixed within a few weeks and removed triage Needs triage (eg: priority, bug/not-bug, and owning component) labels May 28, 2024
@stephanie-wang stephanie-wang added this to the ADAG Developer Preview milestone May 28, 2024
@anyscalesam
Copy link
Collaborator

Handling via exceptions is enough for Developer Preview but we should actually support the use case when data sizes are larger than the gRPC limit as well as the reading of the same value spread across nodes.

We'll get to this after Developer Preview.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accelerated-dag enhancement Request for new feature and/or capability P1 Issue that should be fixed within a few weeks
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants