Bug #611: [rsyncd] Reenable, properly limit bandwidth - Servers - Parabola Issue Tracker

Bug #611

[rsyncd] Reenable, properly limit bandwidth

mtjm - over 9 years ago - . Updated about 7 years ago.

Status:

fixed

Priority:

critical

Assignee:

% Done:

100%

Description

Mirrors use too much bandwidth when they synchronize packages with repo, so there are huge latencies at ssh and other services. Per-connection bandwidth limiting is not useful when a single mirror uses several connections at once.

Find a proper solution (use iptables? have rsync access from only one primary mirror?), implement it and start rsyncd.socket at repo.

Related issues

History

Updated by alfplayer over 9 years ago

mtjm | re-enabled rsyncd, now at --bwlimit=128 until someone finds a better solution

128 KB/s seems too low. I would limit the web access if it helps increase that number (HTTP mirrors can be used anyway) because the web interface is not essential in my opinion. Maybe this works: http://nginx.org/en/docs/http/ngx_http_core_module.html#limit_rate

Updated by mtjm over 9 years ago

128 KB/s seems too low.

768 KiB/s is too high: there were several connections used at once. We cannot limit total bandwidth usage in per-connection rsyncd settings.

I would limit the web access if it helps increase that number (HTTP mirrors can be used anyway) because the web interface is not essential in my opinion.

It's already less than used by rsync.

We need some automated per-port statistics, all that I wrote here is based on several runs of iftop.