“git breaks when it tries to mirror” is not a convincing argument for moving to 
git. It might be an argument for fixing the mirroring in git.

wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/  (my blog)

On May 29, 2015, at 6:03 PM, Yonik Seeley <ysee...@gmail.com> wrote:

> +1 to move to git!
> 
> -Yonik
> 
> On Fri, May 29, 2015 at 5:07 PM, Anshum Gupta <ans...@anshumgupta.net> wrote:
>> I know this has come up a few times in the past but I wanted to bring this
>> up again.
>> 
>> The lucene-solr ASF git mirror has been behind by about a day. I was
>> speaking with the infra people and they say that the size of the repo needs
>> more and more ram. Forcing a sync causes a fork-bomb:
>> 
>> Can't fork: Cannot allocate memory at /usr/share/perl5/Git.pm line 1517.
>> 
>> They tried a few things but it's almost certain that it needs even more RAM,
>> which still is a band-aid as they'd soon need even more RAM. Also, adding
>> RAM involves downtime for git.a.o which needs to be planned. As a stop gap
>> arrangement attached a volume to the instance and are using it as swap to
>> work around the "adding RAM requires restart" issue.
>> 
>> FAQ: How would the memory requirement change if we moved to git instead of
>> mirroring?
>> Answer: svn -> git mirroring is a weird process and has quite the memory
>> leak. Using git directly is much cleaner.
>> 
>> I personally think git does make things easier to manage when you're working
>> on multiple overlapping things and so we should re-evaluate moving to it. I
>> would have been fine had the mirroring worked, as all I want is a way to be
>> able to work on multiple (local) branches without having to create and
>> maintain directories like: lucene-solr-trunk1, lucene-solr-trunk2, or
>> SOLR-XXXX, etc.
>> 
>> Opinions?
>> 
>> 
>> --
>> Anshum Gupta
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
> 

Reply via email to