When hashadow restarts had, it uses a "-restart" argument, which remains visible afterwards.

The "-restart" argument simply indicates that had restarted at some point in the past. It does not mean that a had restart is pending. The argument is a remnant of the fact that hashadow restarted had with a “had –restart" command.

Depending on the reason for the restart, it is possible that hashadow may restart had again in the future. This is common on nodes that are experiencing high CPU utilization or are experiencing problems with the cluster heartbeat network. Check relevant logs, such as engine_A.log, or the system messages log, to determine why had was restarted.