|Re: [cross-project-issues-dev] What's up with download.eclipse.org?|
On 09/29/2009 05:31 PM, Denis Roy wrote:
I'm not an expert in how to prioritize what's mirrored. But with prior knowledge about how p2 meta-data is named and used, perhaps a simple pattern could be applied on all mirrored material?p2 metadata seems to be scattered across our directory tree, making it difficult to strategically redirect content. It's also easy to draw up a plan 5 days after the release. I mean, would you have expected /tools/mylyn/update/e3.4/content.jar to be a top-3 downloaded file?
**/content.*,**/artifacts.*,**/compositeContent.*,**/compositeArtifacts.* would go a long way.
They are all small files so hitting some that aren't really on the top list doesn't matter much.
I know this is frustrating. I've spent the last five years trying to make these releases as painless as possible, but as long as our servers and your code keep evolving, there are always going to be some unexpected results.I know you do a great job with the infrastructure and that sometimes shit happens that just can't be anticipated. It's just that over the years that I've been working with Eclipse, the servers are always more or less swamped just after a release has been made. Perhaps this time, it was caused by a combination of things but I've always had the feeling that we don't really distribute and test things before people start downloading. If that's an incorrect assumption, great.
One thing that would improve the situation a bit on the unforeseen problems front could be if we had someone in our timezone that could react (turn off malfunctioning redirects etc.) on blocking bugzillas. Even if you fix things ASAP, a whole day has passed for us in Europe when things like this happens. I'm probably stating the obvious again.
Regards, Thomas Hallgren
Back to the top