Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-23755

Provide more user-friendly information about locked objects in LOCKS system view.

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • sql
    • Docs Required, Release Notes Required

    Description

      We need to provide more user-friendly information about locked objects in LOCKS system view.

      At the moment, the value returned by the toString() method of the LockedKey class is displayed as the value of the locked object (OBJECT_ID).

      Example:

      OWNING_NODE_ID 1 TX_ID OBJECT_ID MODE
      ilsvt_n_0 0193537b-2340-0001-3668-6b4e00000001 LockKey [ctx=17, key=java.nio.HeapByteBuffer[pos=0 lim=3 cap=3]] X
      ilsvt_n_0 0193537b-2340-0001-3668-6b4e00000001 LockKey [ctx=null, key=16_part_16] IX
      ilsvt_n_0 0193537b-2341-0000-3668-6b4e00000001 LockKey [ctx=17, key=java.nio.HeapByteBuffer[pos=0 lim=3 cap=3]] S
      ilsvt_n_0 0193537b-2341-0001-3668-6b4e00000001 LockKey [ctx=17, key=java.nio.HeapByteBuffer[pos=0 lim=3 cap=3]] X
      ilsvt_n_0 0193537b-2341-0001-3668-6b4e00000001 LockKey [ctx=16_part_8, key=RowId [partitionId=8, uuid=00000193-537b-22a2-c8bf-bf1e67f0506e]] X
      ilsvt_n_0 0193537b-2341-0001-3668-6b4e00000001 LockKey [ctx=null, key=16_part_8] IX
      ilsvt_n_1 0193537b-2341-0000-3668-6b4e00000001 LockKey [ctx=17, key=java.nio.HeapByteBuffer[pos=0 lim=3 cap=3]] X
      ilsvt_n_1 0193537b-2341-0000-3668-6b4e00000001 LockKey [ctx=16_part_10, key=RowId [partitionId=10, uuid=00000193-537b-22a2-c402-15dd1ea44ed7]] X
      ilsvt_n_1 0193537b-2341-0000-3668-6b4e00000001 LockKey [ctx=null, key=16_part_10] IX
      ilsvt_n_1 0193537b-2341-0001-3668-6b4e00000001 LockKey [ctx=17, key=java.nio.HeapByteBuffer[pos=0 lim=3 cap=3]] S

      A more readable output format needs to be defined and implemented.

      For example:

      INDEX_ID=<ID>, partition=<ID>, key=<VALUE/HASH>, 
      TABLE_ID=<ID> partition=<ID> rowId=<ROWID>
      ...
      

      The format and information we can display must be agreed upon with the engineers working on the transaction protocol.

      p.s. please check TODOs related to this issue in the code.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              xtern Pavel Pereslegin
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: