potiuk commented on issue #10964:
URL: https://github.com/apache/airflow/issues/10964#issuecomment-1829815567

   > /home/airflow/.local/lib/python3.8/site-packages/airflow/settings.py:195 
DeprecationWarning: The sql_alchemy_conn option in [core] has been moved to the 
sql_alchemy_conn option in [database] - the old setting has been used, but 
please update your config.
   
   Update your config then. You are using a deprecated one (see the docs they 
explain which one you should use)
   
   > Using the in-memory storage for tracking rate limits as no storage was 
explicitly specified. This is not recommended for production use. See: 
[https://flask-limiter.readthedocs.io#configuring-a-storage-backend](https://flask-limiter.readthedocs.io/#configuring-a-storage-backend)
 for documentation about configuring the storage backend.
   
   You can configure rate limiting following those docs, it does not change 
much 
   
   None of this bring us any closer to finding out what happens in your case 
@tharhtetsan , And likely commenting on a close isssue is not a good idea. I 
recommend you to do one of two things:
   
   1) open a separate discussion where you explain what your problem is, 
describe your environment, how you are running and installing airflow, what 
kind of resources you have  and results of your check if you do not lack any of 
those (memory, cpu, IO, networking etc.)
   
   2) Do the same but in Slack #troubleshooting  channell (you wil find links 
to our slack in the `community` section of our documentation.
   
   


-- 
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: commits-unsubscr...@airflow.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to