Actions that the mmwatch command takes to enable a clustered watch

This topic describes how the mmwatch command enables a clustered watch in IBM Storage Scale.

Note: If any of these steps fail, all of the previous steps are returned to the pre-enablement state.
  1. The mmwatch command verifies that all of the required parameters are present either through the command line or the input file.
  2. The mmwatch command verifies that the file system that is associated with the clustered watch is mounted on the local node.
  3. The mmwatch command converts the event list to a hex bit mask.
  4. The mmwatch command creates a topic with a name in the following format: 
    SpectrumScale_WF_C_<ClusterID>_<WatchType>_<WatchID>_CLW_<Device>
  5. The mmwatch command creates and uploads the CCR file that corresponds to the requested watch. The name of the file is in the following format:
    _SpectrumScale_WF_C_<ClusterID>_<WatchType>_<WatchID>_CLW_<Device>
  6. If it is necessary (for example if the sink authentication type is CERT), the mmwatch command pushes the certificate files to all of the producer nodes.
    Note: For more information, see Interaction between the clustered watch folder and the external Kafka sink.
  7. The mmwatch command creates the policy partition for the newly created watch.