Search

US-12625742-B2 - Method and system for managing loads across multiple geographically dispersed data clusters

US12625742B2US 12625742 B2US12625742 B2US 12625742B2US-12625742-B2

Abstract

A method for managing loads in data clusters includes: identifying, by a first load management module (LMM) of a first data cluster, a load performance decline event associated with the first data cluster; in response to identifying the load performance decline event: selecting a second LMM associated with a second data cluster, wherein the second LMM is associated with an authenticated connection with the first LMM; sending requests to the second LMM using a secure string identifier associated with the authenticated connection, wherein the LMM services the requests using the second data cluster.

Inventors

  • Parminder Singh Sethi
  • Anay Kishore

Assignees

  • DELL PRODUCTS L.P.

Dates

Publication Date
20260512
Application Date
20230421

Claims (16)

  1. 1 . A method for managing loads in data clusters, comprising: identifying, by a first load management module (LMM) of a first data cluster, a load performance decline event associated with the first data cluster; in response to identifying the load performance decline event: making a first determination that there are no active authenticated connections between the first LMM of the first data cluster and any other LMM executing on any other data cluster; in response to the first determination: accessing, from a database of the first data cluster, LMM information, wherein the LMM information comprises configuration parameters and connection bandwidths associated with other LMMs executing in other data clusters; identifying a second LMM of a second data cluster using the LMM information, wherein identifying the second LMM comprises selecting the second LMM whose configuration parameters match a similarity threshold relative to configuration parameters of the first LMM; converting current system time to coordinated universal time (UTC); generating a secure string identifier using a current UTC time and a secure string parameter; encrypting the secure string identifier and a static alphanumeric key; establishing an authenticated connection using the encrypted secure string identifier and the static alphanumeric key; sending requests to the second LMM over the authenticated connection using the secure string identifier, wherein the second LMM services the requests using the second data cluster; making a second determination that load performance of the first data cluster is restored; in response to the second determination: setting the authenticated connection to standby; and servicing second requests using the first data cluster.
  2. 2 . The method of claim 1 , wherein the secure string identifier is associated with an expiration timeframe specified by the secure string parameters.
  3. 3 . The method of claim 2 , wherein the method further comprises: after setting the authenticated connection to standby: identifying the expiration of the secure string identifier based on the expiration timeframe; and terminating the authenticated connection.
  4. 4 . The method of claim 1 , wherein the load performance decline event comprises determining current data cluster performance metrics are below a baseline.
  5. 5 . The method of claim 1 , wherein the load performance decline event comprises identifying an occurrence of a predicted data cluster load performance decline window.
  6. 6 . A method for managing loads in data clusters, comprising: identifying, by a first load management module (LMM) of a first data cluster, a load performance decline event associated with the first data cluster; in response to identifying the load performance decline event: selecting a second LMM of a second data cluster, wherein the second LMM is associated with an authenticated connection with the first LMM, wherein selecting the second LMM of the second data cluster comprises: making a first determination that there are no active authenticated connections between the first LMM of the first data cluster and any other LMM executing on any other data cluster; in response to the first determination: accessing, from a database of the first data cluster, LMM information, wherein the LMM information comprises configuration parameters and connection bandwidths associated with other LMMs executing in other data clusters; identifying the second LMM using the LMM information, wherein identifying the second LMM comprises selecting the second LMM whose configuration parameters match a similarity threshold relative to configuration parameters of the first LMM; converting current system time to coordinated universal time (UTC); generating a secure string identifier using a current UTC time and secure string parameters; encrypting the secure string identifier and a static alphanumeric key; establishing the authenticated connection using the encrypted secure string identifier and the static alphanumeric key; sending requests to the second LMM using a secure string identifier associated with the authenticated connection, wherein the second LMM services the requests using the second data cluster; making a second determination that load performance of the first data cluster is restored; in response to the second determination: setting the authenticated connection to standby; and servicing second requests using the first data cluster.
  7. 7 . The method of claim 6 , wherein the secure string identifier is associated with an expiration timeframe specified by the secure string parameters.
  8. 8 . The method of claim 7 , wherein the method further comprises: after sending the requests to the second LMM: identifying the expiration of the secure string identifier based on the expiration timeframe; and terminating the authenticated connection.
  9. 9 . The method of claim 6 , wherein the load performance decline event comprises identifying current data cluster performance metrics are below a baseline.
  10. 10 . The method of claim 6 , wherein the load performance decline event comprises identifying an occurrence of a predicted data cluster load performance decline window.
  11. 11 . The method of claim 10 , wherein the predicted data cluster load performance decline window is generated using: a prediction model; current data cluster performance metrics; current request information; and baseline data.
  12. 12 . The method of claim 11 , wherein the predicted data cluster load performance decline window specifies a predicted future timeframe that the performance metrics will be below baseline data.
  13. 13 . A non-transitory computer readable medium comprising computer readable program code, which when executed by a computer processor enables the computer processor to perform a method for managing loads in data clusters, the method comprising: identifying, by a first load management module (LMM) of a first data cluster, a load performance decline event associated with the first data cluster; in response to identifying the load performance decline event: selecting a second LMM associated with a second data cluster, wherein the second LMM is associated with an authenticated connection with the first LMM, wherein selecting the second LMM of the second data cluster comprises: making a first determination that there are no active authenticated connections between the first LMM of the first data cluster and any other LMM executing on any other data cluster; in response to the first determination: accessing, from a database of the first data cluster, LMM information, wherein the LMM information comprises configuration parameters and connection bandwidths associated with other LMMs executing in other data clusters; identifying the second LMM using the LMM information, wherein identifying the second LMM comprises selecting the second LMM whose configuration parameters match a similarity threshold relative to configuration parameters of the first LMM; converting current system time to coordinated universal time (UTC); generating a secure string identifier using a current UTC time and secure string parameters; encrypting the secure string identifier and a static alphanumeric key; establishing the authenticated connection using the encrypted secure string identifier and the static alphanumeric key; sending requests to the second LMM using a secure string identifier associated with the authenticated connection, wherein the second LMM services the requests using the second data cluster; making a second determination that load performance of the first data cluster is restored; in response to the second determination: setting the authenticated connection to standby; and servicing second requests using the first data cluster.
  14. 14 . The non-transitory computer readable medium of claim 13 , wherein the secure string identifier is associated with an expiration timeframe specified by the secure string parameters.
  15. 15 . The non-transitory computer readable medium of claim 14 , wherein the method further comprises: after sending the requests to the second LMM: identifying the expiration of the secure string identifier based on the expiration timeframe; and terminating the authenticated connection.
  16. 16 . The non-transitory computer readable medium of claim 13 , wherein the load performance decline event comprises identifying current data cluster performance information below a baseline.

Description

BACKGROUND Computing devices may provide services. To provide the services, the computing devices may include hardware components and software components. The software components may store information usable to provide the services using the hardware components. That information may be transmitted to other computing devices to perform other services. BRIEF DESCRIPTION OF DRAWINGS Certain embodiments of the invention will be described with reference to the accompanying drawings. However, the accompanying drawings illustrate only certain aspects or implementations of the invention by way of example, and are not meant to limit the scope of the claims. FIG. 1 shows a diagram of a system in accordance with one or more embodiments of the invention. FIG. 2 shows a diagram of a data cluster in accordance with one or more embodiments of the invention. FIG. 3 shows a diagram of a load management module in accordance with one or more embodiments of the invention. FIG. 4 shows a diagram of a security module in accordance with one or more embodiments of the invention. FIG. 5.1 shows a flowchart of a method for performing load management services in accordance with one or more embodiments of the invention. FIG. 5.2 shows a flowchart of a method for establishing an authenticated connection in accordance with one or more embodiments of the invention. FIG. 6.1 shows a flowchart of a method for establishing a secure session in accordance with one or more embodiments of the invention. FIG. 6.2 shows a flowchart of a method for verifying a request in accordance with one or more embodiments disclosed herein. FIG. 7 shows a diagram of a computing device in accordance with one or more embodiments of the invention. DETAILED DESCRIPTION Specific embodiments of the invention will now be described in detail with reference to the accompanying figures. In the following detailed description of the embodiments of the invention, numerous specific details are set forth in order to provide a more thorough understanding of one or more embodiments of the invention. However, it will be apparent to one of ordinary skill in the art that the one or more embodiments of the invention may be practiced without these specific details. In other instances, well-known features have not been described in detail to avoid unnecessarily complicating the description. In the following description of the figures, any component described with regard to a figure, in various embodiments of the invention, may be equivalent to one or more like-named components described with regard to any other figure. For brevity, descriptions of these components will not be repeated with regard to each figure. Thus, each and every embodiment of the components of each figure is incorporated by reference and assumed to be optionally present within every other figure having one or more like-named components. Additionally, in accordance with various embodiments of the invention, any description of the components of a figure is to be interpreted as an optional embodiment, which may be implemented in addition to, in conjunction with, or in place of the embodiments described with regard to a corresponding like-named component in any other figure. Throughout this application, elements of figures may be labeled as A to N. As used herein, the aforementioned labeling means that the element may include any number of items, and does not require that the element include the same number of elements as any other item labeled as A to N. For example, a data structure may include a first element labeled as A and a second element labeled as N. This labeling convention means that the data structure may include any number of the elements. A second data structure, also labeled as A to N, may also include any number of elements. The number of elements of the first data structure, and the number of elements of the second data structure, may be the same or different. Throughout the application, ordinal numbers (e.g., first, second, third, etc.) may be used as an adjective for an element (i.e., any noun in the application). The use of ordinal numbers is not to imply or create any particular ordering of the elements nor to limit any element to being only a single element unless expressly disclosed, such as by the use of the terms “before”, “after”, “single”, and other such terminology. Rather, the use of ordinal numbers is to distinguish between the elements. By way of an example, a first element is distinct from a second element, and the first element may encompass more than one element and succeed (or precede) the second element in an ordering of elements. As used herein, the phrase operatively connected, or operative connection, means that there exists between elements/components/devices a direct or indirect connection that allows the elements to interact with one another in some way. For example, the phrase ‘operatively connected’ may refer to any direct connection (e.g., wired directly between two devic