[tahoe-lafs-trac-stream] [tahoe-lafs] #2062: what happens if a "tahoe backup" process is in progress when another one is started?

[tahoe-lafs]

#2062: what happens if a "tahoe backup" process is in progress when another one is
started?
----------------------------+---------------------------
 Reporter:  zooko           |          Owner:
     Type:  defect          |         Status:  new
 Priority:  normal          |      Milestone:  undecided
Component:  code-nodeadmin  |        Version:  1.10.0
 Keywords:  tahoe-backup    |  Launchpad Bug:
----------------------------+---------------------------
 How does the "tahoe backup" process handle the situation that another
 "tahoe backup" process is running at the same time, accessing the same
 backupdb?

 To answer this question, start here:
 [source:trunk/docs/backupdb.rst?rev=83f97dcf7dc968ee8442bf5caf011a70a8971b90
 docs/backupdb.rst] and
 [source:trunk/src/allmydata/scripts/backupdb.py?annotate=blame&rev=a1a1b5bf8a6e1a09c70d4d2b618ad0c06b0f631f
 src/allmydata/scripts/backupdb.py].

 This is relevant to #2053, because a simple, easy improvement for #2053 is
 just to make sure that backup processes don't corrupt each other's state
 if they run concurrently, and that they make good quick progress, and take
 advantage of one another's (complete, consistent) results for faster
 progress.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2062>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage