sidekiq webapp in multiserver deploy scenarios

[Patrick Cullen]

We run two rails servers on EC2.  Both servers also run redis and sidekiq.  We use AWS Elastic Load Balancer to distribute requests.  When we access the sidekiq web app like so: example.com/sidekiq, we get sidekiq stats for whichever server the load balancer happened to send the request to.  As the app polls, the stats are updated to whichever server the load balancer happened to send the xhr stat request to, making it difficult to retry etc...   Is there a way to configure the web app so that it is aware of multiple sidekiq instances or so that it provides a global view of all the jobs (and ways to interact, eg retry, remove)?  Or any other recommendations for using the web app in multi-server setups like this? 

Thanks for the great product.

-P

[Mike Perham]

Sidekiq is designed to run in a typical master/replica architecture, not a multi-master system.  You need to either make one of the instances master or switch to something like ElasticCache which will have the same effect.

http://docs.aws.amazon.com/AmazonElastiCache/latest/UserGuide/WhatIs.html

--
You received this message because you are subscribed to the Google Groups "Sidekiq" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sidekiq+u...@googlegroups.com.
To post to this group, send email to sid...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sidekiq/f0c812af-0d18-4ac1-aec4-2482f45ca081%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Mike Perham – CEO, Contributed Systems

Smart, effective open source infrastructure for your apps.