IJ18710: TSLSPOOL34 ASKS FOR XW LOCK OF INODE 3 WHICH CAUSE CLUSTER WIDE

APAR status

• Closed as program error.

Error description

• tslspool34 "fs_mount_point" will call gpfs_stat() on that
  root directory which need acquire xw token of the inode
  3.
  It causes cluster wide token revoke and long waiters on
  busy large cluster.
  

Local fix

Problem summary

• Problem descriptiption:
  tslspool34 is called by GPFSPool zimon sensor which may cluster
  wide token contention on root directory of file system
  

Problem conclusion

• Benefits of the solution:
  Avoid the token contention by using weaker token mode for
  tslspool34 command
  
  Work Around:
  None
  
  Problem trigger:
  tslspool34 is called by GPFSPool zimon sensor which will run
  once every 5 minutes.
  Per 5.0.3, zimon sensor will run on all nodes which will cause
  lots token contention Since 5.0.3, zimon sensor runs on
  restrict nodes
  
  Symptom:
  Performance Impact/Degradation
  
  Platforms affected:
  ALL Linux OS environments
  
  Functional Area affected:
  perfmon (Zimon)
  
  Customer Impact:
  Suggested
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  IJ18238

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  SPECTRUM SCALE

• Fixed component ID

  5725Q01AP

Applicable component levels