nytai commented on issue #16742: URL: https://github.com/apache/superset/issues/16742#issuecomment-965616327
@ValentinC-BR This error is being thrown by nginx or whichever proxy is in front of superset. 502 means the service(superset) is unavailable, either the superset server hash crashed (out of memory or cpu, etc.), or is too busy to serve your request. This is error is due to your deployment set up and there's nothing we can do on the superset application side, at least not without the log/stack trace for what actually caused the service to report as unavailable. Closing this issue as this is not actionable from an application perspective. If you do a root cause analysis that results in an issue with the superset application please feel free to reopen the ticket. For now I would suggest scaling up your superset deployment, either vertically or horizontally to see if that fixes it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
