Hi, I'm not in the bouncer development. But it's true that the bouncer is in the end the bottleneck for our distribution. In that case I'm wondering if there is no "redundant" DNS entrys. I assume all hits going trough 1 server. If this server is overloaded or down, the downloads are not available. I would suggest to have here a redundant system.
Andrea Pescetti schrieb: > Florian Effenberger ha scritto: > >>> Bouncer has been unresponsive for about one hour. >>> >> thanks for reporting! Should be working again now. >> > > It was, indeed. But, unfortunately, it has been now unresponsive (or > very slow: downloads need 5 minutes or so to be served) for a couple of > hours, again! Our description reminds me of a problem I had on one of my server after serving a big patch file to the public. The file did not load and there was no connection timeout. After a long time the file did load. The reason was simply my server did hit its set connection/transfer limit. There where no more available instances that where allowed to serve files. In the case of a bouncer I think on the option "keep alive" because a normal request is handled in less than a second. The option keep-alive will let the connection stay open as long it is configured in the server config. To increase the performance of the bouncer this option should be switched of. Well due the connection problem I could not check if keep-alive is on or off. greetings Florian Bircher
