Clojurians Log v2

Anyone else seen this error trying to deploy a new release: Could not transfer metadata my-tmpl:lein-template/maven-metadata.xml from/to releases (<https://clojars.org/repo/>): Read timed out? Tried 2 different releases and gotten this error both times. status says clojars is 100% up.

@cap10morgan: yes, that's been reported, but we have no idea of the cause right now https://github.com/clojars/clojars-web/issues/546

did the deploy seem to take a while, or did the timeout occur immediately?

ah, OK. pretty quickly.

was the timeout on maven-metadata.xml both times?

yes

hmm

we are using maven-medata.xml as a trigger to validate the deploy, copy it from a tmp repo to the live repo (part of the atomic deploy feature), and, just recently, to copy the project to Rackspace cloudfiles in anticipation of serving the repo from a CDN

it's possible that that is all taking too long

depending on the default timeout in aether

@cap10morgan: I saw that error, but the release seemed to deploy successfully anyway.

in the reported cases, the deploy actually succeeded, yeah

@tcrawley: the error seemed to occur within a few seconds

OK, that’s good at least 🙂

@daveliepmann: was your error with maven-metadata.xml as well?

Yes: Could not transfer metadata uruk:uruk/maven-metadata.xml from/to clojars (https://clojars.org/repo/): Read timed out Failed to deploy metadata: Could not transfer metadata uruk:uruk/maven-metadata.xml from/to clojars (https://clojars.org/repo/): Read timed out

good to know, thanks

@tcrawley: want me to do another one w/ some debugging output turned on?

I suspect we may need to move uploading to cloudfiles to a queue that gets processed async

@cap10morgan: let me add some timing output to the server side, give me a few minutes

OK, sounds good

how big is the jar for the project you are deploying?

22K

26K

those are pretty small, I was thinking it was large uploads to cloudfiles causing the issue

@cap10morgan: @daveliepmann: I added some profiling to the validation and upload-to-cloudfiles code, and deployed a small test app

It didn't fail, but did take almost 8 seconds to validate + upload

950ms just to upload the 12k jar

to cloudfiles

so, if the timeout is 10s, we could very easily hit it

yeah, it looks like 10s may be the default - I just recreated the issue by increasing the jar size to 23k

the validate+upload took 9800ms, and it's safe to assume we're spending another 200ms outside of that process to get us over 10s

I'm going to disable the cloudfiles upload for now, since we're not yet using the artifacts uploaded there

@cap10morgan: @daveliepmann: the cloudfiles uploads are now disabled in production. I just deployed my testapp, and the deploy time went from ~10s to 200ms. Please let me know if you continue to see the problem

@tcrawley: cool, will do. thanks!