www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henk Penning (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-9470) rsync.{us,eu}.apache.org
Date Thu, 23 Apr 2015 11:56:38 GMT

    [ https://issues.apache.org/jira/browse/INFRA-9470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14508915#comment-14508915

Henk Penning commented on INFRA-9470:


I think going with the OS/distro default setup is best.

With '--no-detach' the daemon-parent-process can (in principle) manage the forked service-processes
; the parent process would need a service port that the sysop can send command to ; like "kill
every service process", or "kill service processes old then
some limit". It appears "daemon management" is going that way.

It would be nice to puppetize 'rsyncwho' (and ggrep, perhaps as rsyncgrep), so it is available
on the apache rsync servers.

I don't know if it is necessary to cron rsync-cleanup, as you suggest. I've never seen
rsync become such a mess before. So perhaps it is better to watch and fix a problem, if there
is one.

The 'archive setup' worries me ; we have multiple archives that are not in sync.
Because we have multiple '/dist/'s that are not in sync.

For the rsync setup, I would prefer 1 master tree, where the production rsync servers get
there stuff from ; rsyncing /dist takes very little time, so syncing frequently is no prob.
And, if the master is temporarily not available, that is no prob (for the mirrors).

Also, I would prefer to exclude /dist/*/.revision for rsyncd.conf [apache-dist] and [apache-dist-most].
Nobody uses it an it clutters the rsync reports I get from /my/ mirror ; I always look if
the mirror updates make sense ; useful info disappears in the long list of .revision updates.



> rsync.{us,eu}.apache.org
> ------------------------
>                 Key: INFRA-9470
>                 URL: https://issues.apache.org/jira/browse/INFRA-9470
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Other/Misc
>            Reporter: Henk Penning
>            Assignee: Geoffrey Corey
> Today (april 18 2015) rsync.us.apache.org was a mess ; #connections maxed out (80) ;
many connections were over a week old ; with 8 connections from tlp-eu-mid.apache.org ; module
[apache-dist-for-archive] ; syncing crud like openoffice/.svn/pristine/ab/ab1d402ad75da398da90df175c4d018977e46ff7.svn-base
> rsyncd.conf on rsync.us.apache.org needs a freshup.
> -- [apache-dist-for-archive] needs a limited 'hosts allow', 'hosts deny  = *'
> -- IMHO TLP/.svn shouldn't be in the archive ; it's not (visible) in
>   http://www.apache.org/dist and it is a lot.
> -- rsync.us.apache.org shouldn't use --no-detach
> Which module(s) are actually used for archive.apache.org ?
> Rsync.us has [apache-dist-for-archive] ;
> Rsync.eu has [apache-dist-for-archive] and [archive-site]

This message was sent by Atlassian JIRA

View raw message