Identify high-traffic clients or files

Contributors

You can use ONTAP Active Objects technology to identify clients or files that are responsible for a disproportionately large amount of cluster traffic. Once you have identified these "top" clients or files, you can rebalance cluster workloads or take other steps to resolve the issue.

What you’ll need

You must be a cluster administrator to perform this task.

Steps
  1. View the top clients accessing the cluster:

    statistics top client show -node node_name -sort-key sort_column -interval seconds_between_updates -iterations iterations -max number_of_instances

    For complete command syntax, see the man page.

    The following command displays the top clients accessing cluster1:

    cluster1::> statistics top client show
    
    cluster1 : 3/23/2016 17:59:10
    
    
                                                   *Total
            Client Vserver           Node Protocol    Ops
    -------------- ------- -------------- -------- ------
    172.17.180.170     vs4 siderop1-vsim4      nfs    668
    172.17.180.169     vs3 siderop1-vsim3      nfs    337
    172.17.180.171     vs3 siderop1-vsim3      nfs    142
    172.17.180.170     vs3 siderop1-vsim3      nfs    137
    172.17.180.123     vs3 siderop1-vsim3      nfs    137
    172.17.180.171     vs4 siderop1-vsim4      nfs     95
    172.17.180.169     vs4 siderop1-vsim4      nfs     92
    172.17.180.123     vs4 siderop1-vsim4      nfs     92
    172.17.180.153     vs3 siderop1-vsim3      nfs      0
  2. View the top files accessed on the cluster:

    statistics top file show -node node_name -sort-key sort_column -interval seconds_between_updates -iterations iterations -max number_of_instances

    For complete command syntax, see the man page.

    The following command displays the top files accessed on cluster1:

    cluster1::> statistics top file show
    
    cluster1 : 3/23/2016 17:59:10
    
    					              *Total
                        File Volume Vserver          Node    Ops
    ------------------------ ------ ------- -------------- ------
    /vol/vol1/vm170-read.dat   vol1     vs4 siderop1-vsim4     22
    /vol/vol1/vm69-write.dat   vol1     vs3 siderop1-vsim3      6
         /vol/vol2/vm171.dat   vol2     vs3 siderop1-vsim3      2
         /vol/vol2/vm169.dat   vol2     vs3 siderop1-vsim3      2
          /vol/vol2/p123.dat   vol2     vs4 siderop1-vsim4      2
          /vol/vol2/p123.dat   vol2     vs3 siderop1-vsim3      2
         /vol/vol1/vm171.dat   vol1     vs4 siderop1-vsim4      2
         /vol/vol1/vm169.dat   vol1     vs4 siderop1-vsim4      2
         /vol/vol1/vm169.dat   vol1     vs4 siderop1-vsim3      2
          /vol/vol1/p123.dat   vol1     vs4 siderop1-vsim4      2