Microservice Node Failure Impact Scheduling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional approaches to deploying and hosting applications in micro-service environments fail to consider the impact of node failures on service disruptions, leading to inefficient scheduling and increased service losses.

Innovation Solution

Implement mechanisms to determine and select nodes based on service capacity factors and impact factors, which indicate the potential disruption impact of node failures, to minimize service losses by balancing service capacities across nodes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional deployment scheduling is used without considering node failure impact, then deployment simplicity is maintained, but service disruption increases

Engineering Contradiction:
Improveservice continuityVSAvoidscheduling complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary evaluation of node failure impact before deployment scheduling. By calculating impact factors for each node in advance, the system identifies critical nodes that would cause significant service disruptions if failed. This preliminary action enables the scheduler to avoid placing service replicas on high-impact nodes, thereby improving service continuity without requiring complex real-time decision-making during failures.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by continuously monitoring service capacity factors and node impact factors, then using this information to adjust deployment schedules. The scheduler receives feedback about which nodes are critical for service continuity and modifies its decisions accordingly, creating a closed-loop system that improves reliability based on actual system state rather than static rules.

Inventive Principle:
Principle #23Feedback

2Reliability

If service replicas are distributed without considering node service capacity, then deployment speed is maintained, but service loss increases

Engineering Contradiction:
Improveservice capacity balanceVSAvoiddeployment efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system changes the parameters used for deployment scheduling by incorporating service capacity factors and node impact factors into the scheduling decision process. Instead of using only basic resource availability metrics, the scheduler now considers weighted combinations of multiple parameters including service capacity utilization and potential service loss from node failures. This parameter expansion enables more intelligent placement decisions that balance reliability and deployment efficiency.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system applies local quality by treating different nodes differently based on their specific service capacity characteristics and failure impact profiles. Rather than using a uniform deployment strategy across all nodes, the scheduler assigns service replicas to nodes based on their individual service capacity factors, ensuring that nodes with higher service capacity and lower failure impact receive appropriate service placements. This localized approach optimizes overall service capacity balance.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11537458B2Reducing service disruptions in a micro-service environment
Publication Date: 2022.12.27 RED HAT INC
  • US11537458B2 patent drawing
  • US11537458B2 patent drawing
  • US11537458B2 patent drawing

AI summary

Aspects of the disclosure provide for reducing service disruptions in a computer system. A method of the disclosure may include identifying a plurality of services running on a node of a computer system, determining a plurality of priorities corresponding to the plurality of services, determining a plurality of service capacity factors for the plurality of services in view of the plurality of priorities, and determining a lost impact factor in view of the plurality of service capacity factors.