[IMPALA-8985] Error in profile accounting of bytes read

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: Impala 3.3.0
• Component/s: Backend
• Epic Color: ghx-label-6
• Assignee: Unassigned
• Reporter: Balazs Jeszenszky
• Created: 30/Sep/19 08:35
• Updated: 31/Oct/19 03:45

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.

Issue Links

• relates to: IMPALA-8294 Inconsistent updating of BytesRead* counters