UI unresponsive when some nodes are down

Steps.

1. Send SIGSTOP to one of the ns_server-s (PID=$(curl -s -X POST -u Administrator:asdasd http://127.0.0.1:9003/diag/eval -d 'list_to_integer(os:getpid()).'); kill -SIGSTOP $PID)
2. Go to "Servers" in the UI
3. Try to click on any of the nodes.
4. You'll get a spinner that'll continue spinning for a long time (most likely until the stopped node is determined to be down by erlang).

Around the same time I see requests to /pools/default/stats/range taking 60 seconds. So I'm suspecting those are the cause of the unresponsiveness.