Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-8985

Error in profile accounting of bytes read

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

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: Impala 3.3.0
    • Fix Version/s: None
    • Component/s: Backend
    • Labels:
      None
    • Epic Color:
      ghx-label-6

      Description

      I've seen this a few times by now:

                 - BytesRead: 571.14 MB (598886266)
                 - BytesReadDataNodeCache: 0
                 - BytesReadLocal: 1.12 GB (1197772532)
                 - BytesReadRemoteUnexpected: 0
                 - BytesReadShortCircuit: 1.12 GB (1197772532)
      

      Haven't tried reproducing it on purpose, just keeps popping up. Counters like this will get more important in cloud-backed clusters since we'll have a mismatch between our charts and what the user ends up paying for S3-based reads.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              jeszyb Balazs Jeszenszky

              Dates

              • Created:
                Updated:

                Issue deployment