thammaneni edited a comment on issue #9236: Email scheduling functionality not 
working in docker container
URL: 
https://github.com/apache/incubator-superset/issues/9236#issuecomment-595191121
 
 
   > Hi @thammaneni - it appears that your tasks are running into a default 
time limit configured in `superset/config.py` under the `CELERY_ANNOTATIONS` 
constant. I'm not sure why your tasks start taking longer after an hour, but I 
would experiment with altering the configuration on your install to allow for a 
longer `soft_time_limit` and `hard_time_limit`. Here are the relevant line in 
the Superset configuration:
   > 
   > 
https://github.com/apache/incubator-superset/blob/7a91498cf1a9e56d4b3d7b3805076137525ea277/superset/config.py#L479-L480
   
   @willbarrett , Thanks for the reply.
   i have increased the  time limits from configuration file like below.
   "time_limit": 300, 
    "soft_time_limit": 350,
   I restarted and scheduled, initial one hour i am able receive emails after 
that i started getting the Timeout error again. is there any other reason 
related to memory capacity increment or what is taking long time to fetch data 
from response object ?
   
   **Error Info:**
   [2020-03-05 06:25:51,285: WARNING/MainProcess] Soft time limit (350s) 
exceeded for email_reports.send[c4ba4cbc-ef85-41ee-824f-15611e36129c]
   [2020-03-05 06:25:51,287: ERROR/MainProcess] Task handler raised error: 
TimeLimitExceeded(300)
   Traceback (most recent call last):
     File "/usr/local/python3.7/lib/python3.7/site-packages/billiard/pool.py", 
line 658, in on_hard_timeout
       raise TimeLimitExceeded(job._timeout)
   billiard.exceptions.TimeLimitExceeded: TimeLimitExceeded(300,)
   [2020-03-05 06:25:51,287: ERROR/MainProcess] Hard time limit (300s) exceeded 
for ftp_reports.send[c4ba4cbc-ef85-41ee-824f-15611e36129c]
   [2020-03-05 06:25:51,405: ERROR/MainProcess] Process 'ForkPoolWorker-2' 
pid:2771 exited with 'signal 9 (SIGKILL)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to