Distributed Data Store Location Updates via Version Indicators

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data store technologies lack effective tools for managing distributed data store location updates, leading to inefficiencies and unreliability due to outdated location information and message delays or loss in distributed partitioned systems.

Innovation Solution

Implementing version indicators within a distributed data store to track partition reconfigurations and using broadcast messages to disseminate updated location information across nodes, ensuring that client nodes maintain up-to-date location information through request-response mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If distributed partitioned data stores are used to scale data storage, then storage capacity and system availability are improved, but location information becomes outdated and message reliability deteriorates

Engineering Contradiction:
Improvestorage capacityVSAvoidlocation information accuracy
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The system performs preliminary actions by proactively broadcasting location update information to all nodes before data access failures occur. The partition manager maintains a list of updated partitions and actively pushes location information to nodes, ensuring that location data is current before it is needed for data retrieval operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where nodes send status information back to the partition manager, and the partition manager responds with targeted location updates. This closed-loop feedback ensures that location information is continuously synchronized across the distributed system, preventing outdated location data from causing access failures.

Inventive Principle:
Principle #23Feedback

2Reliability

If broadcast messages are sent to all nodes for location updates, then location information accuracy is improved, but message loss and system complexity increase

Engineering Contradiction:
Improvelocation information accuracyVSAvoidmessage management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system applies local quality by sending location update information only to specific nodes that need it, rather than uniformly to all nodes. The partition manager identifies which nodes have outdated location information for particular partitions and targets updates only to those nodes, reducing unnecessary message traffic and simplifying message management.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system segments location update messages by partition, sending updates for each partition only to nodes that need them. Instead of a single monolithic broadcast to all nodes, the system divides updates into partition-specific segments and distributes them selectively, reducing message complexity and potential loss.

Inventive Principle:
Principle #1Segmentation

3Reliability

If location updates are sent frequently to ensure accuracy, then data access reliability is improved, but system performance and time efficiency deteriorate

Engineering Contradiction:
Improvedata access reliabilityVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system uses periodic action by broadcasting location update information at regular intervals rather than continuously. This periodic broadcasting ensures that location information remains current without the overhead of constant updates, balancing reliability with system performance by updating locations at optimal intervals rather than continuously.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system performs preliminary location updates before data access operations occur. By proactively updating location information in advance and maintaining it in a ready state, the system ensures fast data access without needing frequent real-time updates during operation, improving both reliability and performance.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8484417B2Location updates for a distributed data store
Publication Date: 2013.07.09 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8484417B2 patent drawing
  • US8484417B2 patent drawing
  • US8484417B2 patent drawing

AI summary

Version indicators within an existing range can be associated with a data partition in a distributed data store. A partition reconfiguration can be associated with one of multiple partitions in the data store, and a new version indicator that is outside the existing range can be assigned to the reconfigured partition. Additionally, a broadcast message can be sent to multiple nodes, which can include storage nodes and/or client nodes that are configured to communicate with storage nodes to access data in a distributed data store. The broadcast message can include updated location information for data in the data store. In addition, a response message can be sent to a requesting node of the multiple nodes in response to receiving from that node a message that requests updated location information for the data. The response message can include the requested updated location information.