- **Comment**:
I have a several problems wiith this ticket.
First, the problem description is both incorrect and incomplete.
Point 7 is incorrect because the alternative and simplest way to clear the
issue is to
re-enable the PBE. It even says so in the pasted warning message in the ticket.
Second, the description is incomplete because it does not describe the
application
(point 3) in any detail. It justs says run "multiple" ccb operations.
The application types supported by IMM for CCBs are (a) operator initiated
configuration changes
and (b) operator initiatated management procedures (c) upgrade campaigns.
Now both (a) and (b) are defined as being limited in size and time.
Put in another way, if the configuration change is masssive, then it probably
should go
into a campaign. Or if the "configuration change" is some kind of high
troughput continous
... eeeeh test (?), then that is not a valid test in itsef.
The SAF imm serice is not designed to support high throughput applications.
If you nevertheless insist on using some kind of automated continous CCb
generting
application (which by definition is not using te´he imm for storing just config
data) then
at the very least any upgrade campaign needs to be made awqare of the
nonconformant
application so that the campaign can quiesce the deviant application before
starting
the upgrade propper. But of course the improper application should not be there
in he first place.
A proposed "fix" has been sent for review. But as I understand that fix, it
does not fix the
problem. It only reduces the likelyhood of it persisting. Its a timer based
solution.
So the fix is an "enhancement" type fix for a problem that lies outside the
scope of what the
SAF IMM service is intended to support. It then possibly an "enhancement".
But I would still argue that it is a "bad" enhancement since it dous not truly
remove the
problem and the invites missunderstanding/missuse of the imm service.
---
** [tickets:#2229] imm:disable pbe should honor critical ccbs**
**Status:** review
**Milestone:** 5.2.FC
**Created:** Wed Dec 14, 2016 09:29 AM UTC by Neelakanta Reddy
**Last Updated:** Wed Dec 14, 2016 09:47 AM UTC
**Owner:** Neelakanta Reddy
reproducible steps:
1. Bring up the cluster with PBE configured.
2. enable PBE
3. parallely run multiple ccb operations
4. disable PBE
5. in one of the payload/controller restart the immnd/node
6. sync wil be aboreted with following messages
WA PBE has been disabled with ccbs in critical state - To resolve: Enable PBE
or resart/reload the cluster
NO Still waiting for existing Ccbs to terminate after 20.027520 seconds.
Aborting this sync attempt
7. The IMMND will never get synced untill cluster restart
The problem is observed, when the node is not joining in middleware upgrade,
and evetually upgrade fails.
---
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
