[tahoe-dev] [tahoe-lafs] #651: handle MemoryError by failing quickly and loudly

[tahoe-lafs]

#651: handle MemoryError by failing quickly and loudly
--------------------------+-------------------------------------------------
 Reporter:  zooko         |           Owner:           
     Type:  defect        |          Status:  new      
 Priority:  major         |       Milestone:  undecided
Component:  code-mutable  |         Version:  1.3.0    
 Keywords:                |   Launchpad_bug:           
--------------------------+-------------------------------------------------

Comment(by zooko):

 People are reporting !UncoordinatedWriteErrors on the test grid (#748),
 and so I checked some of the test grid storage servers and saw that one --
 tahoebs5.allmydata.com bs5c1 -- has 1.5 GB of virt, 475 MB res.  That is
 running some very old versions of foolscap and TahoeLAFS:

 {{{
 allmydata-tahoe: 1.3.0-r3747, foolscap: 0.3.2, pycryptopp: 0.5.2-1, zfec:
 1.4.0-4, Twisted: 2.5.0, Nevow: 0.9.26, zope.interface: 3.3.1, python:
 2.5.2, platform: Linux-Ubuntu_8.04-i686-32bit, simplejson: 1.7.3,
 argparse: 0.8.0, pyOpenSSL: 0.6, pyutil: 1.3.16-12, setuptools: 0.6c8
 }}}

 Hm...  Yep, that one has !MemoryError in its twisted.log.  I wonder if we
 could monkeypatch Python's !MemoryError class to do a {{{sys.exit()}}} or
 the like.  I suppose this also suggests that we ought to be pushing this
 issue upstream to Python itself...

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/651#comment:6>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid