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

Expose dump() call to be called externally

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • RSS Sydney
    • Party@Gregs - 2024-11-12

      From the storage engine's perspective, there is a debug_info() function that gets called within the MongoDB dump() call. The dump() call currently dumps the systems state whenever something in the system goes wrong. It would be also useful for dump() to be called from the external user perspective with the ability to configure what state to dump in the system. Follow the WiredTiger API documentation here:

      'WT_CONNECTION.debug_info' : Method([
    Config('backup', 'false', r'''
        print incremental backup information''', type='boolean'),
    Config('cache', 'false', r'''
        print cache information''', type='boolean'),
    Config('cursors', 'false', r'''
        print all open cursor information''', type='boolean'),
    Config('handles', 'false', r'''
        print open handles information''', type='boolean'),
    Config('log', 'false', r'''
        print log information''', type='boolean'),
    Config('sessions', 'false', r'''
        print open session information''', type='boolean'),
    Config('txn', 'false', r'''
        print global txn information''', type='boolean'),
]),

      The benefit will assist storage engine developers to understand what wiredtiger is doing under the hood when help tickets, and BF failures appear.

            Assignee:
            Unassigned Unassigned
            Reporter:
            jie.chen@mongodb.com Jie Chen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: