2 years ago
Hi,
I have two deployments that appear to be stuck, but they were not showing as active on the platform. I discovered this issue because my database continues to receive data from them. I tried deleting the service, but this did not resolve the problem. It was only after attempting deletion that I found the following IDs for the deployments:
Deployment 1:
- Deployment ID: 3d76873e-9ee2-4e86-a61a-64a61a3d6b48
- Replica ID: 8749c0c3-0fe3-4c1b-951f-03019ca7ee7a
- Service ID: e6f98b40-ccbb-42c9-96f3-a09b80e3822a
Deployment 2:
- Deployment ID: eb436ab5-b87e-48d1-96f1-f955e3220c2b
- Replica ID: 2029ae61-5900-4f69-8215-bc924878fb40
- Service ID: e6f98b40-ccbb-42c9-96f3-a09b80e3822a
Could someone help me with this issue? How can I fully stop these deployments and ensure they are no longer affecting my database?
Thanks in advance for your assistance.
4 Replies
2 years ago
Hi Stevan,
Quick update to let you know we're currently looking into this.
Regards, Christian
Status changed to Awaiting User Response Railway • almost 2 years ago
2 years ago
Okay, thanks for letting me know
Status changed to Awaiting Railway Response Railway • almost 2 years ago
2 years ago
Hi Stevan,
The containers were indeed not properly stopped when you stopped and later removed your service, caused by a rare stuck workload on our end. We've now stopped the containers, and you shouldn't see any more data coming from them. Let us know if you see anything unexpected here.
Regards,
Christian
Status changed to Awaiting User Response Railway • almost 2 years ago
2 years ago
It is really resolved, thank you.
Status changed to Awaiting Railway Response Railway • almost 2 years ago
Status changed to Solved brody • almost 2 years ago