[JIRA] [subversion] (JENKINS-13835) E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request

Thu, 04 Jul 2013 05:24:55 -0700

pancake commented on Bug JENKINS-13835

Greg, the problem is indeed on the Jenkins side. Not necessarily on Jenkins server itself. Basically speaking this glitch occurs when svn client (Jenkins server or slave) stops communicating to svn server for unexpectedly long time (>KeepAlive). In our Jenkins deployment we saw that svn checkout on slave consumed 100% of one CPU core, i.e. checkout speed was limited by per-core performance of Jenkins node. So, to workaround the alleviate the situation you can:

  • See if CPU/disk performance is a bottleneck for svn checkout and upgrade the hardware of relevant Jenkins node.
  • Tune Jenkins GC options. We didn't check, but it's very likely that delays are due to GC.
  • Increase KeepAlive on svn server. You'll probably want to setup a dedicated svn mirror for Jenkins and set KeepAlive on that mirror only. That's not good to have insanely big KeepAlive on a publicly available servers.

Note that we're using 1.6 WC format on Jenkins ("Manage Jenkins" -> "Configure System" -> "Subversion"). I don't quite remember what exactly bug made us downgrade 1.7 -> 1.6 and not even sure if it's still there. But you can try it if the above doesn't help.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to