- This topic has 3 replies, 2 voices, and was last updated 8 hours, 53 minutes ago by
.
-
Posts
-
Hi.
I have a slice with Slice ID 85929841-cb17-4774-9f6d-90382205b226 , which shows that it is in a Stable Error condition due to insufficient resources. I am unable to to extend the lifetime for it right now. Could someone explain what the problem is? I understand that it had a slice lease expiration time. However, how could it run out of resources before the lease expiration time. Help is appreciated.
Thanks.
Hi Sourya,
When you renew or extend a slice, successful extension of all resources isn’t guaranteed. Another user may hold an advance reservation ahead of yours, blocking the renewal. This results in a partial extension, which is what’s happening here: the resources that couldn’t be extended will expire at the original expiry date, while the ones that were successfully extended remain in the Active state. You can also identify the failed slivers on the portal when you view the slice.
Best,
Komal
Hi Komal Ma’am,
Thanks for the heads up. Isn’t there any way I could save the slice from getting expired? I have some important experiments set up over there and losing them would really cause problems for me while I attempt to set them up again.Thanks.
Hi Sourya,
Unfortunately, if your resources can’t be extended because another user has a reservation ahead of yours, there isn’t much we can do on our end.
We recommend structuring your experiment notebooks so that the experiment can be easily re-provisioned and spun back up. Additionally, consider using our Distributed Storage Volumes to persist your data and context — that way, even if you need to re-provision your experiment, you can pick up right where you left off.
For details on Distributed Storage, please see this artifact: https://artifacts.fabric-testbed.net/artifacts/b2f2b34e-333e-4290-9aa7-6427b38bba15
Best,
Komal
- You must be logged in to reply to this topic.