ExportXMLWordPrintableJSON

    • Storage Engines - Transactions
    • Minor Change
    • ALL
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      WiredTigerUtilTest.GetStatisticsValueInvalidKey asserts that looking up a connection statistics key `WT_STAT_CONN_SESSION_OPEN` through a table statistics cursor fails with NoSuchKey.

      A table cursor only accepts keys from WT_STAT_DSRC_BASE (2000) upward. Connection keys start at 1000, but there are now more than 1000 of them, so the connection range overlaps the table range.

      The test only passed because WT_STAT_CONN_SESSION_OPEN was 1994, just below 2000. WT-18993 added more stats so that WT_STAT_CONN_SESSION_OPEN became 2000, which is the same key as WT_STAT_DSRC_AUTOCOMMIT_READONLY_RETRY. The lookup then succeeds and ASSERT_NOT_OK fails.

      We should use the first connection key for the test instead of WT_STAT_CONN_SESSION_OPEN which is alphabetically towards the end of connection stats. The first connection key should stay below the table key range, however many stats are added so further connection stat added before it should not break the test again.

      Follow-up Fix in WT: making the two key ranges non-overlapping would fix the root cause, which is a larger WiredTiger change.

       

            Assignee:
            Alana Huang
            Reporter:
            Alana Huang
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: