You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 9, 2023. It is now read-only.
2 index nodes
1 query node
Agents and 4x services pointing to the query node
query node startup includes GRAPH_LOG_QUERY_TIMING="gql"
This graph query node deployment with GQL timing used to work fine, I wrote all my QLOG scripting on it. I recently came back to QLog and found that there are no GQL timing logs appearing in the graph node log, and when I try to pull data into QLog I end up with no data, which is what I would expect in this scenario.
There is live query traffic hitting the services - I can see indexer_service_queries_ok above zero on a small timeframe. I am assuming this traffic should be served via the query node since that's what the services are pointing to.
The only major change made since I last used this node to get QLogs was deploying multiple service nodes behind a load balancer. Below is a snippet of the node log with debugging. I have not seen this threadpool contention message before.
Configuration -
2 index nodes
1 query node
Agents and 4x services pointing to the query node
query node startup includes
GRAPH_LOG_QUERY_TIMING="gql"
This graph query node deployment with GQL timing used to work fine, I wrote all my QLOG scripting on it. I recently came back to QLog and found that there are no GQL timing logs appearing in the graph node log, and when I try to pull data into QLog I end up with no data, which is what I would expect in this scenario.
There is live query traffic hitting the services - I can see
indexer_service_queries_ok
above zero on a small timeframe. I am assuming this traffic should be served via the query node since that's what the services are pointing to.The only major change made since I last used this node to get QLogs was deploying multiple service nodes behind a load balancer. Below is a snippet of the node log with debugging. I have not seen this threadpool contention message before.
queryNodeDebug.log
The text was updated successfully, but these errors were encountered: