Digital Ocean Server goes down with High Network Input/Output

Viewed 11

I have a simple nodejs/react setup in docker compose which is currently deployed in digital ocean droplet (1 GB Memory / 1 AMD vCPU / 25 GB Disk). Problem is, sometimes my server goes down and I can't ssh to the droplet to check the logs. One thing I found in the graphs of the droplet is a gap on all metrics and a spike in network i/o

enter image description here

enter image description here

There is no attack on our network side as per checking and no weird things in our application logs. Any idea what's happening or what can i check here?

Here is my docker compose

version: '3'
services:
  accounts:
    image: redacted
    restart: unless-stopped
    env_file:
      - ./environment/prod/.env.acc.prod
    volumes:
      - /var/log/app:/var/log/app
    deploy:
      resources:
        limits:
          cpus: '0.25'
          memory: 250M
  bank:
    image: redacted
    restart: unless-stopped
    env_file:
      - ./environment/prod/.env.bank.prod
    volumes:
      - /var/log/app:/var/log/app
    deploy:
      resources:
        limits:
          cpus: '0.25'
          memory: 250M
  bet:
    image: redacted
    restart: unless-stopped
    env_file:
      - ./environment/prod/.env.bet.prod
    volumes:
      - /var/log/app:/var/log/app
    deploy:
      resources:
        limits:
          cpus: '0.25'
          memory: 250M
  game:
    image: redacted
    restart: unless-stopped
    env_file:
      - ./environment/prod/.env.game.prod
    volumes:
      - /var/log/app:/var/log/app
    deploy:
      resources:
        limits:
          cpus: '0.25'
          memory: 250M
  promotions:
    image: index.docker.io/gdtech888/be_promotions:1.0
    restart: unless-stopped
    env_file:
      - ./environment/prod/.env.promo.prod
    volumes:
      - /var/log/app:/var/log/app
    deploy:
      resources:
        limits:
          cpus: '0.25'
          memory: 250M
  websocket:
    image: redacted
    restart: unless-stopped
    deploy:
      resources:
        limits:
          cpus: '0.25'
          memory: 250M
  frontend:
    image: redacted
    restart: unless-stopped
    env_file:
      - ./environment/prod/.env.frontend.prod
    deploy:
      resources:
        limits:
          cpus: '1'
          memory: 1G

0 Answers
Related