Enhancement To Persist Rated Event Data When Nosql Process Is Down (Doc ID 2238825.1)

Last updated on APRIL 30, 2017

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 11.3.0.0.0 and later
Information in this document applies to any platform.

Goal

On :  ECE 11.3.0.1.0 version, Rated request persistence layer

ACTUAL BEHAVIOR  
-----------------------
Even though the Rated Event data is not published successfully to Nosql (say Nosql storage node is down), the data is getting removed from Rated Event cache after the expiry delay(eventually a data loss).


EXPECTED BEHAVIOR
-----------------------
Rated event data should not  get removed from Rated Event cache until it is successfully written-out to Nosql.  Can this be treated as an enhancement request in the product and addressed going forward.

STEPS
-----------------------
0.  Ensure below configuration is set (same as in OOB)  in charging-setting.xml:

          <cache-name>RatedEvent</cache-name>
          <scheme-name>default-federated-expiry</scheme-name>
          <init-params>
              <init-param>
                  <param-name>expiry-delay</param-name>
                  <param-value>5m</param-value>  --------------------> this is 5 minutes, after which RatedEvent cache expires
              </init-param>


1. Whole system is up & running (BRM/ECE/NoSQL)
2. Shut down all NoSQL nodes
3. Generate an usage
4. The usage remains in Rated Event (RE) cache as all NoSQL nodes are down.
5. After expiration time of RE cache, the rated event is removed from the cache, i.e., system does not wait for successful flush to NoSQL before purging the RE from the cache  and this is resulting data loss

Note: It might be a  basic assumption behind this logic that NoSQL should be 'always running' but in reality, such ideal situation may be disturbed (e.g. during failover from Primary to Secondary site). So the expectation is that Rated Events are removed from the cache only after successful flush to NoSQL.

6.  Consider that after step 4, the NoSQL node is brought up
7.  Now it is expected that Rated Event Formatter (REF) picks up the rated event from cache and pushes it to NoSQL but this does not happen, meaning that REF does not have a retry mechanism.

BUSINESS IMPACT
-----------------------
Leads to data loss

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms