Messages requeuing in AFM

The courses of action to be followed for resolving the requeued messages in the Gateway node.

Sometimes requests in the AFM messages queue on the gateway node get requested because of errors at home. For example, if there is no space at home to perform a new write, a write message that is queued is not successful and gets requeued. The administrator would see the failed message getting requeued in the queue on the gateway node. The administrator has to resolve the issue by adding more space at home and running the mmafmctl resumeRequeued command, so that the requeued messages are executed at home again. If mmafmctl resumeRequeued is not run by an administrator, AFM would still execute the message in the regular order of message executions from cache to home.

Running the mmfsadm dump afm all command on the gateway node shows the queued messages. Requeued messages show in the dumps similar to the following example:

c12c4apv13.gpfs.net:    Normal Queue:  (listed by execution order) (state: Active)
c12c4apv13.gpfs.net:      Write [612457.552962] requeued file3 (43 @ 293) chunks 0 bytes 0 0