Skip to content

Disconnected when in burstable zone

0

I keep getting disconnected from my instance in VS code remote develop whenever it enters the burstable zone, i cannot access using SSH neither from the Lightsail console. My application halts and all the services as well. I have a 2gb RAM instance with a really small node app with mongodb, as it is a really small deployment the compute power and memory should be more than enough to carry it. This is a show stopper for me and i need to know if there's an answer or move to another cloud provider that gives a solution as paying 10 USD monthly for a buggy instance is too much.

asked 2 years ago393 views
4 Answers
1
Accepted Answer

For the record and for the sake of helping anyone facing this same issue as Lightsail users won't get technical assistance; The solution isn't to upgrade your instance... as 2VCPUs and 1-2 gb RAM is a lot for a micro service or a webpage in wordpress... the solution is to set a swap file to double of your instance's RAM. By default neither bundle has a swapfile, this means when you face a memory usage spike the OS will kill any process to free some memory including SSH.

This command will help you to create a swap file... sudo fallocate -l 4G /swapfile && sudo chmod 600 /swapfile && sudo mkswap /swapfile && sudo swapon /swapfile && sudo sed -i '$ a/swapfile swap swap defaults 0 0' /etc/fstab

Jorge

answered 2 years ago
  • Thank you very much Jorge! I was struggling since weeks with this problem. My WP was running lightning fast with Lightsail on a Bitnami 2 GB RAM, 2 vCPUs, 60 GB SSD. But, when uploading a bit heavier media files (+/- 1MB) I was hitting the burstable zone with a strong curve up to 50% and the instance completely shut down, including SSH. After creating a swap file according to your recommendation, my Lightsail instance is running absolutely smooth and when uploading heavy media files the curve does not jump into the sky like before but it keeps growing slowly without hitting the burstable zone at all. I believe that his should be an issue for any Lightsail user and you saved us lots of headaches.

0

Hello.

Is it possible to connect using ssh command etc. instead of via VSCode when bursting?
Also, have you ever used up all your burst credits when you were unable to connect?
https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-viewing-instance-burst-capacity

EXPERT
answered 2 years ago
  • No, it's impossible to connect via ssh directly. As for the second question, never I'm always over 90% of burstable credits. I'm wondering if there's any issue regarding nodeJS. I've already migrated instance twice using snapshots as well as clean install, I always face this issue.

0

Just to complement, my burstable graph looks like this and sometimes it takes over 30 min to let me connect again and by then my nohup node process running was dropped and my service halted.

Enter image description here

answered 2 years ago
0

Hi, Thank you for reaching out to us about the issue you are facing. Some of your instances reaching 100% CPU Utilization may be causing the disconnection problem. We recommend upgrading to larger bundles from smaller ones, as this can help alleviate the issue of CPU Utilization reaching 100%.

AWS
SUPPORT ENGINEER
answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.