In case of an issue where mirror maker 2.0 stops replicating messages from source to destination topic, is there a recommended approach to follow/utility(except for restarting the mirror maker instance) that can be used that will minimize the impact on the destination consumers?
If the producer to the destination stops, your only option is to restart it.
You need to use external process monitoring / orchestration tools such as supervisor or Kubernetes to restart the process/containers that fail.