There is also a dumb thing with Collection Sever. The CS seems to be assigned at the same time with WS at the beginning of the WU folding. And if the CS is down by the time the WU is finished (besides the WS being down like today) FAHClient will just endlessly loop on the assigned CS.Aurum wrote:We recommended that about 6 months ago along with other things and still no 7.4.17.ifolder wrote:An even better option would be to implement in the next FAHClient version the fact that when the WS did not assign a WU, FAHClient gives this information, alongside with the IP of the faulty WS, on its next WS request so that a different WS should be assigned. And several requests like this should raise an alarm about the faulty WS.ifolder wrote:Hi,
FAHClient connects to 171.67.108.45 that keeps on assigning the same work server 171.67.108.105 which doesn't assign any work unit.
Shouldn't 171.67.108.45 detect that same client or IP is asking again for WS and assign another work server instead of dumbly assigning the same one again and again and again??
So besides having FAHClient telling the AS that a WS assignment failed with the server having IP x.x.x.x (so that the AS immediately assigns another WS, as suggested above), FAHClient should request the CS from the AS when the WU is finished (if the WS is down). And of course if the assigned CS is down FAHCLient should also tell the AS that CS with IP x.x.x.x is down so that the AS assigns another CS.
And, finally as I suggested in another topic, Credit computation shouldn't take into account the Upload time because there is no reason folders who invested a lot of money in high-end GPUs be penalized by server-side problems or lack of performance.