www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-3122) a certain block of facebook.com machines is unable to access svn.apache.org
Date Thu, 28 Oct 2010 06:06:05 GMT

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

Gavin commented on INFRA-3122:

Hi John, 

Yes they are blackliste for being heavy abusers and causing unusual and sustained loads on
This is not good for the machines, not good for other users etc..

We have dump files at http://svn.apache.org/dump/ 

How about you start using a local copy of svn by downloading the latest dump file and then
rsycning the remainder to keep upto date.

Would that be acceptable?

> a certain block of facebook.com machines is unable to access svn.apache.org
> ---------------------------------------------------------------------------
>                 Key: INFRA-3122
>                 URL: https://issues.apache.org/jira/browse/INFRA-3122
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Subversion
>            Reporter: John Sichi
> Yesterday morning, Hive and Hadoop developers at Facebook started experiencing failures
attempting to run svn to svn.apache.org from certain machines.  Other machines within facebook.com
are not having the problem.  Facebook network engineers are investigating the problem but
so far have not been able to locate a cause of the problem within Facebook's own network.
 The affected machines happen to be development machines which happen to make heavy use of
svn.apache.org, so we would like to know whether there's a possibility that the affected machines
somehow got blacklisted by the svn servers (e.g. via some automatic defense against denial
of service attacks).
> The affected block of machines NAT's to the following IP address range.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message