-
Notifications
You must be signed in to change notification settings - Fork 13.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Redshift could not connect to the server #3162
Comments
You can start by reading the documentation https://superset.incubator.apache.org/installation.html#sql-lab |
thanks, i missed it |
i've installed Redis, run superset worker and run superset server.. and console where worker run: [2017-07-20 14:19:45,658: WARNING/MainProcess] consumer: Connection to broker lost. Trying to re-establish the connection... During handling of the above exception, another exception occurred: Traceback (most recent call last): Where can be a problem? Thank you |
You have misconfigured celery, it's looking for an amqp broker while you said you want to use redis. |
You have to add to add proper quoting to your code excerpts otherwise it's impossible to help you. |
I tried connect to my Redshift database. There are millions of rows. When query time is longer than
one minute, Superset response is "could not connect to the server". I checked Allow Run Async, but there is another message "Failed to start remote query on worker. Tell your administrator to verify the availability of the message queue." Could you help me with this issue?
The text was updated successfully, but these errors were encountered: