Skip to content

[3.12.4] arangodb_aql_current_query shows invalid uint64 value (overflow?) on SINGLE setup #21777

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
sashapetrov opened this issue May 19, 2025 · 3 comments · May be fixed by #21785
Open

[3.12.4] arangodb_aql_current_query shows invalid uint64 value (overflow?) on SINGLE setup #21777

sashapetrov opened this issue May 19, 2025 · 3 comments · May be fixed by #21785

Comments

@sashapetrov
Copy link

Issue

The metric arangodb_aql_current_query returns a huge value close to uint64 max, while there are no active queries (queries.current() returns empty).

This appears to be a misreporting issue, possibly due to counter overflow or internal state corruption.

Example output:

arangodb_aql_current_query{role=“SINGLE”} 18446744073708371286

Environment:

  • ArangoDB version: 3.12.4 (Community)
  • Architecture: SINGLE
  • OS: Ubuntu 22.04 (if applicable)
  • Cluster mode: No, single instance
  • How started: systemd service (not in Docker)

Additional info:

  • queries.current() returns empty array
  • No recent errors or warnings in logs (journalctl -u arangodb3.service)
  • Metric /admin/metrics is used directly by Prometheus

Expected Behavior

The metric should report the actual number of running AQL queries (typically 0), or at most a reasonable number, not 18446744073708....

💬 Let me know if further debug output or /metrics dump is needed.
@maierlars
Copy link
Contributor

Probably a Gauge was decremented more often than it was incremented. Might be related to the latest changes in query shutdown. @goedderz @jbajic

@sashapetrov
Copy link
Author

Will this be fixed in a future release?
Any known workaround?

@jbajic
Copy link
Contributor

jbajic commented May 24, 2025

I am getting the same huge number. We don't increment the counter for some queries, and then still decrease the counter for those queries. We will try to fix it, and I will let you know once we have the fix

@jbajic jbajic linked a pull request May 26, 2025 that will close this issue
Open
19 tasks
@jbajic jbajic linked a pull request May 26, 2025 that will close this issue
Fix query counter gauge #21785
Open
19 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix query counter gauge arangodb/arangodb
3 participants
@jbajic @maierlars @sashapetrov