Why Is a Dedicated Resource Pool That Fails to Be Created Still Displayed on the Console After It Is Deleted?
After a dedicated resource pool is deleted on the console, the backend releases the resources used by the pool. It takes several minutes to release the resources, during which the pool is still displayed on the console. To create a dedicated resource pool again, wait for 5 minutes after the deletion. Additionally, do not use the name of the dedicated resource pool that fails to be created to name the new dedicated resource pool. To perform an automated test on the UI, it is a good practice to use a random string as the name of the created dedicated resource pool.
Resource Pools FAQs
- Can I Use ECSs to Create a Dedicated Resource Pool for ModelArts?
- Can I Deploy Multiple Services on One Dedicated Resource Pool Node?
- How Is a Node Newly Added to a Dedicated Resource Pool Billed?
- What Are the Differences Between a Public Resource Pool and a Dedicated Resource Pool?
- How Do I Log In to a Dedicated Resource Pool Node Through SSH?
- How Are Training Jobs Queued?
- What Do I Do If Resources Are Insufficient for Staring a New Real-Time Service After I Stop a Real-Time Service in a Dedicated Resource Pool?
- Can a Public Resource Pool Be Used for Network Connection Between ModelArts and the Authentication Service for Running Algorithms?
- Why Is a Dedicated Resource Pool That Fails to Be Created Still Displayed on the Console After It Is Deleted?
- How Do I Add a VPC Peering Connection Between a Dedicated Resource Pool and an SFS?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
