IJ50480: ACL FILE CONTENTION WHILE RUNNING GARBAGE COLLECTION

APAR status

• Closed as program error.

Error description

• This is a short-term workaround for a customer
  performance issue allowing them to disable
  automatic ACL garbage collection.  The customer will need
  to choose a time to invoke the
  ACL garbage collection manually.
  
  Add the config option 'enableAutomaticAclGc' to disable
  ACL garbage collection
  To run ACL garbage collection  can invoke the ACL GC via
   mmfsadm test collectacl
  
  The problem was that the ACL garbage collection needs a
  XW lock on the ACL file (inode 4)
  and this was conflicting with a large number of nodes
  that needed a RO lock.
  

Local fix

Problem summary

• Long ACL garbage collection runs in the filesystem manager can
  cause lock conflicts with nodes that need to retrieve ACLs
  during garbage collection. The conflicts will resolve after
  garbage collection has finished.
  

Problem conclusion

• Added a config option ?enableAutomaticAclGc? to allow disabling
  automatic garbage collection. The customer will need to choose a
  time and invoke the ACL GC manually with enableAutomaticAclGc
  is set no.
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  SPEC SCALE ADV

• Fixed component ID

  5737F35AP

Applicable component levels