You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We deployed MapFishPrint in our Kubernetes cluster. It works fine with 1 pod.
But we would like to manage a right load balancing, having N working pods behind the same service.
This does not work today, because the mapfishprint containers are not stateless, and the containers do not share the generated reports of status.
Actually, when we start an asynchronous report, we get a result with an json containing the URL we can query to get the status of our report. But this URL will be send randomly to any pod, which possibly does not know anything about our report.
How to reproduce
Just deploy many pods of MFP behind the same service in any Kubernetes cluster.
Start a asynchron report (POST)
Use the /report/status URL to query the report status
=> Sometimes, it works, sometimes you get invalid reference 'xxxxxx' because the pod does not know the report id.
Question
Is there a way to configure MapFishPrint today, in order to share the report states among all running pods?
Probably you have already solved this for the MapFishPrint SaaS Version?
Thanks,
Guillaume.
The text was updated successfully, but these errors were encountered:
Context
Describe the bug
We deployed MapFishPrint in our Kubernetes cluster. It works fine with 1 pod.
But we would like to manage a right load balancing, having N working pods behind the same service.
This does not work today, because the mapfishprint containers are not stateless, and the containers do not share the generated reports of status.
Actually, when we start an asynchronous report, we get a result with an json containing the URL we can query to get the status of our report. But this URL will be send randomly to any pod, which possibly does not know anything about our report.
How to reproduce
/report/status
URL to query the report status=> Sometimes, it works, sometimes you get
invalid reference 'xxxxxx'
because the pod does not know the report id.Question
Is there a way to configure MapFishPrint today, in order to share the report states among all running pods?
Probably you have already solved this for the MapFishPrint SaaS Version?
Thanks,
Guillaume.
The text was updated successfully, but these errors were encountered: