Modify ↓
Ticket #222 (new defect)
Opened 8 years ago
Optimized collective updates require frozen objects
| Reported by: | hauma | Owned by: | hauma |
|---|---|---|---|
| Priority: | normal | Milestone: | 2.0 |
| Component: | uka.karo | Version: | 1.09b |
| Severity: | normal | Keywords: | |
| Cc: |
Description
The replicated root object is present at each rank of a replicated object. Since this could have been modified during a collective update, the underlying communication is always potentially all-to-all. To optimize collective updates effectively according to ticket:213, there must be the possibility to "freeze" at some point in time after construction. A frozen object must no longer be modified and is excluded from updates.
Attachments
Note: See
TracTickets for help on using
tickets.
