ElasticBeanstalk Sidekiq configuration

0002_sidekiq_initial.config

---
restart_sidekiq: &RESTART_SIDEKIQ
  mode: "000755"
  content: |
    #!/bin/bash
    initctl restart sidekiq || initctl start sidekiq
    ln -sf /var/app/current/log/sidekiq.log /var/app/containerfiles/logs/sidekiq.log
mute_sidekiq: &MUTE_SIDEKIQ
  mode: "000755"
  content: |
    #!/bin/bash
    . /opt/elasticbeanstalk/support/envvars
    PIDFILE=/var/app/containerfiles/pids/sidekiq.pid
    if [ -f ${PIDFILE} ]; then
      if [ -d /proc/`cat ${PIDFILE}` ]; then
        kill -USR1 `cat ${PIDFILE}`
      fi
    fi

files:
  "/opt/elasticbeanstalk/hooks/appdeploy/post/50_restart_sidekiq":
    <<: *RESTART_SIDEKIQ
  "/opt/elasticbeanstalk/hooks/appdeploy/pre/03_mute_sidekiq":
    <<: *MUTE_SIDEKIQ
  "/opt/elasticbeanstalk/hooks/configdeploy/post/50_restart_sidekiq":
    <<: *RESTART_SIDEKIQ
  "/opt/elasticbeanstalk/hooks/configdeploy/pre/03_mute_sidekiq":
    <<: *MUTE_SIDEKIQ
  "/opt/elasticbeanstalk/hooks/restartappserver/post/50_restart_sidekiq":
    <<: *RESTART_SIDEKIQ
  "/opt/elasticbeanstalk/hooks/restartappserver/pre/03_mute_sidekiq":
    <<: *MUTE_SIDEKIQ
  "/opt/elasticbeanstalk/support/conf/sidekiq.conf":
    mode: "000644"
    content: |
      description "Elastic Beanstalk Sidekiq Upstart Manager"
      start on runlevel [2345]
      stop on runlevel [!2345]
      # explained above
      respawn
      respawn limit 3 30
      script
      # scripts run in /bin/sh by default
      # respawn as bash so we can source in rbenv
      exec /bin/bash <<"EOT"
        EB_SCRIPT_DIR=$(/opt/elasticbeanstalk/bin/get-config container -k script_dir)
        EB_SUPPORT_DIR=$(/opt/elasticbeanstalk/bin/get-config container -k support_dir)
        . $EB_SUPPORT_DIR/envvars
        . $EB_SCRIPT_DIR/use-app-ruby.sh
        EB_APP_DEPLOY_DIR=$(/opt/elasticbeanstalk/bin/get-config container -k app_deploy_dir)
        EB_APP_PID_DIR=$(/opt/elasticbeanstalk/bin/get-config container -k app_pid_dir)
        cd $EB_APP_DEPLOY_DIR
        exec su -s /bin/bash -c "sidekiq -e ${RACK_ENV} -c ${SIDEKIQ_WORKERS:-2} -L ${EB_APP_DEPLOY_DIR}/log/sidekiq.log -C ${EB_APP_DEPLOY_DIR}/config/sidekiq.yml -P ${EB_APP_PID_DIR}/sidekiq.pid" webapp
      EOT
      end script

0003_sidekiq_setup.config

---
files:
  "/etc/init/sidekiq.conf" :
    mode: "120400"
    content: "/opt/elasticbeanstalk/support/conf/sidekiq.conf"
commands:
  reload_initctl_for_sidekiq:
    command: "initctl reload-configuration"

README.md

I found this config here: https://medium.com/@benhansen/setting-up-sidekiq-redis-on-aws-elastic-beanstalk-with-elasticache-2efeb32935fe#.mwv0wr59v

I've just altered it to restart sidekiq on environment variable changes, as well as manual app server restarts

@bnhansn
Is there any point that you have to run TERM? I'm noticing that when I use these scripts, long running jobs don't get pushed back to the queue. Using immutable deploy process

Example:

1. I made a job that lasts one hour & enqueued it
2. Job is running
3. I deploy
4. The previous sidekiq process is now quiet & the newly deployed process is running.
5. I see the previous sidekiq disappear & the long running job never gets enqueued again.