Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Caching issue resulting in forever loading until hard refresh #859

Closed
kaihendry opened this issue Aug 2, 2019 · 4 comments
Closed

Caching issue resulting in forever loading until hard refresh #859

kaihendry opened this issue Aug 2, 2019 · 4 comments
Assignees
@kaihendry

Comments

@kaihendry
Copy link
Contributor

This appears to be some invalidation / caching header issue on Meteor. We can't reproduce the problem and it's probably quite complex. So I've proposed to send a Cloudfront invalidation request on deployment via our CD.

This invalidation can be run manually like so until it's been successfully integrated into our CD pipeline.

dev

aws --profile uneet-dev cloudfront create-invalidation --distribution-id E1VVEX26XO7MV5 --invalidation-batch "{ \"Paths\": { \"Quantity\": 1, \"Items\": [ \"/*\" ] }, \"CallerReference\": \"$(date +%s)\" }"

prod

aws --profile uneet-prod cloudfront create-invalidation --distribution-id E173XT6X8V4A18 --invalidation-batch "{ \"Paths\": { \"Quantity\": 1, \"Items\": [ \"/*\" ] }, \"CallerReference\": \"$(date +%s)\" }"
@kaihendry kaihendry self-assigned this Aug 2, 2019
kaihendry pushed a commit to kaihendry/frontend that referenced this issue Aug 26, 2019
Invalidate CloudFront cache after deploying
3c01868 
unee-t#859
@kaihendry kaihendry mentioned this issue Aug 26, 2019
Merged
nbiton pushed a commit that referenced this issue Aug 26, 2019
@nbiton
Invalidate CloudFront cache after deploying (#867)
a835513 
#859
@nbiton
Copy link
Contributor

nbiton commented Aug 26, 2019

Should have been fixed by #867

@nbiton nbiton closed this as completed Aug 26, 2019
kaihendry pushed a commit to kaihendry/frontend that referenced this issue Sep 13, 2019
Fix invalidation to use correct credentials
2e3ab6e 
unee-t#859
This might not work since deploys can timeout or fail before
invalidation is ever run. Or worse invalidation happens before the app
rolls out changes, leading the previous app to be effectively cached,
and not the new one.
@kaihendry kaihendry mentioned this issue Sep 13, 2019
Merged
@kaihendry
Copy link
Contributor Author

AWS recommend creating a lambda that triggers the invalidation like so:
https://docs.aws.amazon.com/codepipeline/latest/userguide/actions-invoke-lambda-function.html#actions-invoke-lambda-function-add-action

@kaihendry kaihendry reopened this Sep 18, 2019
kaihendry pushed a commit that referenced this issue Sep 19, 2019
Fix invalidation to use correct credentials (#875)
b9f0c20 
#859
This might not work since deploys can timeout or fail before
invalidation is ever run. Or worse invalidation happens before the app
rolls out changes, leading the previous app to be effectively cached,
and not the new one.
@kaihendry
Copy link
Contributor Author

We have a lambda but I'm unsure how to deploy across {demo,prod} accounts. I've raised an AWS support query, though yet to receive a response.

@kaihendry
Copy link
Contributor Author

CDN invalidation is done in production by https://github.com/unee-t/frontend/blob/master/.travis.yml

Demo doesn't have a CDN for debugging purposes.

There are some more deployment details upon https://forums.meteor.com/t/aws-ecs-deployment-in-2019/50282?u=hendry

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kaihendry kaihendry

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kaihendry @nbiton