You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@superset.apache.org by gi...@git.apache.org on 2017/09/01 16:05:45 UTC

[GitHub] behanjc commented on issue #3406: Connection Error with Celery and Redis

behanjc commented on issue #3406: Connection Error with Celery and Redis
URL: https://github.com/apache/incubator-superset/issues/3406#issuecomment-326619882
 
 
   Yes, I see that. I tried with both and received the same error.
   The Elasticache is actually a cluster with 3 instances. 1 Primary and 2 replicas for redundancy.
   The endpoint host without the -001, I believe automatically redirects to the primary (001 when there are no issues), so there should be no difference. (You can see in the error traceback, that it is still pointing to -001, even though I don't specify that in the celery broker URL).
   
   In any case, the flask-cache works with both hosts, and the celery returns the same error both.
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services