Metadata Replication Configuration Scoring for Distributed Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing techniques for managing availability domain fault tolerance in distributed computing systems often result in sub-optimal ring configurations due to the failure to consider load balancing and costs of data reapportionment, leading to inefficient resource allocation and increased implementation expenses.

Innovation Solution

The implementation of cost-oriented selection techniques that score and select metadata replication configurations based on hardware fault/availability domain boundaries, using topology attributes to generate candidate configurations and compute configuration scores for load balancing and resource usage balance, ensuring optimal resource allocation and fault tolerance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If existing techniques are used to manage availability domain fault tolerance, then fault tolerance is provided, but sub-optimal ring configurations result due to failure to consider load balancing and data reapportionment costs

Engineering Contradiction:
Improveavailability domain fault toleranceVSAvoidresource allocation efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system changes the parameters used for configuration selection by introducing cost-oriented scoring that considers load balancing and data reapportionment costs. Instead of using only fault tolerance criteria, the system evaluates multiple parameters including resource usage balance scores and implementation costs to select optimal replication configurations.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring resource usage measurements and updating configuration scores accordingly. The cost-oriented selection process uses feedback from resource usage data to adjust and optimize replication configurations, ensuring that load balancing and reapportionment costs are considered in subsequent selections.

Inventive Principle:
Principle #23Feedback

2Reliability

If existing techniques are used to manage availability domain fault tolerance, then fault tolerance is provided, but increased implementation expenses result due to inefficient resource allocation

Engineering Contradiction:
Improveavailability domain fault toleranceVSAvoidimplementation expenses
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system introduces cost parameters into the configuration selection process, evaluating both technical merit and implementation expenses. By changing the selection criteria to include cost-oriented scoring, the system identifies configurations that achieve fault tolerance at lower implementation costs, reducing unnecessary data movement and resource allocation expenses.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system performs preliminary evaluation of candidate configurations using cost-oriented scoring before implementation. By pre-assessing load balancing requirements and data reapportionment costs, the system selects configurations that minimize implementation expenses from the outset, avoiding costly post-deployment adjustments.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If data replication is implemented across available hardware, then data consistency and availability are improved, but sub-optimal configurations increase resource usage and network bandwidth demand

Engineering Contradiction:
Improvedata consistencyVSAvoidnetwork bandwidth usage
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system changes the approach to data replication by using cost-oriented configuration selection that explicitly considers network bandwidth usage and resource consumption. The scoring mechanism evaluates candidate configurations based on their expected resource usage patterns, selecting replicas placements that maintain data consistency while minimizing network bandwidth demand and energy consumption.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system applies local quality optimization by selecting replication configurations tailored to specific hardware characteristics and resource usage patterns. Instead of uniform replication strategies, the system evaluates local conditions at each hardware location and selects configurations that optimize resource usage and network bandwidth utilization for each specific context.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10678457B2Establishing and maintaining data apportioning for availability domain fault tolerance
Publication Date: 2020.06.09 NUTANIX INC
  • US10678457B2 patent drawing
  • US10678457B2 patent drawing
  • US10678457B2 patent drawing

AI summary

Systems for distributed computing systems. A topological configuration of computing nodes is selected to manage availability of metadata data in a computing system. A method embodiment commences by accessing a plurality of node topology attributes and using those attributes to map between nodes and availability domains. Resource usage measurements such as computing node load are collected. A plurality of candidate replication configurations are generated, and each candidate replication configuration is scored with respect to several quantitative objectives. Additionally, the candidate replication configurations are given respective resource usage balance scores. One or more candidate replication configurations are selected based on resource usage balance scores and/or a separation skew value. Determination of a selected configuration is dominated by resource usage when there is a tie between best-scoring configurations or when none of the configurations meet a scoring threshold. Recalculation of configurations are triggered by an administrative command or by a topology change.