You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@superset.apache.org by "DEPA, SHASHIDHAR REDDY [AG-Contractor/1000]" <sh...@monsanto.com> on 2017/09/11 23:07:50 UTC

Superset workers

Hi,

Is there any documentation available on spinning up superset workers on different servers?
We would like to pursue this option because of the dataset size

Any help is appreciated

Thanks
Shashi
This email and any attachments were sent from a Monsanto email account and may contain confidential and/or privileged information. If you are not the intended recipient, please contact the sender and delete this email and any attachments immediately. Any unauthorized use, including disclosing, printing, storing, copying or distributing this email, is prohibited. All emails and attachments sent to or from Monsanto email accounts may be subject to monitoring, reading, and archiving by Monsanto, including its affiliates and subsidiaries, as permitted by applicable law. Thank you.

Re: Superset workers

Posted by Maxime Beauchemin <ma...@gmail.com>.
Quick clarification that we use the term "worker" to designate 2 different
things:

gunicorn workers: if you decide to use gunicorn as your production server,
you can define how many web server processes you want to kick off on each
work. Note that you can fire off as many web servers as you want (they are
stateless), and put a load balancer in front of them

celery workers: if you want to allow for long-running queries in SQL Lab
(beyond the typical web server scope timeout), you probably want to setup a
Celery backend as described here:
http://superset.apache.org/installation.html#sql-lab

On Mon, Sep 11, 2017 at 4:07 PM, DEPA, SHASHIDHAR REDDY
[AG-Contractor/1000] <sh...@monsanto.com> wrote:

> Hi,
>
> Is there any documentation available on spinning up superset workers on
> different servers?
> We would like to pursue this option because of the dataset size
>
> Any help is appreciated
>
> Thanks
> Shashi
> This email and any attachments were sent from a Monsanto email account and
> may contain confidential and/or privileged information. If you are not the
> intended recipient, please contact the sender and delete this email and any
> attachments immediately. Any unauthorized use, including disclosing,
> printing, storing, copying or distributing this email, is prohibited. All
> emails and attachments sent to or from Monsanto email accounts may be
> subject to monitoring, reading, and archiving by Monsanto, including its
> affiliates and subsidiaries, as permitted by applicable law. Thank you.
>