Content-Sensitive Container Scheduling for Hot Starts

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Container management systems like Kubernetes face challenges in migrating stateful applications, such as caching servers, due to the performance hit from leaving behind large amounts of cached data when containers are moved to new hosts, leading to slow response times and inefficient service ramp-up.

Innovation Solution

Implementing a content-sensitive container scheduling system that monitors and selects optimal hosts based on quality indicators and metrics, allowing new instances of applications to reuse cached content from previous instances, thereby reducing the need for data migration and improving performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If containers are moved from host to host for updates or failures, then system reliability is improved, but service performance deteriorates due to cold cache

Engineering Contradiction:
Improvesystem reliabilityVSAvoidservice performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent uses content-addressable storage to create content copies of cached data. When a container is migrated, the new instance can quickly restore cached content from the content-addressable storage system rather than rebuilding it from scratch, enabling hot starts while maintaining migration capability for reliability

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system pre-loads and stores cached content in content-addressable storage before container migration occurs. This preliminary action ensures that when a container is restarted on a different host, the cached content is already available, eliminating the cold cache problem and enabling immediate service performance

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If containers are migrated to new hosts, then load balancing is improved, but data reuse capability deteriorates

Engineering Contradiction:
Improveload balancingVSAvoidcached data reuse
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent introduces content-addressable storage as an intermediary layer between containers and persistent storage. This intermediary decouples the container from its cached data, allowing containers to be migrated for load balancing while the cached content remains preserved in the content-addressable storage system for future reuse by new container instances

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system extracts cached content from the container lifecycle and stores it independently in content-addressable storage. This extraction allows the container to be freely migrated for load balancing purposes while the cached data remains intact and can be quickly restored to new container instances, preventing data loss

Inventive Principle:
Principle #2Taking out (Extraction)

3Productivity

If cached data is preserved on local disks, then service performance is improved, but portability deteriorates

Engineering Contradiction:
Improveservice performanceVSAvoidportability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent introduces content-addressable storage as an intermediary between the container's cached data and the underlying storage infrastructure. This intermediary layer preserves the high performance benefits of local cached data while abstracting the portability constraint, allowing containers to be migrated across hosts because the cached content is managed independently in the content-addressable storage system

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system separates the cached data management into a different dimension by using content-addressable storage instead of traditional local disk binding. This dimensional change allows the container to access cached content regardless of which host it runs on, simultaneously achieving high performance through cached data and high portability through decoupled storage management

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS11650894B2Content-sensitive container scheduling on clusters
Publication Date: 2023.05.16 SALESFORCE INC
  • US11650894B2 patent drawing
  • US11650894B2 patent drawing
  • US11650894B2 patent drawing

AI summary

Content-sensitive computer applications are run on computer hosts in a computer cluster. A computer application running history including but not limited to computer host scores is recorded for the computer cluster. A request to start a container for a content-sensitive computer application type in the computer cluster is received. In response, available computer hosts in the computer cluster are identified. A specific computer host is selected from among the available computer hosts to run the container for the content-sensitive computer application type.