Hello,
I’m currently using three servers:
- Ignition Server A (MAIN)
- Ignition Server B
- Database Server C
These servers are configured in a redundancy setup, with A ↔ B as redundant servers. Only Ignition Server A writes tag history data to Database Server C.
However, I’ve been observing that the Gateway Database Connections on Ignition Server A frequently fluctuate between 3/8 and 8/8, and sometimes reach full capacity (8/8), causing disconnections.
From my understanding, only two servers (A and B) are connected to the database, but I don’t understand why the connections are maxing out. Additionally, I’m unclear about the exact criteria for counting these database connections.
For reference, there are two clients viewing the screens.
I’d really appreciate any help or clarification on this issue. Thank you!
Ignition uses additional connections to DBs depending on workload. If you have a long running query and something else submits a query, ignition will use another connection to avoid stalling the second query.
If you have lots of long running queries, then its possible for your gateway to consume all the allowed connections in the connection pool. Each gateway gets its own connection pool.
I'd start by investigating if you have any long running queries. If you do, see if the tables they are querying have the necessary indexes. Also make sure you are not querying extremely large amounts of data more than necessary.
What data are your two vision clients querying? I wouldn't expect it to be eating all your connections unless something is really wrong.
Tag history will also use db connections, so maybe check your history configurations to make sure you aren't logging too much data.
1 Like
This. There's a status page that will show them.
2 Likes