暫時性故障是指透過 mssql-python 驅動程式連接 SQL Server 和 Azure SQL 時可能發生的暫時錯誤。 這些錯誤通常會自行解決:
- 網路連線短暫中斷。
- 伺服器資源限制。
- Azure SQL 節流
- 故障轉移事件。
實作重試邏輯能提升應用程式的可靠性,尤其是雲端託管資料庫。
不要用重試來隱藏設定或程式碼錯誤。 資料庫遺失、憑證錯誤或連線池耗盡,需要修復,而不是再嘗試一次。
識別暫態錯誤
mssql-python 不會在例外時將 SQL Server 引擎的錯誤編號作為屬性揭露。 驅動程式會將 SQLSTATE 程式碼映射到固定的 PEP 249 例外子類別(OperationalError、 ProgrammingError等等)以及屬性中的 driver_error 標準化英文文本。 將此組合作為暫態分類的基礎。
可靠的瞬態訊號
以下 SQLSTATE 值會以 OperationalError 傳回,表示該狀況值得重試。 右側欄位顯示駕駛者設定的精確 driver_error 文字:
| SQLSTATE |
driver_error 正文 |
狀況 |
|---|---|---|
HYT00 |
Timeout expired |
陳述層級的暫停。 |
HYT01 |
Connection timeout expired |
連線時間暫停。 |
08001 |
Client unable to establish connection |
無法開啟連線。 |
08S01 |
Communication link failure |
網路斷線、伺服器重置、TCP 故障。 |
08007 |
Connection failure during transaction |
連線在交易中途中斷。 |
40001 |
Serialization failure |
僵局受害者。 |
40003 |
Statement completion unknown |
交易狀態不確定。 |
import mssql_python
TRANSIENT_DRIVER_ERRORS = frozenset({
"Timeout expired",
"Connection timeout expired",
"Client unable to establish connection",
"Communication link failure",
"Connection failure during transaction",
"Serialization failure",
"Statement completion unknown",
})
def is_transient_error(error: BaseException) -> bool:
"""Return True if the exception represents a retryable transient failure.
Classification is based on the driver's PEP 249 exception subclass and
on the standardized `driver_error` text that mssql-python sets from
the SQLSTATE returned by the server.
"""
if isinstance(error, mssql_python.OperationalError):
return getattr(error, "driver_error", "") in TRANSIENT_DRIVER_ERRORS
return False
Azure SQL 節流(盡力而為)
Azure SQL 節流錯誤(40197、40501、40613、49918、49919、49920 及相關程式碼)通常會以 SQLSTATE 42000 的形式出現,而 mssql-python 會將其對應為 ProgrammingError。 引擎錯誤編號不會以屬性形式顯示,所以唯一的訊號是屬性中的 ddbc_error 伺服器訊息文字。
如果您的工作負載在 Azure SQL 上執行,且需要在發生節流時重試,請查找 ddbc_error 中的已知編號。 這是盡力而為,因為伺服器端文字的格式並非穩定的合約:
import re
# Azure SQL throttling and reconfiguration error numbers.
AZURE_THROTTLING_ERRORS = frozenset({
40197, 40501, 40540, 40613, 40680, 49918, 49919, 49920, 10928, 10929,
})
_ERROR_NUMBER_RE = re.compile(r"\b(?:Error|Msg)\s+(\d+)\b")
def is_azure_throttling(error: BaseException) -> bool:
"""Best-effort detection of Azure SQL throttling in ProgrammingError text."""
if not isinstance(error, mssql_python.ProgrammingError):
return False
ddbc_text = getattr(error, "ddbc_error", "") or ""
return any(int(m) in AZURE_THROTTLING_ERRORS for m in _ERROR_NUMBER_RE.findall(ddbc_text))
def is_retryable(error: BaseException) -> bool:
return is_transient_error(error) or is_azure_throttling(error)
不應重試的情況
應該快速失敗而不必重試的錯誤範例包括無效憑證(OperationalError 帶有驅動文字 Invalid authorization specification)、缺少或無法存取的資料庫、語法錯誤()、ProgrammingError缺少物件,以及連線池耗盡。
is_transient_error上述函數結構排除了所有這些。
基本重試裝飾器
簡單重試,固定延遲
裝飾器會以固定次數以恆定延遲重試包裹函式:
import time
import functools
import mssql_python
def retry_on_failure(max_retries: int = 3, delay: float = 1.0):
"""Decorator to retry database operations on transient failures."""
def decorator(func):
@functools.wraps(func)
def wrapper(*args, **kwargs):
last_exception = None
for attempt in range(max_retries + 1):
try:
return func(*args, **kwargs)
except mssql_python.Error as e:
last_exception = e
if not is_transient_error(e) or attempt == max_retries:
raise
print(f"Attempt {attempt + 1} failed: {e}. Retrying in {delay}s...")
time.sleep(delay)
raise last_exception
return wrapper
return decorator
# Usage
@retry_on_failure(max_retries=3, delay=2.0)
def get_user(cursor, user_id: int):
cursor.execute("SELECT * FROM Person.Person WHERE BusinessEntityID = %(id)s", {"id": user_id})
return cursor.fetchone()
指數輪詢
讓每次重試之間的延遲以指數方式增加,並可選擇加入隨機抖動,以分散並行重試:
import time
import random
def retry_with_backoff(max_retries: int = 5,
base_delay: float = 1.0,
max_delay: float = 30.0,
jitter: bool = True):
"""Retry with exponential backoff and optional jitter."""
def decorator(func):
@functools.wraps(func)
def wrapper(*args, **kwargs):
last_exception = None
for attempt in range(max_retries + 1):
try:
return func(*args, **kwargs)
except mssql_python.Error as e:
last_exception = e
if not is_transient_error(e) or attempt == max_retries:
raise
# Calculate delay with exponential backoff
delay = min(base_delay * (2 ** attempt), max_delay)
if jitter:
delay = delay * (0.5 + random.random())
print(f"Attempt {attempt + 1} failed. Retrying in {delay:.2f}s...")
time.sleep(delay)
raise last_exception
return wrapper
return decorator
@retry_with_backoff(max_retries=5, base_delay=1.0, max_delay=30.0)
def execute_query(cursor, query: str, params: dict):
cursor.execute(query, params)
return cursor.fetchall()
連線重試類別
韌性連線管理器
一個同時處理重試與自動重新連線的連線包裝器:
import mssql_python
import time
import logging
# This example uses is_transient_error from the "Identify transient errors"
# section earlier in this article. Include that helper in your module.
# Configure logging so the retry and reconnect messages are visible
logging.basicConfig(level=logging.INFO)
class ResilientConnection:
"""Connection wrapper with automatic retry and reconnection."""
def __init__(self, connection_string: str, max_retries: int = 5,
base_delay: float = 1.0, max_delay: float = 60.0):
self.connection_string = connection_string
self.max_retries = max_retries
self.base_delay = base_delay
self.max_delay = max_delay
self._conn = None
self._logger = logging.getLogger(__name__)
def _connect(self) -> mssql_python.Connection:
"""Establish connection with retry logic."""
last_exception = None
for attempt in range(self.max_retries + 1):
try:
self._logger.debug(f"Connection attempt {attempt + 1}")
return mssql_python.connect(self.connection_string)
except mssql_python.Error as e:
last_exception = e
if not is_transient_error(e) or attempt == self.max_retries:
self._logger.error(f"Connection failed: {e}")
raise
delay = min(self.base_delay * (2 ** attempt), self.max_delay)
self._logger.warning(f"Connection attempt {attempt + 1} failed. "
f"Retrying in {delay:.1f}s...")
time.sleep(delay)
raise last_exception
@property
def connection(self) -> mssql_python.Connection:
"""Get or create connection."""
if self._conn is None:
self._conn = self._connect()
return self._conn
def execute(self, query: str, params: dict = None):
"""Execute query with automatic retry and reconnection."""
return self._execute_with_retry(
lambda c: self._do_execute(c, query, params)
)
def _do_execute(self, cursor, query: str, params: dict):
cursor.execute(query, params or {})
return cursor.fetchall()
def _execute_with_retry(self, operation):
"""Execute an operation with retry logic."""
last_exception = None
for attempt in range(self.max_retries + 1):
try:
cursor = self.connection.cursor()
return operation(cursor)
except mssql_python.Error as e:
last_exception = e
if not is_transient_error(e):
raise
if attempt == self.max_retries:
raise
# Try to reconnect
self._logger.warning(f"Operation failed. Reconnecting...")
self._close()
delay = min(self.base_delay * (2 ** attempt), self.max_delay)
time.sleep(delay)
raise last_exception
def _close(self):
"""Close connection."""
if self._conn:
try:
self._conn.close()
except:
pass
self._conn = None
def close(self):
"""Public close method."""
self._close()
def __enter__(self):
return self
def __exit__(self, exc_type, exc_val, exc_tb):
self.close()
return False
# Usage
with ResilientConnection(connection_string) as db:
users = db.execute("SELECT * FROM Person.Person WHERE EmailPromotion = %(promo)s",
{"promo": 1})
print(f"Retrieved {len(users)} rows")
Azure SQL 特定處理
處理 Azure 節流
Azure SQL 限速錯誤需要比標準暫態錯誤更長的延遲和更多重試。 重用 is_azure_throttling 自 識別暫態錯誤:
def execute_with_throttle_handling(cursor, query: str, params: dict,
max_retries: int = 10,
base_delay: float = 5.0):
"""Execute with extended retry for Azure SQL throttling."""
for attempt in range(max_retries + 1):
try:
cursor.execute(query, params)
return cursor.fetchall()
except mssql_python.Error as e:
if is_azure_throttling(e):
if attempt < max_retries:
# Longer delays for throttling
delay = base_delay * (2 ** min(attempt, 4)) # Cap at 80s
print(f"Throttled. Waiting {delay}s before retry...")
time.sleep(delay)
continue
raise
處理故障轉移
當 Azure SQL 或可用性群組發生故障轉移而導致連線中斷時,請重新連線並重試:
def execute_with_failover_retry(connect, query: str, params: dict,
max_retries: int = 3,
recovery_delay: float = 10.0):
"""Reconnect and retry during Azure SQL failover scenarios."""
failover_numbers = frozenset({40613, 40197, 40540})
last_exception = None
for attempt in range(max_retries + 1):
conn = None
try:
conn = connect()
cursor = conn.cursor()
cursor.execute(query, params)
return cursor.fetchall()
except mssql_python.Error as e:
last_exception = e
# Failover surfaces either as a transient OperationalError or as
# a ProgrammingError whose ddbc_error text contains the engine
# error number. Treat both as recoverable.
ddbc_text = getattr(e, "ddbc_error", "") or ""
is_failover = is_transient_error(e) or any(
int(m) in failover_numbers for m in _ERROR_NUMBER_RE.findall(ddbc_text)
)
if is_failover and attempt < max_retries:
print(f"Failover detected. Reconnecting in {recovery_delay}s...")
if conn is not None:
try:
conn.close()
except mssql_python.Error:
pass
time.sleep(recovery_delay)
continue
raise
raise last_exception
# Usage
connection_string = (
"Server=tcp:<server>.database.windows.net,1433;"
"Database=AdventureWorks2022;"
"Authentication=ActiveDirectoryDefault;"
"Encrypt=yes;TrustServerCertificate=no"
)
rows = execute_with_failover_retry(
lambda: mssql_python.connect(connection_string),
"SELECT TOP 10 ProductID, Name FROM Production.Product WHERE Color = %(color)s",
{"color": "Silver"}
)
死鎖處理
發生死鎖時重試
死結(錯誤 1205)是暫時性的。 用短暫的隨機延遲重試以打破僵局循環。 重試可以處理立即失敗,但反覆出現的死機表示設計有問題,應該在伺服器端調查。 關於分析與解決根本原因的指引,請參見 死結錯誤。
def execute_with_deadlock_retry(cursor, query: str, params: dict,
max_retries: int = 3):
"""Automatically retry deadlocked transactions.
Deadlocks (SQL Server error 1205) surface as OperationalError with
driver_error == "Serialization failure" (SQLSTATE 40001).
"""
for attempt in range(max_retries + 1):
try:
cursor.execute(query, params)
return cursor.fetchall()
except mssql_python.OperationalError as e:
if getattr(e, "driver_error", "") == "Serialization failure":
if attempt < max_retries:
delay = random.uniform(0.1, 0.5) * (attempt + 1)
print(f"Deadlock detected. Retry {attempt + 1} in {delay:.2f}s")
time.sleep(delay)
continue
raise
# Usage in transaction
conn.autocommit = False
try:
cursor = conn.cursor()
rows = execute_with_deadlock_retry(
cursor,
"SELECT TOP 5 Name, ListPrice FROM Production.Product WHERE ListPrice > %(price)s",
{"price": 100}
)
conn.commit()
except Exception:
conn.rollback()
raise
結構化重試與配置
重試原則類別
將重試配置封裝在資料類別中,以便在不同操作間重複使用:
from dataclasses import dataclass, field
from typing import FrozenSet
import time
import random
# This example uses TRANSIENT_DRIVER_ERRORS from the "Identify transient errors"
# section earlier in this article. Include that allowlist in your module.
@dataclass
class RetryPolicy:
"""Configuration for retry behavior."""
max_retries: int = 3
base_delay: float = 1.0
max_delay: float = 30.0
exponential_base: float = 2.0
jitter: bool = True
transient_driver_errors: FrozenSet[str] = field(default_factory=lambda: TRANSIENT_DRIVER_ERRORS)
def get_delay(self, attempt: int) -> float:
"""Calculate delay for given attempt number."""
delay = min(
self.base_delay * (self.exponential_base ** attempt),
self.max_delay,
)
if self.jitter:
delay *= (0.5 + random.random())
return delay
def should_retry(self, error: BaseException, attempt: int) -> bool:
"""Determine if operation should be retried."""
if attempt >= self.max_retries:
return False
if isinstance(error, mssql_python.OperationalError):
return getattr(error, "driver_error", "") in self.transient_driver_errors
return False
def execute_with_policy(cursor, query: str, params: dict,
policy: RetryPolicy = None):
"""Execute query with configurable retry policy."""
policy = policy or RetryPolicy()
last_exception = None
for attempt in range(policy.max_retries + 1):
try:
cursor.execute(query, params)
return cursor.fetchall()
except mssql_python.Error as e:
last_exception = e
if not policy.should_retry(e, attempt):
raise
delay = policy.get_delay(attempt)
time.sleep(delay)
raise last_exception
# Usage with custom policy
aggressive_retry = RetryPolicy(max_retries=10, base_delay=0.5, max_delay=60.0)
conservative_retry = RetryPolicy(max_retries=2, base_delay=5.0, max_delay=10.0)
results = execute_with_policy(cursor, query, params, aggressive_retry)
斷路器模式
透過追蹤連續錯誤,並在達到閾值時暫時封鎖通話,防止連鎖故障:
import time
from enum import Enum
from threading import Lock
class CircuitState(Enum):
CLOSED = "closed" # Normal operation
OPEN = "open" # Failing, reject all calls
HALF_OPEN = "half_open" # Testing if service recovered
class CircuitBreaker:
"""Circuit breaker to prevent cascading failures."""
def __init__(self, failure_threshold: int = 5,
recovery_timeout: float = 30.0):
self.failure_threshold = failure_threshold
self.recovery_timeout = recovery_timeout
self.state = CircuitState.CLOSED
self.failure_count = 0
self.last_failure_time = None
self._lock = Lock()
def can_execute(self) -> bool:
"""Check if circuit allows execution."""
with self._lock:
if self.state == CircuitState.CLOSED:
return True
if self.state == CircuitState.OPEN:
# Check if recovery timeout has passed
if time.time() - self.last_failure_time > self.recovery_timeout:
self.state = CircuitState.HALF_OPEN
return True
return False
# HALF_OPEN: allow one test request
return True
def record_success(self):
"""Record successful operation."""
with self._lock:
self.failure_count = 0
self.state = CircuitState.CLOSED
def record_failure(self):
"""Record failed operation."""
with self._lock:
self.failure_count += 1
self.last_failure_time = time.time()
if self.failure_count >= self.failure_threshold:
self.state = CircuitState.OPEN
# Usage
circuit = CircuitBreaker(failure_threshold=5, recovery_timeout=30.0)
def execute_with_circuit_breaker(cursor, query: str, params: dict):
if not circuit.can_execute():
raise Exception("Circuit breaker is open")
try:
cursor.execute(query, params)
result = cursor.fetchall()
circuit.record_success()
return result
except mssql_python.Error as e:
if is_transient_error(e):
circuit.record_failure()
raise
相關內容
發生組態錯誤時請勿重試
並非每個錯誤都是短暫的。 重試設定或程式碼錯誤會浪費時間,也可能掩蓋真正的問題。 只重試那些可能自行解決的錯誤。 因為 mssql-python 不會將引擎錯誤編號公開為屬性,所以請根據例外子類別加上 driver_error 文字來分類。
切勿重試這些( 改為修正程式碼或設定):
| 狀況 | 例外狀況類型 |
driver_error 正文 |
修復 |
|---|---|---|---|
| 物件名稱無效(引擎 208) | ProgrammingError |
Base table or view not found |
該資料表不存在。 修正查詢或建立資料表。 |
| 欄位名稱無效(引擎 207) | ProgrammingError |
Column not found |
那欄根本不存在。 檢查架構。 |
| 語法錯誤(引擎 102) | ProgrammingError |
Syntax error or access violation |
修正查詢。 |
| 登入失敗(引擎 18456) | OperationalError |
Invalid authorization specification |
資格證明錯誤。 修正連線字串。 |
| 無法開啟資料庫(引擎 4060) | OperationalError |
Server rejected the connection |
資料庫不存在,或是登入時無法存取。 設定目標或權限。 |
| 連線集區耗盡 | OperationalError |
(變化不一) | 增加池容量、及時釋放連線,或減少並行。 |
ConnectionStringParseError |
獨立 | n/a | 連線字串關鍵字中的拼寫錯誤。 把繩子修好。 |
| 不支援的功能 | NotSupportedError |
Optional feature not implemented |
請採用替代方法。 |
這些一律重試(它們會自行解決):
| 狀況 | 例外狀況類型 |
driver_error 正文 |
|---|---|---|
| 陳述式逾時 | OperationalError |
Timeout expired |
| 連線逾時 | OperationalError |
Connection timeout expired |
| 無法開啟連線 | OperationalError |
Client unable to establish connection |
| 網路掉落 | OperationalError |
Communication link failure |
| 連線在交易進行中中斷 | OperationalError |
Connection failure during transaction |
| 死結犧牲者(引擎 1205) | OperationalError |
Serialization failure |
| 不確定交易狀態 | OperationalError |
Statement completion unknown |
| Azure SQL throttling (40197, 40501, 40613, 49918–49920) | ProgrammingError |
Syntax error or access violation(引擎編號僅在 ddbc_error 中;請使用 is_azure_throttling) |