: While rooted in military history, the same blank gaze is seen in victims of violence, accidents, or any severe psychological trauma. Cultural and Historical Impact
: The stare continues to be portrayed in film and literature to represent a character's internal collapse or loss of innocence.
: The Marine in the painting had been in combat for 31 months, surviving tropical diseases and relentless fighting while most of his company had been killed or wounded.
Thousand Yard Stare -
: While rooted in military history, the same blank gaze is seen in victims of violence, accidents, or any severe psychological trauma. Cultural and Historical Impact
: The stare continues to be portrayed in film and literature to represent a character's internal collapse or loss of innocence. Thousand Yard Stare
: The Marine in the painting had been in combat for 31 months, surviving tropical diseases and relentless fighting while most of his company had been killed or wounded. : While rooted in military history, the same
This could have to do with the pathing policy as well. The default SATP rule is likely going to be using MRU (most recently used) pathing policy for new devices, which only uses one of the available paths. Ideally they would be using Round Robin, which has an IOPs limit setting. That setting is 1000 by default I believe (would need to double check that), meaning that it sends 1000 IOPs down path 1, then 1000 IOPs down path 2, etc. That’s why the pathing policy could be at play.
To your question, having one path down is causing this logging to occur. Yes, it’s total possible if that path that went down is using MRU or RR with an IOPs limit of 1000, that when it goes down you’ll hit that 16 second HB timeout before nmp switches over to the next path.