Overload management of a transaction processing server

Patent metadata

Field	Value
Publication number	US-2020092395-A1
Application number	US-201816135186-A
Country	US
Kind code	A1
Filing date	Sep 19, 2018
Priority date	Sep 19, 2018
Publication date	Mar 19, 2020
Grant date	—

Abstract

Method and system are provided for overload management of a transaction processing server. The method includes detecting a high load state of a server based on a count of current transactions being processed in the server and activating prioritization of incoming client requests to the server based on prioritization of types of transaction request that reduce the load on the server. The prioritization may include: inspecting incoming client requests to determine their type and allocate a priority level; and forwarding a higher level prioritized request for processing ahead of a lower level priority request.

First claim

What is claimed is:

1 . A computer-implemented method for overload management of a transaction processing server, comprising:
detecting a high load state of a server based on a count of current transactions being processed in the server; activating prioritization of incoming client requests to the server based on prioritization of types of transaction request that reduce the load on the server, including:
inspecting incoming client requests to determine their type and allocating a priority level; and
forwarding a higher level prioritized request for processing ahead of a lower level priority request.

2 . The method as claimed in claim 1 , including prioritizing a top priority type of transaction request that terminates a transaction and thereby reduces the load on the server.

3 . The method as claimed in claim 2 , including prioritizing within the top priority type transaction requests that terminate a transaction successfully with committed or backed out recoverable updates, followed by transaction requests that terminate a transaction abnormally in-flight.

4 . The method as claimed in claim 2 , including prioritizing a bottom priority type of transaction request that creates a new transaction for a new work request.

5 . The method as claimed in claim 4 , including deferring a bottom priority type of transaction until an overload condition is relieved.

6 . The method as claimed in claim 1 , including determining the following types of transaction and prioritizing them with prioritization levels as follows:
a first type of transaction request that requests termination of a transaction and commit or backout recoverable updates; a second type of transaction request that requests termination of an in-flight transaction abnormally; a third type of transaction request that requests continuation of an existing transaction with a further work request; and a fourth type of transaction request that requests creation of a new transaction for a new work request.

7 . The method as claimed in claim 1 , wherein detecting a high load state includes:
counting current transactions at the server; and determining whether a number of current transactions is above a defined threshold count.

8 . The method as claimed in claim 7 , wherein the defined threshold is below a maximum concurrent transaction limit of the server.

9 . The method as claimed in claim 1 , including detecting that a high load state has passed and de-activating the prioritization of incoming requests.

10 . The method as claimed in claim 1 , including activating prioritization of a subset of requests in a queue of incoming requests that are closest to a top of the queue.

11 . A system for overload management of a transaction processing server, comprising:
a processor and a memory configured to provide computer program instructions to the processor to execute a function of components; a server capacity monitor for detecting a high load state of a server based on a count of current transactions being processed in the server; a request prioritization system for activating prioritization of incoming client requests to the server based on prioritization of types of transaction request that reduce the load on the server, including:
a client request inspection component for inspecting incoming client requests to determine their type and allocating a priority level; and
a request forwarding component for forwarding a higher level prioritized request for processing ahead of a lower level priority request.

12 . The system as claimed in claim 11 , including a prioritization rules component for prioritizing a top priority type of transaction request that terminates a transaction and thereby reduces the load on the server.

13 . The system as claimed in claim 12 , wherein the prioritization rules component includes prioritizing within the top priority type transaction requests that terminate a transaction successfully with committed or backed out recoverable updates, followed by transaction requests that terminate a transaction abnormally in-flight.

14 . The system as claimed in claim 12 , wherein the prioritization rules component includes prioritizing a bottom priority type of transaction request that creates a new transaction for a new work request.

15 . The system as claimed in claim 12 , wherein the prioritization rules component determines the following types of transaction and prioritizes them with prioritization levels as follows:
a first type of transaction request that requests termination of a transaction and commit or backout recoverable updates; a second type of transaction request that requests termination of an in-flight transaction abnormally; a third type of transaction request that requests continuation of an existing transaction with a further work request; and a fourth type of transaction request that requests creation of a new transaction for a new work request.

16 . The system as claimed in claim 11 , wherein the server capacity monitor for detecting a high load state includes:
a transaction count component for counting current transactions at the server; and a threshold component for determining whether a number of current transactions is above a defined threshold count.

17 . The system as claimed in claim 16 , wherein the server capacity monitor for detecting a high load state includes:
a prioritization activation component for activating a prioritization of incoming transaction requests when a high load state is detected; and a prioritization de-activation component for de-activating a prioritization of incoming transaction requests when the high load state is no longer detected.

18 . The system as claimed in claim 17 , wherein the threshold component includes a threshold configuration component for configuring a defined threshold below a maximum concurrent transaction limit of the server.

19 . The system as claimed in claim 11 , including a deferring component for deferring one or more bottom priority types of transaction until an overload condition is relieved.

20 . A computer program product for overload management of a transaction processing server, the computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a processor to cause the processor to:
detect a high load state of a server based on a count of current transactions being processed in the server; activate prioritization of incoming client requests in to the server based on prioritization of types of transaction request that reduce the load on the server, including:
inspect incoming client requests to determine their type and allocate a priority level; and
forward a higher level prioritized request for processing ahead of a lower level priority request.

Assignees

• IBM

Inventors

• Horn Julian
• Hollingshead Alan
• Brooks Michael D
• Wakelin Philip I

Classifications

• H04L67/1008

  based on parameters of servers, e.g. available memory or workload (monitoring of computer activity G06F11/30) · CPC title

• G06F9/5083

  Techniques for rebalancing the load in a distributed system · CPC title

• G06F2209/5022

  Workload threshold · CPC title

• H04L67/1012

  based on compliance of requirements or conditions with available server resources · CPC title

• G06F9/466

  Transaction processing · CPC title