mittwald / mittwald/kube-httpcache
Purge from magento wrong behaviour
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 313
- Forks
- 82
- PR merge metrics
- No merged PRs in 30d
Description
I have 2 pods of httpcache and 2 pods of magento and when purge I can see the signal in the 2 pods of httpcache, but I can't see the changes until after a few minutes, when they are automatically updated. When only have 1 pod of httpcache I can see the changes instantly. do you know why?
- kube-httpcache version: v0.7.0
I have the vcl config recommended by magento. Need share a volume or a special vcl config for use 2 pods of httpcache?
Regards.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported setup with two kube-httpcache pods and two Magento pods, using kube-httpcache v0.7.0 and the recommended Magento VCL configuration. Compare purge propagation and cached responses between one and two httpcache pods. Done means identifying why purged changes remain stale with two pods and documenting or implementing a verified fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100