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).

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • ALL
    • Query 2020-11-30
    • 12

      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).

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

              Created:
              Updated:
              Resolved: