Repository navigation
warm up cache does not work #18933
Description
A clear and concise description of what the bug is.
How to reproduce the bug
- Start celery
- Start beat
- Start flask
- There is a request from cache_warmup, but data is not be cached.
Expected results
request will be send by this order: /explore/xxx -> /explore_json/xxx or /api/v1/data/xxx
Actual results
request will be sent by this order: /explore/xxx -> break.
Screenshots
I actually setup a cookie in the request to login in with a warmup user. If I do not add this cookie, it will be redirect to login page.
here is the code I used in warm_up
Environment
(please complete the following information):
- browser type and version:
- superset version:
superset version - python version:
python --version - node.js version:
node -v - any feature flags active:
Checklist
Make sure to follow these steps before submitting your issue - thank you!
- [Y ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
- I have reproduced the issue with at least the latest released version of superset.
- [Y ] I have checked the issue tracker for the same issue and I haven't found one similar.
Additional context
Add any other context about the problem here.
Activity
srinify commentedon Feb 24, 2022
Hey @kachely this is a start but a bit more context would be useful to the community:
zhaoyongjie commentedon Feb 25, 2022
Hi @kachely, I can't reproduce on the latest master. warm-up cache works well in my local.
warm-cache.mov
kachely commentedon Mar 1, 2022
Hi @zhaoyongjie , I believe we do not use "warm_up_cache" api in the latest master in celery.
We use explore api to refresh
Please correct me if I am wrong.
kachely commentedon Mar 1, 2022
Hi @srinify , please see my responses below.
zhaoyongjie commentedon Mar 1, 2022
Hi @kachely, Could you point out which URL do you use for cache "warm up"?
kachely commentedon Mar 2, 2022
I use the url in get_rul function. It returns /superset/explore/?form_data={}.
stale commentedon May 1, 2022
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue
.pinnedto prevent stale bot from closing the issue.musicmuthu commentedon Jun 1, 2022
still the issue not solved
musicmuthu commentedon Jun 2, 2022
#.pinned #bug #pinned
atticoos commentedon Jun 4, 2022
@zhaoyongjie in your video, it appears you are sharing the same web session as the authenticated user.
The problem is that the celery worker is an unauthorized agent, and gets a
302redirect to login. egatticoos commentedon Jun 4, 2022
@kachely would you mind sharing your patches for authorizing the cache worker? I've been stuck with this for days, and #9597 has been dead for 2 years.
rgarrigue commentedon Jun 7, 2022
A workaround would be nice to share, we're having performance issues, a functional warm up could help
vnaidu-wish commentedon Jun 8, 2022
Any updates on this.
Seems like even the superset/warm_up_cache/?slice_id=XXX does not work for many charts.
i.e. echarts_area / echarts_timeseries_line
atticoos commentedon Jun 8, 2022
I got a workaround working locally on my fork, f57fab7, discussed here #9597 (comment)
But I haven't successfully built an image yet, as I am running into unrelated issues with node building the frontend
ensky commentedon Jun 15, 2022
@ajwhite I sent a PR to address this issue, which is working in my environment.
rgarrigue commentedon Jun 22, 2022
Anyone can push this PR ?
fix: cache warmup unable to login (#9597, #18933)
fix: cache warmup unable to login (#9597, #18933)
fix: cache warmup unable to login (#9597, #18933)
fix: cache warmup using WebDriver for reliable authentication
fix: cache warmup using WebDriver for reliable authentication