Output of 'top' command on a cluster member shows that routed process consumes CPU at 100%.
Output of 'ps auxw' command shows that the PID of problematic routed process belongs to RouteD instance manager - "routed -N".
No apparent impact on the machine is experienced.
/var/log/dump/usermode/ folder (refer to sk92764) might show core dump files for routed process. These core dump files contain the following stack:
#0 0x... in clock_gettime () from /lib/librt.so.1
#1 0x... in monotime (...) at os/monotime.c
#2 0x... in task_timer_time_update (...) at task/task_timer.c
#3 0x... in task_process_sockets (...) at task/task_socket.c
#4 0x... in main (...) at task/task_init.c
Output of strace tool attached to the problematic routed process repeatedly shows the following lines during the issue: