- **status**: review --> fixed
- **assigned_to**: Vu Minh Nguyen --> nobody
- **Comment**:
commit 18f6ab6e2f48d5f3fb51dc51ed1e611b64b98708 (HEAD, origin/develop,
ticket-2749, develop)
Author: Vu Minh Nguyen <[email protected]>
Date: Wed Dec 27 17:21:36 2017 +0700
imm: fix immnd restarted during SYNC finalize [#2749]
The call to saImmOiImplementerSet and saImmOiImplementerClear are allowed
during
sync. Therefore, there is possibility the messages of these calls arrived
at
the sync-client after finalizeSync was sent from IMMND coord but before
finalizeSync arrived at sync-client (over fevs).
In that case, the implementer record stored in sImplementerVector database
will
then be different with the implementer record in finalizeSync and this
mismatch
caused the IMMND sync-client restart with current implementation.
This ticket adds a check to ignore that implementer record in finalizeSync
as it is obsolete instead of terminating the sync-client.
commit 5b575478f7273b06555ed69fd7f27af983c0819b (HEAD, origin/release, release)
Author: Vu Minh Nguyen <[email protected]>
Date: Wed Dec 27 17:21:36 2017 +0700
imm: fix immnd restarted during SYNC finalize [#2749]
The call to saImmOiImplementerSet and saImmOiImplementerClear are allowed
during
sync. Therefore, there is possibility the messages of these calls arrived
at
the sync-client after finalizeSync was sent from IMMND coord but before
finalizeSync arrived at sync-client (over fevs).
In that case, the implementer record stored in sImplementerVector database
will
then be different with the implementer record in finalizeSync and this
mismatch
caused the IMMND sync-client restart with current implementation.
This ticket adds a check to ignore that implementer record in finalizeSync
as it is obsolete instead of terminating the sync-client.
---
** [tickets:#2749] imm: immnd restarted during SYNC finalize**
**Status:** fixed
**Milestone:** 5.18.01
**Created:** Wed Dec 27, 2017 09:29 AM UTC by Vu Minh Nguyen
**Last Updated:** Wed Dec 27, 2017 10:36 AM UTC
**Owner:** nobody
The call to `saImmOiImplementerSet` and `saImmOiImplementerClear` are allowed
during sync.
Therefore, there is possibility the messages of these calls arrived at the
sync-client after `finalizeSync` was sent from IMMND coord but before
`finalizeSync` arrived at sync-client (over fevs).
In that case, the implementer record stored in `sImplementerVector` database
will then be different with the implementer record in `finalizeSync` and this
mismatch caused the IMMND sync-client restart with current implementation.
This ticket will add a check to ignore that implementer record in
`finalizeSync` as it is obsolete instead of terminating the sync-client.
To reproduce this issue, continuously call implementer set and clear on SC
while performing PL node(s) reboot.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
