GitHub user archsyscall added a comment to the discussion: Should Airflow keep SQLAlchemy connection pooling enabled when using PgBouncer (transaction pooling mode)?
@potiuk Thank you for your response. What about the opposite case — disabling API pooling while keeping PgBouncer for pooling? After trying your suggestion and removing PgBouncer, the main issue we encountered was that it became difficult to centrally manage the total number of database connections. When using PgBouncer, we only needed to monitor the PgBouncer pool count. However, without it, we now have to manage and coordinate multiple factors — such as the number of API replicas, each API server’s internal pool size, and the number of schedulers — to control overall connection usage. GitHub link: https://github.com/apache/airflow/discussions/56890#discussioncomment-14737954 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
