Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 509
    • Issues 509
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 56
    • Merge requests 56
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • KeaKea
  • Issues
  • #2312
Closed
Open
Created Feb 14, 2022 by Francis Dupont@fdupontDeveloper

ALLOC_ENGINE_Vx_ALLOC_FAIL_CLASSES message does not make sense

The ALLOC_ENGINE_V4_ALLOC_FAIL_CLASSES message (and soon ALLOC_ENGINE_V6_ALLOC_FAIL_CLASSES message and associated counters) is triggered by a failed allocation for a query which has at least one class. As all queries are members of the ALL classes this does not make sense. Same for the KNOWN and UNKNOWN classes which are commonly used as guards too.

Note that to print classes is not a bad idea, the issue is only the assumption classes are related to the allocation failure.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking