Bug: Node that is left behind taking a long time in catching up

[capt4ce]

Description

The problem suspected from the download process which is not optimized yet for priority peers implementation. This suspected happens when the node that has been left behind trying to communicate to his peers to catch up to the latest state of blockchain but mostly got rejected because his state of priority peers is not synced with his peers.

Steps to reproduce

The problem happens really rarely, and need the above situation to be fulfilled.
The example case when it happens:

while the download activity mostly happens briefly (like it has caught up to the latest state of the block):

Expected behavior

The download process has to seamless regardless whether a node is left behind or not.