Internally, a target is identified by its NAME, so
When a target is removed and added quickly via loader, the dialer that started early sees the old listener that is dying slowly as an active listener(as the listener is identified by NAME), causing the new listener to not start. But in a while, the old listener closes, ultimately causing the absence of a listener for the client; hence, metric collection comes to a halt for that target,
And we have no way to detect this since target_up metirc is showing value as 1, eventullay tcp conneciton for this target is getting torn up due to keep alive, but gnmic is stuck waiting for the listener to read the message from the subscribe response channel
Internally, a target is identified by its NAME, so
When a target is removed and added quickly via loader, the dialer that started early sees the old listener that is dying slowly as an active listener(as the listener is identified by NAME), causing the new listener to not start. But in a while, the old listener closes, ultimately causing the absence of a listener for the client; hence, metric collection comes to a halt for that target,
And we have no way to detect this since target_up metirc is showing value as 1, eventullay tcp conneciton for this target is getting torn up due to keep alive, but gnmic is stuck waiting for the listener to read the message from the subscribe response channel