panic: Some of the data has been pending for too long about minimal HOT 1 CLOSED

The Ethereum protocols keeps a linked list queue for the elements to be dowloaded. Each item in the list corresponds to a range of 190 blocks. Thus, for each item you have to download the headers, the bodies (transactions and uncles) and the receipts. Those three elements correspond to the three columns. They can either be Completed (correctly downloaded), Pending (the data is being requested now) or Waiting (the data needs to be selected to download). When a bunch of items are completed, they are processed in the blockchain (archive mode).

I think that some peers get disconnected from the client and the task manager cannot realize that the data must go back to waiting state to be allocated again to another peer. In this case, block 101461 has the bodies pending. Thus, the rest of the data that is completed cannot be flushed from memory. It executes a preemptive panic to avoid too much memory allocation on the client.

from minimal.