Database Notification System for Data Storage State Changes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional state change indication systems in data storage systems are inefficient and prone to losing notifications upon restart, as they rely on RAM for queuing notifications, and require excessive CPU cycles due to multiple software layers subscribing to change indications from the same component.

Innovation Solution

Implementing a system where asynchronous notifications of state changes are delivered by querying a database with sequentially generated identifier values, ensuring persistent storage and reducing CPU cycles by allowing direct access to subscribed notifications within the database.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If notifications are queued in RAM for delivery through software layers, then notifications can be delivered in desired order, but notifications are lost upon computer restart

Engineering Contradiction:
Improvenotification delivery guaranteeVSAvoidnotification loss
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent applies preliminary action by persistently storing notification data in a database before it is needed for delivery. The notification information is written to persistent storage in advance, ensuring it survives system restarts. This resolves the contradiction by preparing the notification data in a safe location beforehand, preventing loss while maintaining delivery capability.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If multiple software layers subscribe to change indications from the same component, then each layer can access needed notifications, but excessive CPU cycles are required for propagation

Engineering Contradiction:
Improvelayer subscription flexibilityVSAvoidCPU cycle consumption
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent applies copying by creating a single centralized copy of notification data in the database that all software layers can access. Instead of propagating notifications through multiple layers (which consumes CPU cycles), each layer independently queries and copies the needed notification data directly from the persistent storage. This eliminates the expensive propagation process while maintaining the ability of multiple layers to subscribe to and access change indications.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9754004B2Asynchronous notification method for data storage systems
Publication Date: 2017.09.05 EMC IP HLDG CO LLC
  • US9754004B2 patent drawing
  • US9754004B2 patent drawing
  • US9754004B2 patent drawing

AI summary

An improved technique involves delivering asynchronous notifications of state changes of components of a data storage system by querying a database whose entries contain event descriptors along with a sequentially generated identifier value. In response to a state change of a component, a database server receives a state change indication and updates an entry in the database by recording the state change and generating a new identifier value. A management server running management software then detects state changes by noting the largest generated identifier value from a previous query and queries all entries in the database having an identifier value larger than that previous value. The layers of the management software that subscribe to state change indications of various components may then access those entries as needed.