Uploaded image for project: 'Traffic Server'
  1. Traffic Server
  2. TS-4870

Storage can be marked offline multiple times which breaks related metrics

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.0.0
    • Component/s: Cache, Metrics
    • Labels:
      None

      Description

      Let us say traffic server is running with 2 disks

      $ cat etc/trafficserver/storage.config
      /dev/sdb
      /dev/sdc
      
      $ sudo fdisk -l|grep 'Disk /dev/sd[b|c]'
      Disk /dev/sdb: 134 MB, 134217728 bytes
      Disk /dev/sdc: 134 MB, 134217728 bytes
      

      Let us see what happens when we mark the same disk 3 times in a raw (/dev/sdb) and check the proxy.node.cache.bytes_total.

      # Initial cache size (when using both disks).
      $ ./bin/traffic_ctl metric get proxy.node.cache.bytes_total
      proxy.node.cache.bytes_total 268025856
      
      # Take 1st disk offline. Cache size changes as expected.
      $ sudo ./bin/traffic_ctl storage offline /dev/sdb
      $ ./bin/traffic_ctl metric get proxy.node.cache.bytes_total
      proxy.node.cache.bytes_total 134012928
      
      # Take same disk offline again. Not good!
      $ sudo ./bin/traffic_ctl storage offline /dev/sdb
      $ ./bin/traffic_ctl metric get proxy.node.cache.bytes_total
      proxy.node.cache.bytes_total 0
      
      # Take same disk offline again. Negative value.
      $ sudo ./bin/traffic_ctl storage offline /dev/sdb
      $ ./bin/traffic_ctl metric get proxy.node.cache.bytes_total
      proxy.node.cache.bytes_total -134012928
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                gancho Gancho Tenev
                Reporter:
                gancho Gancho Tenev
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 2h 50m
                  2h 50m