Transaction Lock Wait History via Telemetry Events
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data systems face challenges in efficiently managing transaction locks and constructing transaction lock wait history, particularly in identifying blocker queries that cause delays.
Innovation Solution
The proposed solution involves a method for constructing a transaction lock wait history by generating telemetry events for lock waits and grants, which are then used to identify blocker queries and optimize lock management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If transaction lock wait history is constructed using traditional methods, then complete lock information can be captured, but the system complexity and processing overhead increase significantly
Solution Approach 1:
The system pre-assigns unique transaction IDs to transactions before they acquire locks, and pre-configures event listeners to monitor lock events. This preliminary setup eliminates the need for complex post-processing and reduces system complexity while maintaining complete lock wait history accuracy.
Solution Approach 2:
The patent introduces an intermediary component (lock event listener/monitor) that sits between the transaction processing system and the history recording system. This intermediary captures lock events in real-time and formats them for storage, simplifying both the transaction processing system and the history analysis system while ensuring complete and accurate lock wait history.
2Loss of information
If detailed telemetry events are generated for every lock wait and grant, then complete troubleshooting information is available, but the data processing and storage requirements increase
Solution Approach 1:
The system extracts only the essential troubleshooting information from lock events (transaction IDs, lock timestamps, blocker relationships) and stores them in a structured format. Non-essential data is excluded, reducing storage requirements while maintaining complete troubleshooting capability.
Solution Approach 2:
The patent transforms raw lock event data into standardized parameters with specific formats (timestamps, transaction IDs, event types). This parameterization allows efficient storage and retrieval while maintaining complete information for troubleshooting, reducing data volume through consistent formatting and indexing.
Data Source
AI summary
Techniques for constructing transaction lock wait history showing blocker queries are described. A first transaction referencing a resource saved in a network-based data warehouse is received where the first transaction being blocked due to second transaction accessing the resource. A first telemetry event based on the first transaction being blocked is transmitted. After acquiring lock ownership of the resource by the first transaction, a second telemetry event based on acquiring lock ownership by the first transaction is transmitted.