Debugging and performance-monitoring statistics for offloaded data transfer

Offloaded data transfer (ODX) infrastructure captures debug and monitoring information for specific ODX modules and makes it available in global and local views.

Debug and monitoring information for specific ODX modules is available in global and local views. The facility to maintain historical data for certain time periods is also available. It currently represents the historical data in eight entries in the global and local views.

Global view

In this view, ODX infrastructure displays the information at the node level. ODX infrastructure provides the memory to represent the module information. It can also capture the historical data for a certain time period. An example of the information is open system interconnect (OSI) command-related information (populate token, write using token, command failure, token revoked, and other commands). ODX infrastructure provides the following facilities to capture the data as part of the global view:
  • MAX - maximum

    MAX represents the largest/maximum value along with the time stamp in the base object. Whenever you update the object, it can maintain the history for the last X time period if needed. Through the history, information on how many times the MAX is reached on the last X time period becomes known.

  • MIN - minimum
  • CUMULATIVE - cumulative

    CUMULATIVE represents the cumulative value along with time stamp in the base object. It can also maintain the history for the last X time period. Through the history, the frequency of failures on the last X time period becomes known.

Table 1 lists the global (node level) parameters.
Table 1. ODX debug global parameters
Command Statistic
max pt cmd entry Maximum simultaneous ODX PT commands arrived at OSI layer
max pt cmd exit Maximum simultaneous ODX PT commands exited at OSI layer
max wut cmd entry Maximum simultaneous ODX WUT commands arrived at OSI layer
max wut cmd exit Maximum simultaneous ODX WUT commands exited at OSI layer
cmd failure cumulative history Total number of ODX commands failure happened during ODX copy operation
token revoked cumulative history Total number of ODX tokens revoked happened during ODX copy operation
send ops history by comm Total number of communication messages that are sent by a node to all nodes as part of ODX copy operation
send kb data history by comm Total amount (KBs) of cluster-wide data that is sent by a node as part of ODX copy operation
send & rcvd ops history by comm Represents clustering operations that are generated by a node (Number of messages sent & received)
send & rcvd kb data history by comm Represents clustering traffic that is generated by a node (Data sent & received in KBs)

Local view

In this view, ODX infrastructure displays the information at the VDisk level. ODX infrastructure provides the following facility to capture the data as part of the local view:
  • COPY SPECIAL - cumulative

    COPY SPECIAL is specific to the copy job manager. It maintains the history of ODX I/O (read and write) average latency for the last X time period. It has a local view only.

Table 2 lists the local (volume level) parameters.
Table 2. ODX debug local parameters
Command Statistic
Average READ latency (ms) Offload read (ODX) average latency in milliseconds (ms)
Average WRITE latency (ms) Offload write (ODX) average latency in milliseconds (ms)