Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-52973

CursorID (long long) printed via LOGV2 can print corrupted value (lower-order bytes altered).

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Cannot Reproduce
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Operating System:
      ALL
    • Sprint:
      Query 2020-11-30
    • Linked BF Score:
      12

      Description

      Came from investigation on BF-18408. It seems like a platform/hardware specific bug. Not able to reproduce in my local machine but I was able to reproduce on Amazon EC2 instance.

      E.g., cursor id 8388079694692667449, when printing via LOGV2 (or via javascript layer print()) it displays some corrupted value, like, 8388079694692667000.

      P.S: Based on my analysis, the real data isn't corrupted, just the value that gets printed are corrupted (both in c++ and javascript layer).

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mindaugas.malinauskas Mindaugas Malinauskas
              Reporter:
              suganthi.mani Suganthi Mani
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: