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

scheduler not support nuke server #549

Open
chinanoodles opened this issue Aug 3, 2022 · 3 comments
Open

scheduler not support nuke server #549

chinanoodles opened this issue Aug 3, 2022 · 3 comments

Comments

@chinanoodles
Copy link

chinanoodles commented Aug 3, 2022

hi guys,
anyone use afanasy scheduler has this problem?

One or more input nodes are not fully generated due to upstream failures. This node cannot partition input work items.
One or more input nodes are not fully generated due to upstream failures. This node cannot partition input work items.
One or more input nodes are not fully generated due to upstream failures. This node cannot partition input work items.
-- Too many errors, additional errors were suppressed. --

Warnings from node nukeserver_begin1:
Unable to schedule work item 'nukeserver_begin1_6389' using scheduler 'afanasyscheduler1' because it does not support inprocess work items.

origin_img_v2_4fa30c4c-39fc-443a-a036-90d6c08e38bg

origin_img_v2_7ca3e758-e514-41ab-9d34-ea86c9716c9g

you can use a clean nuke command chain to reproduce this issue .

thanks in advanced

@timurhai
Copy link
Member

Hi!
You can try to override top scheduler to local for inprocess work items.

@chinanoodles
Copy link
Author

hey Timur,
Thanks for the rely. I know it works for the local scheduler. But it would be super slow if run all nuke tasks locally.
are you planning on fix it in next version ?

@IcedQuinn
Copy link

I do not use Nuke but the error

This node cannot partition input work items.

sounds to me like some node you are using does not support having its work load split up?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants