You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Zimfarm worker does not manage at all the outgoing traffic, meaning it uses whatever default route is configured in the OS.
When a worker has multiple public IP, we would benefit from taking advantage of that by spreading the task on the various public IPs available (which would be exposed as various adapters at the host level).
Not sure how much effort it would necessitate, and I think that we've just encountered the first worker which make take benefit from this new functionality, might well be an edge case.
The text was updated successfully, but these errors were encountered:
I don't think they are causing any issues, we are just defaulting to one of them in fact. Which is a bit of a pity since having multiple might help to run multiple tasks in // from multiple IPs
Currently, Zimfarm worker does not manage at all the outgoing traffic, meaning it uses whatever default route is configured in the OS.
When a worker has multiple public IP, we would benefit from taking advantage of that by spreading the task on the various public IPs available (which would be exposed as various adapters at the host level).
Not sure how much effort it would necessitate, and I think that we've just encountered the first worker which make take benefit from this new functionality, might well be an edge case.
The text was updated successfully, but these errors were encountered: