-
Type: Bug
-
Status: Resolved
-
Priority: Critical
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 10.10
-
Component/s: Migration Service
-
Backlog priority:1,500
-
Sprint:nxcore 10.10.5
-
Story Points:1
Currently the migration service starts a pub/sub broker during its own start. This broker is used to invalidate migration state on a Nuxeo node inside a cluster.
Once the state is invalidated, migration service notify the corresponding migrator, which recomputes the service to use. As it, each nodes can change service from former one to a bridge service (during migration) to new one.
But these invalidations are not sent. We have to send them when:
- we probe the repositories
- migration is in progress
- migration has finished