sequential qerying active servers takes too long

Bug #275917 reported by pwrcycle
2
Affects Status Importance Assigned to Milestone
Eris
Confirmed
Low
Unassigned

Bug Description

This was reported on IRC:
########################
10:40 < Demitar:#ember>Does ember query servers sequentially? Or is that perhaps all wrapped up in eris? (I'm asking as it takes forever to get the
interesting servers up in the list, and I've noticed there's a whole host of unreachable servers out there.)
########################

I've had the same result and did some testing while talking to Al:

11:14 < pwrcycle:#cyphesis>here's the timestamps..
11:15 < pwrcycle:#cyphesis>entered "date" on the server to get a timestamp at the same time Ember queried the first server in the list "SECRET"
11:15 < pwrcycle:#cyphesis>Mon Sep 29 11:11:31 EDT 2008
11:15 < pwrcycle:#cyphesis>i tcpdumped on the 6767 port to watch the data go out to my Ember client:
11:15 < pwrcycle:#cyphesis>11:12:52.259335 IP 64.85.164.54.6767 >

11:16 < pwrcycle:#cyphesis>it was the Silicea server that takes a long time to reply..
11:17 < pwrcycle:#cyphesis>when it shows up, Amber, and llama11 return as active very fast.

########################

Revision history for this message
Erik Ogenvik (erik-ogenvik) wrote :

We need to look through how Eris queries the servers. I think that Al might know most about this piece of code, but this might also be a good opportunity for someone else to get more acquainted with that piece of code.

Changed in eris:
importance: Undecided → Low
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.