IP Library Granted Patent US 11,693,723
Granted Patent B2
US 11,693,723 · App. 17/537,124 · Granted Jul 4, 2023

Query watchdog

Inventors: Alicja Luszczak (Amsterdam, NL); Srinath Shankar (Belmont, CA); Shi Xin (San Francisco, CA)
Assignee: Databricks, Inc.
G06F11/0757G06F11/076G06F11/0721G06F11/0793G06F11/3024G06F11/3419G06F2201/81G06F2201/88
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,693,723
App. No.
17/537,124
Granted
Jul 4, 2023
Kind
B2
Abstract

A system for monitoring job execution includes an interface and a processor. The interface is configured to receive an indication to start a cluster processing job. The processor is configured to determine whether processing a data instance associated with the cluster processing job satisfies a watchdog criterion; and in the event that processing the data instance satisfies the watchdog criterion, cause the processing of the data instance to be killed.

Claims (42)

1. A system for monitoring job execution, comprising:

an interface configured to:

receive an indication to start a cluster processing job; and

a processor configured to:

determine whether processing a data instance associated with the cluster processing job satisfies a watchdog criterion; and

in the event that processing the data instance satisfies the watchdog criterion:

determine whether the cluster processing job should be killed, comprising to:

determine whether the cluster processing job be killed after a single data instance that satisfies the watchdog criterion; and

in response to a determination that the cluster processing job be killed after the single data instance that satisfies the watchdog criterion, indicate that the cluster processing job should be killed.

2. The system of claim 1 , wherein the data instance comprises a row.

3. The system of claim 1 , wherein the watchdog criterion comprises a time limit exceeded for processing the data.

4. The system of claim 1 , wherein the watchdog criterion comprises a time limit exceeded during processing of a most recent N data instances, wherein N comprises a predetermined number of data instances for the time limit.

5. The system of claim 1 , wherein the watchdog criterion comprises an output limit exceeded during processing of the data instance.

6. The system of claim 5 , wherein the output limit comprises a number of output bytes.

7. The system of claim 5 , wherein the output limit comprises a number of output data instances.

8. The system of claim 5 , wherein the output limit comprises a number of output files.

9. The system of claim 1 , wherein the watchdog criterion comprises an output limit exceeded during processing of a most recent N data instances, wherein N comprises a predetermined number of data instances for the output limit.

10. The system of claim 1 , wherein the processor is further configured to cause processing of the cluster processing job to be killed.

11. The system of claim 10 , wherein the processor is further configured to indicate that the cluster processing job has been killed.

12. The system of claim 10 , wherein the processor is further configured to indicate the data instance that caused the cluster processing job to be killed.

13. The system of claim 1 , wherein the processor is further configured to indicate the watchdog criterion that has been satisfied.

14. The system of claim 1 , wherein the processor is further configured to:

after processing of the data instance is caused to be killed, cause processing of a next data instance.

15. The system of claim 14 , wherein the processor is further configured to indicate that processing of the data instance was caused to be killed.

16. The system of claim 14 , wherein the processor is further configured to store an indication in an output file that processing of the data instance was caused to be killed.

17. The system of claim 14 , wherein the processor is further configured to increment a killed data instance counter.

18. The system of claim 17 , wherein the processor is further configured to:

in the event a value of the killed data instance counter exceeds a threshold, cause execution of the cluster processing job to be killed.

19. A method for monitoring job execution, comprising:

receiving an indication to start a cluster processing job; and

determining, using a processor, whether processing a data instance associated with the cluster processing job satisfies a watchdog criterion; and

in the event that processing the data instance satisfies the watchdog criterion:

determining whether the cluster processing job should be killed, comprising:

determining whether the cluster processing job be killed after a single data instance that satisfies the watchdog criterion; and

in response to a determination that the cluster processing job be killed after the single data instance that satisfies the watchdog criterion, indicating that the cluster processing job should be killed.

20. A computer program product for monitoring job execution, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

receiving an indication to start a cluster processing job; and

determining whether processing a data instance associated with the cluster processing job satisfies a watchdog criterion; and

in the event that processing the data instance satisfies the watchdog criterion:

determining whether the cluster processing job should be killed, comprising:

determining whether the cluster processing job be killed after a single data instance that satisfies the watchdog criterion; and

in response to a determination that the cluster processing job be killed after the single data instance that satisfies the watchdog criterion, indicating that the cluster processing job should be killed.

Assignments (3)
SECURITY INTEREST Recorded Jan 6, 2025
From: DATABRICKS, INC.
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 069825/0419 →
CORRECTIVE ASSIGNMENT TO CORRECT THE THE ASSIGNEE NAME PREVIOUSLY RECORDED AT REEL: 063717 FRAME: 0246. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Nov 6, 2023
From: LUSZCZAK, ALICJA; SHANKAR, SRINATH; XIN, SHI
To: DATABRICKS, INC.
Reel/Frame 065462/0492 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 22, 2023
From: LUSZCZAK, ALICJA; SHANKAR, SRINATH; XIN, SHI
To: DATABRICKS INC.
Reel/Frame 063717/0246 →
Continuity (3)
Continuation 16793921 · Feb 18, 2020
Continuation 15809907 · Nov 10, 2017
Related Publication 20220083410A1 · Mar 17, 2022
Cited By (1)
US 12,287,698