Menu
▾
▴
[Statsvn-developers] [ statsvn-Bugs-2811325 ] runs without end
|
From: SourceForge.net <no...@so...> - 2010-03-09 07:51:58
|
Bugs item #2811325, was opened at 2009-06-24 06:29 Message generated for change (Comment added) made by i5513 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=833326&aid=2811325&group_id=164845 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Works For Me Priority: 5 Private: No Submitted By: Bert Lange (bartfax) Assigned to: Nobody/Anonymous (nobody) Summary: runs without end Initial Comment: I want to try statsvn on our repository on an 8-core machine. It seem's to run endlessly Here is my command-line: java -jar ~/path_to_statsvn/statsvn.jar -threads 7 svn.log . -output-dir ~/output/ Now after 24h runtime I see 7 processes using my CPU link this: svn diff -c 28073 http://repository/trunk/ --non-interactive The last (unchanged since 12 hours) output on the console is this: svn diff 498/2107 on r37404 (1237 ms.) pool-1-thread-6 What can I do? ---------------------------------------------------------------------- Comment By: Javier Barroso (i5513) Date: 2010-03-09 07:51 Message: Hi, Could be possible to add an timeout parameter to svn operations ? So if an svn diff takes more than 30 ? minutes statsvn skip to next step or similar ? I have many svn repo, and there are some which "hangs". Thanks ! ---------------------------------------------------------------------- Comment By: Jason Kealey (jkealey) Date: 2009-07-01 14:54 Message: Indeed. The issue here appears to be related to a HUGE commit (5.7 million lines of diff). The good thing is that once it is cached, it should run faster. However, with this size of a commit, I am not sure if the issue is with the server (slow to process) or if the sheer size of the commit makes it unmanageable. I will mark this bug as "Works for me" as it is related to the SVN call. However, please feel free to let us know if you do manage to process it. ---------------------------------------------------------------------- Comment By: Bert Lange (bartfax) Date: 2009-07-01 07:12 Message: Ok. Some news: @jkealey: 1) It did "-threads 1". It was a typo in the comment, not on commandline. 2) Out svn-server allow only http connections. No https, no svn, no svn+ssh. And I'am not the svn-admin. 3) A manually run show following: $ time svn diff -c 28073 http://repository/trunk/ --non-interactive > svnoutput real 796m49.422s user 786m4.162s sys 0m21.980s $ wc -l svnoutput 5712184 svnoutput It runs around 13 hours with 100% CPU. So it seems everything is working alright, but not in worthwhile times. So I will try to limit the date range. Maybe I can talk with our admin to get an svn dump an try the "local svn repository" variant. Thank you all for your response. ---------------------------------------------------------------------- Comment By: Jason Kealey (jkealey) Date: 2009-06-30 13:04 Message: @benoitx svn diff 498/2107 - my guess is that the estimate looks at progress done and infers time left - because it froze for hours, the estimate is way off. ---------------------------------------------------------------------- Comment By: Benoit Xhenseval (benoitx) Date: 2009-06-29 13:24 Message: Errr... I do not want to jump in here but have you noticed the estimate for completion? Sat Jun 27 04:16:07 CEST 2009 Intermediary save took 472 ms. Estimated completion=Mon Mar 01 05:01:24 CET 2010 March 1, 2010! How many svn diff is it doing? How long each request is taking? ... I wonder if some networking issues are not properly reported back to StatSVN and therefore just "hang"... wondering if this issue would happen with SVNKit rather than command lines. ---------------------------------------------------------------------- Comment By: Jason Kealey (jkealey) Date: 2009-06-29 12:10 Message: 1) Did you do "-threads 1" or (incorrectly) "-treads 1"? 2) You are connecting to the server via HTTP. Can you change that to SVN? 3) What happens if you manually run svn diff -c 28073 http://repository/trunk/ --non-interactive via the command line? (or another command that you saw frozen). (try this when it is normal and right after it freezes) ---------------------------------------------------------------------- Comment By: Bert Lange (bartfax) Date: 2009-06-29 11:28 Message: Ok. I run in now with "-treads 1". This is my last output: Sat Jun 27 04:16:07 CEST 2009 Intermediary save took 472 ms. Estimated completion=Mon Mar 01 05:01:24 CET 2010 The svn server is internal. There is no firewall or DoS problem. All others users can work with svn without problems. Only my process takes 100% CPU and didn't stop even if I interrupt statsvn. $svn --version svn, version 1.5.5 (r34862) compiled Dec 22 2008, 12:59:38 Any other hint's? ---------------------------------------------------------------------- Comment By: Jason Kealey (jkealey) Date: 2009-06-24 14:49 Message: As per this thread: http://sourceforge.net/forum/message.php?msg_id=7449240 I would reduce the number of threads to 1 and see what is happening... Why is your SVN server not responding quickly? Is it an internal server? Are you sure that the firewall is not blocking you? You could have generated a lot of queries and been flagged as a DoS. Run with -threads 1 as per the user manual http://wiki.statsvn.org/Default.aspx?Page=User%20Manual&AspxAutoDetectCookieSupport=1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=833326&aid=2811325&group_id=164845 |