[kepler-dev] [Bug 5378] New: add rety logic to SpanTodt, attempt to recover if RBNB goes down

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5378

           Summary: add rety logic to SpanTodt, attempt to recover if RBNB
                    goes down
           Product: Kepler
           Version: 2.1.0
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: sensor-view
        AssignedTo: barseghian at nceas.ucsb.edu
        ReportedBy: barseghian at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org
   Estimated Hours: 0.0


We've found that requesting a large amount of data from RBNB on a gumstix, at
least via rdv (1.9.0 and 2.2.1), can get the server into a messed up state,
requiring a restart, and the RBNB files written to disk will become corrupt
such that a restart of rbnb fails to load the old data (yikes - we'll work on a
replication procedure and submit these bug(s) to the rbnb list). When this
happen SpanTodt locks up. Even when rbnb is successfully restarted (e.g. by
deleting rbnb files on disk and starting fresh), SpanTodt stays locked. We
should add some retry logic so spanToDT can attempt to persevere through tough
times.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.