What does Single-Host Hot Migration and the Ten-Second Contract conclude, in numbers, about “Many Containers on One Host behind a Shared Tunnel: Common-Cause Failure, Reconnect Backoff and Memory Headroom for Dual Running”?

Answer: Chapter 4 shows that two colours on one host are capped by common-cause failure, saving only 262.1 minutes at a common-cause share of 0.5, and that a single tunnel connector with a short fixed retry recovers within ten seconds in a share of 0.9504, against 0.8518 for backoff with full jitter.

Scope of the numbers: Examples use fictional names, parameters are illustrative, and all calculations come from the book's programs, which connect to no server. Marked boxes separate published evidence, runnable Python calculations (22 programs), classical sources and the author's hypotheses.

中文版

Data table

The numbers below are printed verbatim by the chapter's Python program and can be reproduced by running it. printed values that match the answer: 0.5, 262.1

series ceiling host*tunnel*db: A = 0.998001, 1050.5 min a year
one app colour:A = 0.997003, 1575.1 min a year
betaA servicedown min/yrgain min/yr
0.00.9980001051.1524.0
0.10.9979011103.4471.7
0.30.9977011208.2366.9
0.50.9975021312.9262.1
1.00.9970031575.10.0
host share of the series downtime: 0.500
Show the full program
# Chapter 4. p41: what two app colours on one host can and cannot buy.
# Model: the service is up when the host, the shared tunnel, the db
# container and at least one app colour (app-blue or app-green) are up.
# Series parts multiply. The two app colours fail together with a
# beta-factor: a share beta of each colour's unavailability is common
# cause (same image, same config, same host kernel) and hits both;
# the rest is independent. Then the app pair is unavailable with
#   beta u + ((1 - beta) u)^2,  u = 1 - A_app.
# Availabilities are illustrative.
YEAR_MIN = 365.0 * 1440.0
A_HOST = 0.999
A_TUNNEL = 0.9995
A_DB = 0.9995
A_APP = 0.999
BETAS = (0.0, 0.1, 0.3, 0.5, 1.0)


def pair(beta, a=A_APP):
    u = 1.0 - a
    return 1.0 - (beta * u + ((1.0 - beta) * u) ** 2)


series = A_HOST * A_TUNNEL * A_DB
one = series * A_APP
print("series ceiling host*tunnel*db: A = %.6f, %.1f min a year" % (
    series, (1.0 - series) * YEAR_MIN))
print("one app colour:                A = %.6f, %.1f min a year" % (
    one, (1.0 - one) * YEAR_MIN))
print("%6s %12s %14s %12s" % ("beta", "A service", "down min/yr",
                              "gain min/yr"))
for b in BETAS:
    a = series * pair(b)
    print("%6.1f %12.6f %14.1f %12.1f" % (
        b, a, (1.0 - a) * YEAR_MIN, (a - one) * YEAR_MIN))
share = (1.0 - A_HOST) / (1.0 - series)
print("host share of the series downtime: %.3f" % share)

Single source and citation

Fan, Y. (2026). Zero-Downtime Hot Migration and Rollback on Multi-Container Single Hosts: Lossless Schema Evolution behind a Shared Tunnel and a Ten-Second Stop-the-Bleeding Contract (Version 1.0.0), Chapter 4: Many Containers on One Host behind a Shared Tunnel: Common-Cause Failure, Reconnect Backoff and Memory Headroom for Dual Running. 5D Library. DOI pending

DOI pending · monograph page goes live after publication · 5DL-B-269 · v1.0.0 · CC-BY-NC-ND-4.0

BibTeX
@book{fan2026269,
  author    = {Fan, Yafu},
  title     = {Zero-Downtime Hot Migration and Rollback on Multi-Container Single Hosts: Lossless Schema Evolution behind a Shared Tunnel and a Ten-Second Stop-the-Bleeding Contract},
  year      = {2026},
  publisher = {5D Library},
  edition   = {1.0.0},
  note      = {DOI pending}
}

Other chapter answers in this book