Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-1395

Automatically cancel long running queries

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.17
    • Component/s: query
    • Labels:
      None

      Description

      Queries potentially read many nodes, for example because they don't use an index or because they use join conditions that return many nodes.

      Such cases are sometimes not detected early because the default storage engine (the Tar storage) is fast. However it is a problem for slower storage engine (that stores data remotely).

      To detect such cases early on, we could add a limit on how many nodes a query may read. It might make sense to use multiple distinct limits: one for how many nodes were read but skipped, and another limit for how many nodes were read, and a third for how many nodes are kept in memory (for example for "order by" queries).

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              thomasm Thomas Mueller
              Reporter:
              thomasm Thomas Mueller

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment