# US 2021/0173745 A1 · Ticketing system for managing computing services

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0173745 A1
- Document ID: US20210173745A1
- Status: Published application
- Kind: A1
- Application number: 16/709,667
- Filed: 2019-12-10
- Published: 2021-06-10
- Earliest claimed: 2019-12-10
- Assignees: salesforce.com, inc.
- Applicants: salesforce.com, inc.
- Inventors: Jeffrey ZOCH; Ted LIU; Karthik Mohan SUBRAMANIAN; Youngjin YU; Bo Xia; Yeshwant Sai MADANAGOPAL
- Web page: https://patentgrep.com/patent/US20210173745A1

## CPC

- G06F 9/4887: {involving deadlines, e.g. rate based, periodic}
- G06F 11/1458: {Management of the backup or restore process}
- G06F 9/466: {Transaction processing}
- G06F 9/485: {Task life-cycle, e.g. stopping, restarting, resuming execution (G06F9/4881 takes precedence)}
- G06F 9/4881: {Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues}
- G06F 11/1405: {at machine instruction level}
- G06F 11/1438: {Restarting or rejuvenating}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Examples include a ticketing system for managing performance of computer services. The ticketing system includes a ticket database to store a plurality of tickets, each ticket defining a job to be performed on a computing system, and a master to create a ticket, store the ticket in the ticket database, and update the ticket. The ticketing system includes a scheduler to determine whether to create the ticket based at least in part on a set of conditions, and to request the master to create the ticket when the ticket is to be created, and a worker to get the ticket from the master, perform the job defined by the ticket, and request the master to update the ticket with a status of the ticket. The ticketing system includes a supervisor to request the master to find a stale ticket, and, if found, to request the worker to abort performance of the job defined by the stale ticket.

## Claims

### Claim 1

A ticketing system comprising:
a ticket database to store a plurality of tickets, each ticket defining a job to be performed on a computing system;
a master, coupled to the ticket database, to create a ticket, store the ticket in the ticket database, and update the ticket;
a scheduler, coupled to the master, to determine whether to create the ticket based at least in part on a set of conditions, and to request the master to create the ticket when the ticket is to be created;
a worker, coupled to the master, to get the ticket from the master, perform the job defined by the ticket, and request the master to update the ticket with a status of the ticket; and
a supervisor, coupled to the worker and the master, to request the master to find a stale ticket, and, if found, to request the worker to abort performance of the job defined by the stale ticket.

### Claim 2 (depends on 1)

The ticketing system of claim 1, wherein the supervisor is to determine a maximum number of retries for the stale ticket, and if the number of retries of the stale ticket is more than the maximum number of retries, the supervisor is to request the master to update the ticket to reflect a status of aborted.

### Claim 3 (depends on 2)

The ticketing system of claim 2, wherein the supervisor is to determine a maximum number of retries for the stale ticket, and if the number of retries of the stale ticket is not more than the maximum number of retries, the supervisor is to request the master to update the ticket to a status of failed and to reset the failed stale ticket.

### Claim 4 (depends on 3)

The ticketing system of claim 3, wherein resetting the failed stale ticket comprises the supervisor to request the master to get the failed stale ticket from the ticket database and update the status of the failed stale ticket to new.

### Claim 5 (depends on 4)

The ticketing system of claim 4, wherein the supervisor is to check the status of the ticket being worked on by the worker and request the master to update the status of the ticket.

### Claim 6 (depends on 1)

The ticketing system of claim 1, wherein the ticket is idempotent.

### Claim 7 (depends on 1)

The ticketing system of claim 1, wherein the scheduler gets the set of conditions from one or more applications being executed by the computing system.

### Claim 8 (depends on 1)

The ticketing system of claim 1, wherein the job comprises one of a backup of a database system and a restore of the database system.

### Claim 9 (depends on 1)

The ticketing system of claim 1, wherein the master determines staleness of the ticket by analyzing a time threshold for a type of job to be performed according to the ticket.

### Claim 10 (depends on 1)

The ticketing system of claim 1, wherein one or more of the master, the scheduler, the worker, and the supervisor are executed independently and concurrently by one or more different processing cores of a multi-core computing system.

### Claim 11 (depends on 1)

The ticketing system of claim 1, wherein one or more of the master, the scheduler, the worker, and the supervisor are executed independently and concurrently by one or more different processing threads of a multi-threaded computing system.

### Claim 12 (depends on 1)

The ticketing system of claim 1, comprising
a plurality of schedulers, each scheduler adapted for a selected one of a plurality of types of jobs to be performed for the ticket; and
a plurality of workers, each worker adapted for a selected one of a plurality of types of jobs to be performed for the ticket.

### Claim 13

A method to be performed by one or more processors in a computing system, comprising:
determining, by a scheduler, whether to create an idempotent ticket based at least in part on a set of conditions, the ticket defining a job to be performed on the computing system;
creating, by a master, the ticket and storing the ticket in the ticket database;
getting, by a worker, the ticket from the master, performing the job defined by the ticket, and requesting the master to update the ticket with a status of the ticket; and
requesting, by a supervisor, the master to find a stale ticket, and, if found, to request the worker to abort performance of the job defined by the stale ticket.

### Claim 14 (depends on 13)

The method of claim 13, comprising:
determining, by the supervisor, a maximum number of retries for the stale ticket; and
if the number of retries of the stale ticket is more than the maximum number of retries, requesting, by the supervisor, the master to update the ticket to reflect a status of aborted.

### Claim 15 (depends on 14)

The method of claim 14, comprising:
determining, by the supervisor, the maximum number of retries for the stale ticket; and
if the number of retries of the stale ticket is not more than the maximum number of retries, requesting, by the supervisor, the master to update the ticket to a status of failed and to reset the failed stale ticket.

### Claim 16 (depends on 15)

The method of claim 15, wherein resetting the failed stale ticket comprises requesting the master to get the failed stale ticket from the ticket database and update the status of the failed stale ticket to new.

### Claim 17 (depends on 16)

The method of claim 16, comprising:
checking, by the supervisor, the status of the ticket being worked on by the worker and requesting the master to update the status of the ticket.

### Claim 18 (depends on 13)

The method of claim 13, comprising:
getting, by the scheduler, the set of conditions from one or more applications being executed by the computing system.

### Claim 19 (depends on 13)

The method of claim 13, comprising:
determining, by the master, staleness of the ticket by analyzing a time threshold for a type of job to be performed according to the ticket.

### Claim 20

At least one tangible machine-readable medium comprising a plurality of instructions that in response to being executed by a processor in a computing system cause the processor to:
determine, by a scheduler, whether to create an idempotent ticket based at least in part on a set of conditions, the ticket defining a job to be performed on the computing system;
create, by a master, the ticket and storing the ticket in the ticket database;
get, by a worker, the ticket from the master, performing the job defined by the ticket, and requesting the master to update the ticket with a status of the ticket; and
request, by a supervisor, the master to find a stale ticket, and, if found, to request the worker to abort performance of the job defined by the stale ticket.

### Claim 21 (depends on 20)

The at least one tangible machine-readable medium of claim 20, wherein the plurality of instructions that in response to being executed by the processor in the computing system cause the processor to:
determine, by the supervisor, a maximum number of retries for the stale ticket; and
if the number of retries of the stale ticket is more than the maximum number of retries, request, by the supervisor, the master to update the ticket to reflect a status of aborted.

### Claim 22 (depends on 21)

The at least one tangible machine-readable medium of claim 21, wherein the plurality of instructions that in response to being executed by the processor in the computing system cause the processor to:
determine, by the supervisor, the maximum number of retries for the stale ticket; and
if the number of retries of the stale ticket is not more than the maximum number of retries, request, by the supervisor, the master to update the ticket to a status of failed and to reset the failed stale ticket.

### Claim 23 (depends on 22)

The at least one tangible machine-readable medium of claim 22, wherein instructions to reset the failed stale ticket comprise instructions to request the master to get the failed stale ticket from the ticket database and update the status of the failed stale ticket to new.

### Claim 24 (depends on 23)

The at least one tangible machine-readable medium of claim 23, wherein the plurality of instructions that in response to being executed by the processor in the computing system cause the processor to:
check, by the supervisor, the status of the ticket being worked on by the worker and request the master to update the status of the ticket.

### Claim 25 (depends on 20)

The at least one tangible machine-readable medium of claim 20, wherein the plurality of instructions that in response to being executed by the processor in the computing system cause the processor to:
get, by the scheduler, the set of conditions from one or more applications being executed by the computing system.

### Claim 26 (depends on 20)

The at least one tangible machine-readable medium of claim 20, wherein the plurality of instructions that in response to being executed by the processor in the computing system cause the processor to:
determine, by the master, staleness of the ticket by analyzing a time threshold for a type of job to be performed according to the ticket.
