HttpStreamingConfigListener throwing > 900 exceptions per second

Hi, I’m a colleague of Julien

I’ve analysed the code, this is what I understood and discovered

once connected, ConfigHandler polls config from the server

if during polling it catches a DocumentNotFoundException, it starts all HttpStreamingConfigListener

this listner continuously calls on cluster nodes, in a background task, the url http://nodeaddress/pools/default/bs/CLUSTER

this request always throws a 404

So the root question is : why dos it get a DocumentNotFoundException
is it a false positive because of network error?
is it expected?

BTW, I found a bug in HttpStreamingConfigListener
It gets a random node with var nodes = _configSubscriber?.ClusterNodes.ToList().Shuffle();
but if the node has no management uri, it throws a null reference exception