Balanced input/output task management for use in multiprocessor transaction processing system

• US 5,924,097 A
• Filed: 12/23/1997
• Issued: 07/13/1999
• Est. Priority Date: 12/23/1997
• Status: Expired due to Term

• Current Assignee: Unisys Corporation
• Original Assignee: Unisys Corporation
• Inventors: Hill, Michael James, Nowatzki, Thomas L., Cooper, Thomas Pearson, Konrad, Dennis Richard
• Primary Examiner(s): Kulik, Paul V.
• Assistant Examiner(s): HOMERE, JEAN RAYMOND
• Application Number:
  US08/996,761
• Time in Patent Office: 567 Days
• Field of Search: 707/10, 707/8, 707/2, 707/201, 395/675, 395/200.43, 395/200.38
• US Class Current: 707/703
• CPC Class Codes: G06F 2209/5016 Session
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals
• CPC Class Codes: G06F 9/505 considering the load
• CPC Class Codes: Y10S 707/922 Communications
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users

Abstract

A system and method for balancing database transaction request distribution between various hosts in a multiprocessor transaction processing system is provided. The transaction processing system includes a database and multiple host processors each coupled to at least one database transaction request unit. Database transaction requests sent from the host processors are collectively entered into a commonly-accessible load balancing queue. Each database transaction request is accompanied by a source identifier that identifies the database transaction request unit which initiated the corresponding database transaction request. The queued database transaction requests from the load balancing queue are processed by currently-available host processors, regardless of which host processor initiated the database transaction request. A transaction request acknowledgment for each of the processed transaction requests is created and transferred to the database transaction request unit identified by their respective source identifiers.

Claims

1. A method for balancing database transaction request distribution in a transaction processing system having a database, and a plurality of host processors each coupled to one or more database transaction request units, the method comprising:

collectively entering database transaction requests sent from each of the host processors into a commonly-accessible load balancing queue, wherein each database transaction request is accompanied by a source identifier identifying the database transaction request unit that initiated the corresponding database transaction request;

processing queued database transaction requests from the commonly-accessible load balancing queue by available ones of the host processors;

creating a transaction request acknowledgment for each of the queued database transaction requests which are processed; and

transferring the transaction request acknowledgments to the database transaction request unit identified by their respective source identifiers.

2. The method as in claim 1, further comprising processing related database transaction requests using the host processor which processed a first of the related database transaction requests.

3. The method as in claim 2, wherein processing related database transaction requests comprises:

including a host affinity identifier, which identifies the host processor which processed the first of the related database transaction requests, with the transaction request acknowledgment;

providing the host affinity identifier with a subsequently transmitted database transaction request from the host processor which issued the first of the related database transaction requests;

entering the subsequently transmitted database transaction request on the load balancing queue; and

assigning the subsequently transmitted database transaction request to the host processor identified by the host affinity identifier when the host processor identified by the host affinity identifier is available.

4. The method as in claim 3, further comprising:

retaining the subsequently transmitted database transaction request on the load balancing queue for a predetermined time; and

allowing the host processor identified by the host affinity identifier to process the subsequently transmitted database transaction request if the host processor identified by the host affinity identifier is available within the predetermined time.

5. The method as in claim 3, further comprising processing the subsequently transmitted database transaction request by any of the host processors which is available when the host processor identified by the host affinity identifier is not available.

6. The method as in claim 3, wherein the related database transaction requests comprise the database transaction requests associated with a common terminal session.

7. The method as in claim 1, wherein collectively entering database transaction requests comprises entering the database transaction requests from all of the database transaction request units onto the commonly-accessible load balancing queue in a first-in-first-out fashion.

8. The method as in claim 1, wherein collectively entering database transaction requests comprises entering the database transaction requests from all of the database transaction request units onto a non-volatile, centralized first-in-first-out storage device accessible to each of the host processors.

9. The method as in claim 1, wherein creating a transaction request acknowledgment comprises generating a completion status code indicating whether the database transaction was successful.

10. The method as in claim 1, further comprising queuing the transaction request acknowledgment in one of a plurality of output queues corresponding to a communication software module that initiated the database transaction request, wherein the communication software modules each interface one or more of the database transaction request units the corresponding output queue.

11. The method as in claim 10, wherein transferring the transaction request acknowledgments comprises providing an address to the output queues using the source identifier corresponding to the database transaction request unit that initiated the database transaction request.

12. The method as in claim 11, wherein providing an address comprises locating the address of a particular one of the output queues in a memory structure addressable via the source identifiers.

13. The method as in claim 1, wherein processing queued database transaction requests comprises;

removing the database transaction request next in the load balancing queue; and

updating the database in accordance with the database transaction request.

14. The method as in claim 1, wherein processing queued database transaction requests comprises processing the queued database transaction requests using a different one of the host processors than the host processor that issued the queued database transaction request.

15. The method as in claim 1, wherein processing queued database transaction requests by available ones of the host processors further comprises examining the queued database transaction requests on the load balancing queue by a particular one of the host processors upon its completing a current processing task.

16. The method as in claim 1, further comprising designating selected ones of the host processors to execute functionally-related ones of the queued database transaction requests.

17. The method as in claim 1, further comprising transferring the source identifier concurrently with each of the database transaction requests sent from a particular one of the host processors, wherein the source identifier comprises a digital code corresponding to the transaction request unit issuing the database transaction request.

18. A multiprocessor system for managing database transaction requests from a plurality of input/output (I/O) devices, comprising:

a plurality of host processing units each coupled to at least one of the plurality of I/O devices to receive the database transaction requests;

a task management system coupled to each of the plurality of host processing units to process the database transaction requests from the plurality of host processing units, the task management system comprising;

a load balancing queue coupled to each of the host processing units to collectively queue the database transaction requests from each of the plurality of host processing units;

a plurality of input message queues, each coupled to a respective one of the host processing units and to the load balancing queue; and

wherein an available one of the host processing units transfers a next available one of the database transaction requests from the load balancing queue to its corresponding input message queue for processing by the available host processing unit.

19. The multiprocessor system as in claim 18, wherein the load balancing queue comprises a non-volatile memory queue.

20. The multiprocessor system as in claim 18, wherein the plurality of input message queues each comprise a non-volatile memory queue.

21. The multiprocessor system as in claim 18, wherein the load balancing queue comprises a plurality of storage entry fields to receive the database transaction request and a source indicator which identifies the terminal session that provided the database transaction request.

22. The multiprocessor system as in claim 21, wherein the storage entry field comprises a first field to store a pointer to the database transaction request and a second field to store the source indicator.

23. The multiprocessor system as in claim 18, further comprising a plurality of output message queues, one for each of the plurality of host processing units, to queue transaction acknowledgment messages destined for the I/O device which initiated the database transaction request as identified by a source indicator.

24. The multiprocessor system as in claim 23, further comprising a source indicator memory structure coupled to each of the output message queues to store pointers to the output message queues, and wherein the source indicator memory structure is addressable via the source identifiers provided within the transaction acknowledgment messages.