GitHub user dosubot[bot] added a comment to the discussion: Superset 4.11 hangs 
after a period of user inactivity

<!-- Greeting -->
Hey @manishtiwari-ie! I'm here to help you with any bugs, questions, or 
contributions you have for Superset. Let's squash those bugs together!

<!-- Answer -->
The issue you're experiencing with Superset hanging after a period of 
inactivity and the Gunicorn workers exiting with code 120 could be related to 
several factors, including timeout settings or resource limits.

1. **Gunicorn Timeout**: Ensure that the Gunicorn timeout setting is configured 
appropriately. The default timeout is 60 seconds, but it can be extended to 300 
seconds to accommodate long-running queries. You can adjust this setting in 
your Gunicorn configuration or command line by using the `--timeout` option.

2. **Worker Connections**: If you're using asynchronous workers, such as 
`gevent`, ensure that the `--worker-connections` setting is high enough to 
handle the number of concurrent connections. A typical configuration might be 
`-w 10 -k gevent --worker-connections 1000` for high concurrency.

3. **Logging and Debugging**: Since the error involves an `OSError: [Errno 5] 
Input/output error`, it might be related to issues with writing logs or output. 
Ensure that the file system where logs are being written is stable and has 
sufficient space. Additionally, check if there are any restrictions or issues 
with the terminal or console where the application is running.

4. **Configuration File**: Verify that your Superset configuration file is 
correctly set up and accessible. The error in the logs indicates an issue with 
loading the configuration, which might be causing the workers to fail.

5. **Resource Limits**: Check if there are any system-level resource limits 
(e.g., file descriptors, memory) that might be affecting the Gunicorn workers. 
Adjust these limits if necessary.

By addressing these areas, you should be able to mitigate the issue of Superset 
hanging after inactivity and the Gunicorn workers exiting unexpectedly.


<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*

---
<sup>Help Dosu learn! Give it feedback: [Great 
Response](https://app.dosu.dev/response-feedback/8d92cdad-7c86-447b-a891-7ae370ae2747?feedback_type=great_response)
 | [Irrelevant 
Answer](https://app.dosu.dev/response-feedback/8d92cdad-7c86-447b-a891-7ae370ae2747?feedback_type=irrelevant_answer)
 | [Incorrect 
Sources](https://app.dosu.dev/response-feedback/8d92cdad-7c86-447b-a891-7ae370ae2747?feedback_type=incorrect_sources)
 | [Too 
Verbose](https://app.dosu.dev/response-feedback/8d92cdad-7c86-447b-a891-7ae370ae2747?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/8d92cdad-7c86-447b-a891-7ae370ae2747?feedback_type=hallucination)
 | [Bug 
Report](https://app.dosu.dev/response-feedback/8d92cdad-7c86-447b-a891-7ae370ae2747?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/8d92cdad-7c86-447b-a891-7ae370ae2747?feedback_type=other)</sup>


GitHub link: 
https://github.com/apache/superset/discussions/32766#discussioncomment-12561287

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: 
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to