Ticket #46 (new defect)
Opened 19 months ago
Online migration
| Reported by: | ieslick | Owned by: | ieslick |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | system-wide | Version: | |
| Keywords: | Cc: |
Description
Can we enable online migration as a kind of GC? We're a long way there.
Enablers:
- Migrate already updates moved instances to point to new store controller
- New objects will be created in the new store controller by default, if *store-controller* is updated in each thread
Needed:
- We need to make sure that references to btrees, slots, etc check for access against a 'migrating' store so they don't complete until the object in question has itself been migrated.
- Does access to an 'old' instance migrate it, poll-wait, etc?
Perhaps a full online GC solution will pre-empt this.
Note: See
TracTickets for help on using
tickets.
