In the original report, the Infrastructure team said that throwing memory at it did not solve the problem. And I believe they threw *a lot* of memory at it.
There may well be other options - just needs someone to dive in and look! Upayavira On Fri, Dec 4, 2015, at 11:10 PM, Alexandre Rafalovitch wrote: > Maybe a silly question, but has anybody actually looked into the > git-svn itself. E.g. talking to git-svn team with our example to help > them troubleshoot the link. Or run a test sync under profiler. > Also, it is running into OOM, but how big is a system doing the sync. > If the issue is upgrading the server from 8gb of memory to 16gb, this > might be an easier/cheaper course that moving the whole infrastructure > around. I am sure Lucidworks or Elastic could probably sponsor a > couple hundred bucks for memory upgrade if that turned out to be the > real problem. :-) > > Reading JIRA, I get a feeling that this problem with git-svn is mostly > treated as a blackbox. It feels like there might be other options. > > Regards, > Alex. > > On 4 December 2015 at 15:57, Michael McCandless > <luc...@mikemccandless.com> wrote: > > The infra team has notified us (Lucene/Solr) that in 26 days our > > git-svn mirror will be turned off, because running it consumes too > > many system resources, affecting other projects, apparently because of > > a memory leak in git-svn. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
