Ticket #330 (assigned defect)
Report MDS_DOWN if no service exists
| Reported by: | bertil.engelholm@… | Owned by: | bertil.engelholm@… |
|---|---|---|---|
| Priority: | major | Milestone: | PL 3.0.1 |
| Component: | MDS | Version: | 3.0.0-FC |
| Keywords: | Cc: | ||
| patch waiting for maintainer: | no |
Description
If an m+n adest is withdrawn and there are no other adest available for the service MDS_DOWN is sent first after AWAIT_ACTIVE_TMR expires. If a new adest is published within AWAIT_ACTIVE_TIME it means that the user will not be informed that there has been no service available at all for a moment.
In AVD-AvND communication this means that if a new controller comes up within AWAIT_ACTIVE_TIME AvND is not informed that it has lost contact with both AVD for a while. This implies that the payload node will never enter the cluster again until someone reboots it manually. If MDS_DOWN is sent by MDS to AvND as soon as there are no AVD service available it'll reboot the payload node.
I'm working on a patch solving this.
Attachments
Change History
Note: See
TracTickets for help on using
tickets.
