Database Load Balancer Table-Level Error Isolation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database load balancer solutions apply state changes and administrative tasks at a system level, affecting all tables and systems, even when inconsistencies or errors are localized to specific tables or subsystems, leading to operational inefficiencies and potential data fragmentation.
Innovation Solution
The Teradata Unity system employs expanded load balancer algorithms that allow for granular processing of error conditions and operational states at a database table level, enabling selective application of administrative tasks and error handling, allowing continued operation of other applications and queries on unaffected systems while isolating affected tables or subsystems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If state changes and administrative tasks are applied at a system level, then system-wide consistency is maintained, but operational efficiency deteriorates and system availability decreases
Solution Approach 1:
The patent segments the database system into multiple independent subsystems (tables, indexes, partitions) that can be managed individually. Instead of applying state changes at the system level, the load balancer identifies and applies changes only to affected subsystems, allowing other parts of the system to continue operating normally. This segmentation resolves the contradiction by maintaining consistency where needed while preserving operational efficiency in unaffected areas.
Solution Approach 2:
The patent implements local quality by applying administrative tasks and state changes only to specific subsystems where inconsistencies or errors are detected, rather than uniformly across the entire system. The load balancer monitors individual subsystems and applies recovery operations locally, allowing other subsystems to maintain their normal operational state and continue processing requests without interruption.
2Reliability
If state changes are applied at a system level, then comprehensive error handling is achieved, but system availability deteriorates
Solution Approach 1:
The patent divides the database system into separable subsystems that can be independently managed. When an error is detected in one subsystem, the load balancer applies error handling measures only to that specific subsystem while leaving other subsystems operational. This segmentation enables comprehensive error handling where needed while maintaining system availability through independent operation of unaffected subsystems.
Solution Approach 2:
The load balancer acts as an intermediary between the client and the database subsystems. It monitors the state of individual subsystems and intermediates error handling by routing requests away from affected subsystems and toward healthy ones, applying state changes only where necessary. This intermediary approach ensures comprehensive error handling while preserving system availability through intelligent request routing.
3Device complexity
If system-level administrative tasks are performed, then centralized control is maintained, but operational complexity increases
Solution Approach 1:
The patent segments administrative control into subsystem-level operations managed by the load balancer. Instead of requiring centralized system-level administrative tasks, the load balancer independently monitors and manages individual subsystems, applying state changes only where needed. This segmentation reduces operational complexity by eliminating the need for system-wide administrative interventions while maintaining effective centralized control through the load balancer's coordination.
Data Source
AI summary
A method and system for managing operational states of database tables within a multiple-database system. If a particular user session issues a query against a target table that causes a data inconsistency, the target table transitions into an errant state and the session will become interrupted. This errant state is then propagated onto any other table associated with the user session. A session-level recovery process can thereafter be executed to repair and restore database tables associated with the interrupted user sessions without the need to take an entire database system offline.