Opened 10 years ago
Last modified 10 years ago
#151 new
Create sliver failure leaves behind state at AM
| Reported by: | ahelsing@bbn.com | Owned by: | somebody |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | AM | Version: | SPIRAL5 |
| Keywords: | Cc: | ||
| Dependencies: |
Description
I tried a createsliver that failed (code 2: Embedding workflow ERROR: 1:Insufficient resources or Unknown domain)
I fixed the problem and tried again. But I got an error: code 2: ERROR: duplicate slice urn urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+ahtestpgeni.
The AM should clean up after a failed createsliver, such that an intermediate deletesliver is not required
Change History (2)
comment:1 Changed 10 years ago by
comment:2 Changed 10 years ago by
| Priority: | major → minor |
|---|
Note: See
TracTickets for help on using
tickets.
As you know createSliver is a misnomer. It is really a slice. We flag slice as failed if any slivers fail in it, but the rest may have become active. Our current policy is to leave it to the user to decide what they want to do with a partially failed slice. If all slivers in a slice failed it will get garbage collected 'in the fullness of time' (GC is lazy).