Hello everyone,
I have an Argilla Space with paid persistent storage. When coming back after a day or two of inactivity, I’m seeing the following error in my space during space start up:
Saying:
Runtime error
Scheduling failure: not enough hardware capacity
Container logs:
===== Application Startup =====
I’ve tried restarting the space but this doesn’t work.
Has anyone encountered a similar issue? I’m also thinking of upgrading the CPU, would I loose all uncommitted data (we had an annotator do an Eval run and this hasn’t been pushed to a dataset yet)?
Thanks in advance for any help!
1 Like
Same error here - happened to me on both free and upgraded-CPU Argilla instances today; I was able to spin up one of my Argilla spaces earlier this morning however have been running in the same error ever since. Restarting the environment typically would solve this when I have encountered it.
Re: upgrading the CPU - you won’t loose your uncommitted annotations from my experience (downgrading the CPU back to a free tier should not cause such an error either) but it did not seem to solve this problem on my end.
2 Likes
Update: Unsure if this is related to other errors people have been experiencing with spaces but thought it is worth trying to rebuild the Argilla spaces again as another error was just reported as fixed (namely this one: [ERROR] Get error when deploy space).
Have been able to spin up both free and CPU-upgraded Argilla instances without issue just now so I’d recommend simply restarting once again.
1 Like
Thanks for the update. I just checked and it looks like my space is now back to normal after a restart!
2 Likes