IP Library › Granted Patent US 11,940,886
Granted Patent B2
US 11,940,886 · App. 17/579,058 · Granted Mar 26, 2024

Automatically predicting fail-over of message-oriented middleware systems

Inventors: Madhanamohana Reddy Gandluri (Andrapradesh, IN); Sheik Saleem (Hyderabad, IN); Bijan Kumar Mohanty (Austin, TX); Hung T. Dinh (Austin, TX)
Assignee: Dell Products L.P.
G06F11/203G06F2201/85
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,940,886
App. No.
17/579,058
Granted
Mar 26, 2024
Kind
B2
Abstract

Methods, apparatus, and processor-readable storage media for automatically predicting fail-over of message-oriented middleware systems are provided herein. An example computer-implemented method includes obtaining one or more message-oriented middleware parameter values for at least a portion of multiple message-oriented middleware systems; detecting one or more fail-over-related anomalies associated with at least one of the multiple message-oriented middleware systems by processing at least a portion of the one or more message-oriented middleware parameter values using one or more machine learning techniques; and automatically migrating, based at least in part on the one or more detected fail-over-related anomalies, at least a portion of data associated with the at least one message-oriented middleware system associated with the one or more detected fail-over-related anomalies to at least one of the other of the multiple message-oriented middleware systems.

Claims (40)

1. A computer-implemented method comprising:

obtaining one or more message-oriented middleware parameter values for at least a portion of multiple message-oriented middleware systems;

detecting one or more fail-over-related anomalies associated with at least one of the multiple message-oriented middleware systems by processing at least a portion of the one or more message-oriented middleware parameter values using one or more machine learning techniques, wherein detecting one or more fail-over-related anomalies comprises predicting at least one middleware outage associated with the at least one of the multiple message-oriented middleware systems based at least in part on (i) results of processing the at least a portion of the one or more message-oriented middleware parameter values using the one or more machine learning techniques and (ii) results of processing, using the one or more machine learning techniques, one or more additional values related to at least one infrastructure upon which at least a portion of the at least one of the multiple message-oriented middleware systems is hosted; and

automatically migrating, based at least in part on the one or more detected fail-over-related anomalies, at least a portion of a set of data associated with the at least one message-oriented middleware system associated with the one or more detected fail-over-related anomalies to at least one of the other of the multiple message-oriented middleware systems, wherein automatically migrating the at least a portion of the set of data comprises synchronizing one or more items of metadata from the at least one message-oriented middleware system associated with the one or more detected fail-over-related anomalies to the at least one of the other of the multiple message-oriented middleware systems, and wherein the one or more items of metadata comprise information indicating where to resume processing, in connection with the at least a portion of the set of data, subsequent to automatically migrating the at least a portion of the set of data to the at least one of the other of the multiple message-oriented middleware systems;

wherein the method is performed by at least one processing device comprising a processor coupled to a memory.

2. The computer-implemented method of claim 1 , wherein processing at least a portion of the one or more message-oriented middleware parameter values comprises processing at least a portion of the one or more message-oriented middleware parameter values using at least one isolation forest algorithm.

3. The computer-implemented method of claim 1 , further comprising:

processing historical values for the one or more message-oriented middleware parameter values.

4. The computer-implemented method of claim 3 , wherein detecting one or more fail-over-related anomalies associated with at least one of the multiple message-oriented middleware systems comprises comparing at least a portion of the one or more obtained message-oriented middleware parameter values to the processed historical values for the one or more message-oriented middleware parameter values.

5. The computer-implemented method of claim 1 , further comprising:

automatically identifying, subsequent to automatically migrating the at least a portion of the set of data, one or more issues related to a fail-over event of the at least one message-oriented middleware system associated with the one or more detected fail-over-related anomalies.

6. The computer-implemented method of claim 5 , further comprising:

training the one or more machine learning techniques using at least a portion of the one or more identified issues related to the fail-over event.

7. The computer-implemented method of claim 1 , wherein obtaining one or more message-oriented middleware parameter values comprises obtaining values pertaining to at least one of central processing unit utilization, memory utilization, storage utilization, input/output utilization, queue depth, channel agent information, and channel connection information.

8. A non-transitory processor-readable storage medium having stored therein program code of one or more software programs, wherein the program code when executed by at least one processing device causes the at least one processing device:

to obtain one or more message-oriented middleware parameter values for at least a portion of multiple message-oriented middleware systems;

to detect one or more fail-over-related anomalies associated with at least one of the multiple message-oriented middleware systems by processing at least a portion of the one or more message-oriented middleware parameter values using one or more machine learning techniques, wherein detecting one or more fail-over-related anomalies comprises predicting at least one middleware outage associated with the at least one of the multiple message-oriented middleware systems based at least in part on (i) results of processing the at least a portion of the one or more message-oriented middleware parameter values using the one or more machine learning techniques and (ii) results of processing, using the one or more machine learning techniques, one or more additional values related to at least one infrastructure upon which at least a portion of the at least one of the multiple message-oriented middleware systems is hosted; and

to automatically migrate, based at least in part on the one or more detected fail-over-related anomalies, at least a portion of a set of data associated with the at least one message-oriented middleware system associated with the one or more detected fail-over-related anomalies to at least one of the other of the multiple message-oriented middleware systems, wherein automatically migrating the at least a portion of the set of data comprises synchronizing one or more items of metadata from the at least one message-oriented middleware system associated with the one or more detected fail-over-related anomalies to the at least one of the other of the multiple message-oriented middleware systems, and wherein the one or more items of metadata comprise information indicating where to resume processing, in connection with the at least a portion of the set of data, subsequent to automatically migrating the at least a portion of the set of data to the at least one of the other of the multiple message-oriented middleware systems.

9. The non-transitory processor-readable storage medium of claim 8 , wherein processing at least a portion of the one or more message-oriented middleware parameter values comprises processing at least a portion of the one or more message-oriented middleware parameter values using at least one isolation forest algorithm.

10. The non-transitory processor-readable storage medium of claim 8 , wherein the program code when executed by the at least one processing device causes the at least one processing device:

to process historical values for the one or more message-oriented middleware parameter values.

11. The non-transitory processor-readable storage medium of claim 10 , wherein detecting one or more fail-over-related anomalies associated with at least one of the multiple message-oriented middleware systems comprises comparing at least a portion of the one or more obtained message-oriented middleware parameter values to the processed historical values for the one or more message-oriented middleware parameter values.

12. The non-transitory processor-readable storage medium of claim 8 , wherein obtaining one or more message-oriented middleware parameter values comprises obtaining values pertaining to at least one of central processing unit utilization, memory utilization, storage utilization, input/output utilization, queue depth, channel agent information, and channel connection information.

13. The non-transitory processor-readable storage medium of claim 8 , wherein the program code when executed by the at least one processing device causes the at least one processing device:

to automatically identify, subsequent to automatically migrating the at least a portion of the set of data, one or more issues related to a fail-over event of the at least one message-oriented middleware system associated with the one or more detected fail-over-related anomalies.

14. The non-transitory processor-readable storage medium of claim 13 , wherein the program code when executed by the at least one processing device causes the at least one processing device:

to train the one or more machine learning techniques using at least a portion of the one or more identified issues related to the fail-over event.

15. An apparatus comprising:

at least one processing device comprising a processor coupled to a memory;

the at least one processing device being configured:

to obtain one or more message-oriented middleware parameter values for at least a portion of multiple message-oriented middleware systems;

detect one or more fail-over-related anomalies associated with at least one of the multiple message-oriented middleware systems by processing at least a portion of the one or more message-oriented middleware parameter values using one or more machine learning techniques, wherein detecting one or more fail-over-related anomalies comprises predicting at least one middleware outage associated with the at least one of the multiple message-oriented middleware systems based at least in part on (i) results of processing the at least a portion of the one or more message-oriented middleware parameter values using the one or more machine learning techniques and (ii) results of processing, using the one or more machine learning techniques, one or more additional values related to at least one infrastructure upon which at least a portion of the at least one of the multiple message-oriented middleware systems is hosted; and

to automatically migrate, based at least in part on the one or more detected fail-over-related anomalies, at least a portion of a set of data associated with the at least one message-oriented middleware system associated with the one or more detected fail-over-related anomalies to at least one of the other of the multiple message-oriented middleware systems, wherein automatically migrating the at least a portion of the set of data comprises synchronizing one or more items of metadata from the at least one message-oriented middleware system associated with the one or more detected fail-over-related anomalies to the at least one of the other of the multiple message-oriented middleware systems, and wherein the one or more items of metadata comprise information indicating where to resume processing, in connection with the at least a portion of the set of data, subsequent to automatically migrating the at least a portion of the set of data to the at least one of the other of the multiple message-oriented middleware systems.

16. The apparatus of claim 15 , wherein processing at least a portion of the one or more message-oriented middleware parameter values comprises processing at least a portion of the one or more message-oriented middleware parameter values using at least one isolation forest algorithm.

17. The apparatus of claim 15 , wherein the at least one processing device is further configured:

to process historical values for the one or more message-oriented middleware parameter values.

18. The apparatus of claim 17 , wherein detecting one or more fail-over-related anomalies associated with at least one of the multiple message-oriented middleware systems comprises comparing at least a portion of the one or more obtained message-oriented middleware parameter values to the processed historical values for the one or more message-oriented middleware parameter values.

19. The apparatus of claim 15 , wherein obtaining one or more message-oriented middleware parameter values comprises obtaining values pertaining to at least one of central processing unit utilization, memory utilization, storage utilization, input/output utilization, queue depth, channel agent information, and channel connection information.

20. The apparatus of claim 15 , wherein the at least one processing device is further configured:

to automatically identify, subsequent to automatically migrating the at least a portion of the set of data, one or more issues related to a fail-over event of the at least one message-oriented middleware system associated with the one or more detected fail-over-related anomalies.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 19, 2022
From: GANDLURI, MADHANAMOHANA REDDY; SALEEM, SHEIK; MOHANTY, BIJAN KUMAR; DINH, HUNG T.
To: DELL PRODUCTS L.P.
Reel/Frame 058697/0282 →
Continuity (1)
Related Publication 20230229574A1 · Jul 20, 2023