- This topic has 8 replies, 4 voices, and was last updated 2 years, 2 months ago by
.
-
Posts
-
Hi, how to “force” remove the slices that are stuck in closing or configuring state as I am unable to make new slice because of the old “closing” or “configuring” ones.
They will go away eventually. You can create new slices with different names though – that shouldn’t be a problem.
Yeah I am able to create new ones with different names but some slices are stuck in “Closing” state for weeks now…
I have
38d8f22e-8909-4985-ba34-3f2d63ec6cd9andc909ede9-681a-4bf1-97b8-d6b20a77a477stuck in Configuring state.c0284334-d0a4-45ea-9d5b-e9c76c9ec2c0
a87026b0-90a8-434f-af30-6c9288e7af04
35ccd9da-67da-4da3-be71-08a33bb6c926
2aa04965-b824-4f65-9093-2396ef58ad48
2988f08f-83a0-430b-a7d0-c70cf46a0b8c
9943eab4-d2b6-4a7b-9d27-5a41d6248b11
891d0cea-d834-4764-84a5-43ed55747170
0fd401cd-550a-42ed-becb-eead76d4a467
8efbccb2-6d59-4509-aa0e-54b6b404add9
767903ac-3af6-4c30-9e55-c4fa0536ab0b
54fb6706-ee71-4154-a430-4dbe4bbe3361
17c0cd6c-465f-4094-ae72-c67c5c5fb162Slices in Closing state do not have any resources allocated to them. They can be ignored. They stay in the Closing state as the confirmation for the delete response from the various Sites is not received (potentially because of the Kafka timeouts). These slices do not prevent the creation of new slices with the same name. We are working to improve the Kafka timeouts and would work to address the issue of Closing slices in the upcoming release.
Slices in Configuring state would prevent the creation of a new slice with the same name. I checked all the slices listed above and they are all in Closing state.
Thank you so much for sharing your observations and help us make the testbed better.
Please do share the slice id of the slices in Configuring state if you do run into them again.
- You must be logged in to reply to this topic.