Both VWS Nodes Processing Bucket Expiry
(Doc ID 2785241.1)
Last updated on SEPTEMBER 23, 2022
Applies to:Oracle Communications Network Charging and Control - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On Oracle Communications Network Charging and Control Applications (NCC), 22.214.171.124.0 version,
Consider the scenario:
- Long held data session running on Voucher and Wallet Server (VWS) due to switchover (planned or unplanned)
- Primary running (and grovelling)
- The expiry plugin fires due to the groveller, and also due to charging events. So essentially any situation when a call or session is on the secondary there's a window for an
expiry to fire on both nodes.
- a renewal for a Periodic Charge (PC) fired at the same moment on both VWS nodes.
So one was driven by traffic, and one was driven by background processing (i.e. the groveller). Is this a fundamental design flaw? Is there a configuration based solution for this?
- The beServer will not accept connections until the sync is complete and the beVWARS are up to date.
- The beGroveller will not start grovelling accounts unless the VWS is "running" and beServer is accepting connections
They see a race condition between the primary and the secondary - both nodes have the opportunity to process the expiry. Between one node processing, writing the sync file and the other node being made aware it too could process the expiry. Disabling the groveller on the primary is not a good solution as there could be ongoing sessions on the secondary for a long time. So it can't be left disabled.
Once the primary VWS is active and starts serving the request it will get the future Subsequent Requests(SR/CCRs .This doesn't match how it works in a practical test. If one restart the primary VWS during a long duration call, the call completes on the Secondary VWS. What is the expected functionality and how it is meant to work. It seems BeClient will not prefer the primary automatically for SRs - it will "stick" to the same route unless that route becomes unavailable.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document