Scalable compute services.
Simple object storage.
Run managed Kubernetes clusters.
Tools & Integrations
Automate your infrastructure.
Deploy pre-built applications.
Connect, share and learn
DevOps and development guides
Questions & Answers
Development and systems Q&A
by Justin Ellingwood
Creation of cancel button command, to delayed or not response actions in the server.
Please add this feature
add this feature
Please add this feature.
add this feature!
Add this feature
this feature is needed!!
Need this feature to be on
please get this option for us. no phone support and we log support ticket, comes back reply after 24 hours..
Mine is also stuck in a snapshot!! Can't do anything at all - please give us control over this - at least a way to cancel irt !
pls, just do it
accidentally pressed to snapshot button (actually my cat pressed XD )
stuck in snapshot... finally turned off and now I'm stuck off :(
Please make this a feature ASAP
this feature should be ADDED!
I turned off my machine (shutdown -h now) while a snapshot was in progress (unaware of this) and now the machine is off, snapshot stuck and now I can't cancel snapshot nor can I turn on the VM....
This is high time the cancel snpashot feature worked....
Why is this STILL not implemented?
I cannot believe a company this large has such an unreliable and terrible snapshot system. Until now I had no idea.
This is literally going to cause us to abandon your entire platform as we can't have reliable backups before migrations. You're going to lose real revenue here.
Dear DigitalOcean, I do not ask you take snapshot faster. I just ask you to let me control this process. I need to cancel snapshot creation process. Otherwise I am totally blocked and I cannot do anything with my droplet while snapshot is creating.
It is very critical and should be implemented ASAP. I cannot believe that such feature request was created at 2012 and now is 2017 and it is still not implemented. FIVE YEARS?
This needs to be implemented NOW. My snapshot is stuck just like EVERYONE else. WTF
Please add this! Snapshots get stuck and the server is down for hours ... even with "LIVE" snapshots that get stuck and the server stops responding
Just do it.
Sounds good to me. Mostly just for 'whoops I forgot one thing' snapshots.
Definitely. We need a way to stop an unwanted snapshot process, at the very least. Always allow the user to stop an unwanted process, particularly if it is really long!
This is the worst Digital Ocean feature. We need a way to cancel snapshots when they fail.
This would be useful. Or at the very least it would be great to have some kind of confirmation where user is made aware that taking snapshots could take a while. I made the mistake of not powering off the machine before taking a snapshot so now I need to do it again.
I love everything, I mean everything about DigitalOcean, except this one. Had my first encounter with a frozen snapshot process on one of my servers. And just realized that there is no way to kill it. Not good!
Agree and associated with cancelling snapshot requests would be more useful feedback from the dashboard, e.g. estimated time left, any error messages if it gets stuck. At the moment you have a wordless progress bar which doesn't really tell you anything, and there is actually no official way to know if it is stuck or failing apart from that it doesn't come back after a time you subjectively decide seems too long.
Why is this still not done? DO is broken and the snapshot gets stuck and then you cant even cancel?? really fix it asap
It would be great to have a feature to cancel a droplet create in the middle of the event process in case if a user changed his mind. I mainly got this idea because of the issue that DigitalOcean had few minutes ago with slow event processing, but the same could be used in a normal day.
Suggestion opened 3 years ago... no comment. And yes, mine snapshot creation stuck on processing too.
At the very least inform us that once the process is started you CANT stop it.
yes, please allow user to cancel it.
my data is 60GB, its taking too much
Part of this rolls back to the ability to run snapshots online. I know that would solve 90% of my issues, but cancel would still be a good option.
i agree please :)
Agree there must be a way for customer to decide when the window for a snapshot is over, since the machine is offline. Can't hold the domain hostage. Not sure if the progress bar is accurate either. Look forward to Singapore-like solution with online snapshots of a mirror. Thanks!
I'd also like to be able to know more about what is happening when a snapshot is being created and cancel it if it's taking too long. Still waiting after 20 minutes.
yes, I am also facing the same snapshot stuck problem. Please add the cancel option.
snapshot is already running for 8 Min... knowing when it's going to end or being able to cancel it
For example, I pressed to take a snapshot with the server off and it got held in the processing status....
Creating a snapshot went from 3 minutes to....I have no idea as it is still running after 15 minutes. I only changed 3 config lines.....As the droplet is a very heavy used redirector, such long downtime is really bad. What makes it take this long?
Glad I found out pre-production :)
Just chiming in; definitely would love to see some sort of timer indicating how long the snapshot process is going to take with the option to cancel it.
I came here as it was Processing... longer than a previous snapshot tool. I assume this is due to some queue on your backend. Maybe you could indicate to the user how big the queue is if this is the reason. I would rather know its being stalled because of your system load rather than what seems like an inconstant failure of some kind. Anyways, snapshots are a awesome feature :)
Going to look into that and see if we can provide a way to get events cancelled before they start processing.
Interesting suggestion, definitely something we are going to look into.
Dear DO, at least, can you answer my support ticket please and cancel snapshot creation manually from your side? It is an absolutely unimaginable and unacceptable situation for a production environment!
You won't be notified about changes to this idea.