Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
1) Identify any long running and expensive queries being currently executed. An example of this is when the application team ran a query that did a full table scan which caused disruption in the application and increased latency.
2) Any locks-based queries that are impacting the health of the system.
3) Identify any anti-pattern table architecture with non-Interleaving table design.
4) Automatic handling (Throttling at the client library level as an option. Throttling is the requirement ) of high surge of queries - Autoscale is not an option since Walmart has specific requirements that prevent them from using this feature. The application team is sending a timeout but failing the query is not desirable.