-
Notifications
You must be signed in to change notification settings - Fork 14k
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
Async chart not rendering #19940
Comments
+1, the async event in polling api is always empty([]). The charts never renders. |
I'm seeing this same behavior as well, the celery worker seems to load the query fine
But the web server keeps repeatedly hitting the async endpoint, and not getting any results. Configs are class CeleryConfig(object):
broker_url = 'redis://{0}:{1}/0'.format(REDIS_HOST, REDIS_PORT)
imports = (
'superset.sql_lab',
'superset.tasks',
)
result_backend = 'redis://{0}:{1}/0'.format(REDIS_HOST, REDIS_PORT)
worker_log_level = 'DEBUG'
worker_prefetch_multiplier = 1
task_acks_late = False
task_annotations = {
'sql_lab.get_sql_results': {
'rate_limit': '10000/s',
},
'email_reports.send': {
'rate_limit': '1/s',
'time_limit': 120,
'soft_time_limit': 150,
'ignore_result': True,
},
}
CELERY_CONFIG = CeleryConfig
# On Redis
from cachelib.redis import RedisCache
RESULTS_BACKEND = RedisCache(host=REDIS_HOST, port=REDIS_PORT, key_prefix='superset_results')
# import redis
CACHE_DEFAULT_TIMEOUT = 21600 # Default timeout
GLOBAL_ASYNC_QUERIES_JWT_SECRET = ''
GLOBAL_ASYNC_QUERIES_POLLING_DELAY = 4000
GLOBAL_ASYNC_QUERIES_REDIS_CONFIG = {
"port": REDIS_PORT,
"host": REDIS_HOST,
"password": "",
"db": 0,
"ssl": False,
}
GLOBAL_ASYNC_QUERIES_TRANSPORT = "polling"
CACHE_CONFIG = {
'CACHE_TYPE':'redis', # Use Redis
'CACHE_REDIS_PORT': REDIS_PORT, # Configure port number
'CACHE_REDIS_URL':'redis://{0}:{1}'.format(REDIS_HOST, REDIS_PORT)
}
DATA_CACHE_CONFIG = {
'CACHE_TYPE':'redis', # Use Redis
'CACHE_REDIS_PORT': REDIS_PORT, # Configure port number
'CACHE_REDIS_URL':'redis://{0}:{1}'.format(REDIS_HOST, REDIS_PORT)
}
EXPLORE_FORM_DATA_CACHE_CONFIG = {
'CACHE_TYPE':'redis', # Use Redis
'CACHE_REDIS_PORT': REDIS_PORT, # Configure port number
'CACHE_REDIS_URL':'redis://{0}:{1}'.format(REDIS_HOST, REDIS_PORT)
}
FILTER_STATE_CACHE_CONFIG = {
'CACHE_TYPE':'redis', # Use Redis
'CACHE_REDIS_PORT': REDIS_PORT, # Configure port number
'CACHE_REDIS_URL':'redis://{0}:{1}'.format(REDIS_HOST, REDIS_PORT)
}
FEATURE_FLAGS = {
"ENABLE_TEMPLATE_PROCESSING": True,
"DASHBOARD_NATIVE_FILTERS": True,
"DASHBOARD_CROSS_FILTERS": True,
"VERSIONED_EXPORT": True,
"GLOBAL_ASYNC_QUERIES": True,
} Celery worker running with This is running superset 2.0.0, we may look into using websockets but at this point hard to invest the time if global async queries might not work. |
Did anyone investigate this further? Having the same problem with 2.0.0. |
Having the same issue, tried different versions, no luck |
I'm seeing similar behavior, particularly in embeds, it seems to be that there is auth / permission issues with the POST to the chart endpoint to fetch the polling data. Captured here - #18814 |
I have the same issue. I tried version 1.3.2, 1.5.2 and 2.0.0 but no luck |
+1, any update? |
+1 |
1 similar comment
+1 |
I am getting results successfully no problem |
@rohitpawar2811 What did you do differently? |
I got same problem.. is there an update related this issue..? |
I'm not sure if this is still an issue in current versions of Superset (3.x). If it is, we can re-open this, or feel free to open a new issue with updated context and a reproducible case. We're no longer supporting Superset 2.x or prior, and it's been a while since this thread saw any activity, so I'm closing this as stale. |
Can confirm that async chart queries work with @mkramer5454 's config. We're running chart version I'd recommend adding his config to the documentation of this feature. Without this issue I don't think I'd have succeeded in enabling this feature. Cheers! |
@smisch would you be willing to open a docs PR? There's an "edit this page" button in the bottom right of the docs site now which I hope makes it easier. Or if anyone wants to spell out what the instructions should be here on this thread, I can open the PR. |
@rusackas I'll check it out. Haven't been contributing on Github yet, but looks easy enough. Fork, clone, change, commit, push, propose as PR to you. |
Yep! And I think the Github website will do like half of that pretty seamlessly/smoothly if you do it from the website. Of course, forking/cloning and making edits locally is fantastic if you want to contribute to additional pages or areas of the codebase! |
Hello, I have tried to turn on GAQ on the latest helm/superset release (0.6.1, 1.5.0, respectively). When I try to run a query from a chart, the chart spins until it times out. However, I can see the query execute on the data warehouse and the results are returned to redis. In fact, if I refresh the chart page after seeing the load_chart_data_into_cache task complete successfully on the worker, then the chart pulls from redis and loads as expected. I believe that I've configured superset as outlined here.
Async queries are running as expected in sql labs.
How to reproduce the bug
Deploy superset to k8s using helm with the following config overrides:
Expected results
I expect the chart to render results after the query completes.
Actual results
The chart never renders.
Screenshots
Environment
(please complete the following information):
1.5.0
3.8.12
node -v
Checklist
Make sure to follow these steps before submitting your issue - thank you!
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: