Eliminating data traffic redirection in scalable clusters

Patent metadata

Field	Value
Publication number	US-10742559-B2
Application number	US-201815967423-A
Country	US
Kind code	B2
Filing date	Apr 30, 2018
Priority date	Apr 24, 2014
Publication date	Aug 11, 2020
Grant date	Aug 11, 2020

Abstract

Provided are methods and systems for eliminating a redirection of data traffic in a cluster. An example method may include receiving, by one or more nodes of the cluster, a data packet associated with a service session. The method may include determining, by the node, that the data packet is directed to a further node in the cluster. The method may further include, in response to the determination, acquiring, by the node, a session context associated with the service session. Acquiring the session context may include sending, by the node, a request for the session context to the further node and receiving the session context from the further node. The method may further include processing, by the one or more nodes, the data packet based on the session context.

First claim

What is claimed is:

1. A system for eliminating a redirection of data traffic, the system comprising:
a cluster comprising one or more nodes, the one or more nodes being configured to:
receive, from a forwarding node, a data packet associated with a service session;
determine that the one or more nodes is not assigned to process the service session, the service session including an existing service session processed by a further node in the cluster; and

in response to the determination:
acquire a session context associated with the service session from a separate node acting as a control plane, wherein a first time spent by the one or more nodes for the acquiring the session context from the control plane is less than a second time needed by the one or more nodes to redirect the data packet to the further node; and
process the data packet based on the session context without forwarding the data packet to the further node; and

wherein the control plane:
obtains a plurality of session contexts of service sessions;
selects one or more session contexts from the plurality of session contexts based on priorities of the service sessions, wherein the priorities of the service sessions are based on latency requirements for the service sessions; and
after the selecting the one or more session contexts, synchronizes the one or more session contexts from the plurality of session contexts with the session context.

2. The system of claim 1 , wherein the one or more nodes are further configured to store the session context in a dedicated memory.

3. The system of claim 2 , wherein the obtaining the plurality of session contexts is performed by acquiring the session context from the one or more nodes.

4. The system of claim 3 , wherein the one or more nodes are configured to acquire a further session context by sending a request for the further session context to the control plane.

5. The system of claim 3 , wherein the session context is stored in the one or more nodes in the cluster.

6. The system of claim 1 , wherein the one or more nodes are further configured to:
receive a further packet of a further service session;
generate a further session context associated with the further service session; and
send the further session context to one or more further nodes of the cluster.

7. The system of claim 1 , wherein the one or more nodes are configured to:
send a request for the session context to the further node; and
receive the session context from the further node.

8. A method for eliminating a redirection of data traffic in a cluster, the method comprising:
receiving, by one or more nodes of the cluster, from a forwarding node, a data packet associated with a service session;
determining, by the one or more nodes, that the one or more nodes is not assigned to process the service session, the service session including an existing service session processed by a further node in the cluster;
in response to the determination:
acquiring, by the one or more nodes, a session context associated with the service session from a separate node acting as a control plane, wherein a first time spent by the one or more nodes for the acquiring the session context from the control plane is less than a second time needed by the one or more nodes to redirect the data packet to the further node; and
processing, by the one or more nodes, the data packet based on the session context without forwarding the data packet to the further node;

obtaining, by the control plane, a plurality of session contexts of service sessions;
selecting, by the control plane, one or more session contexts from the plurality of session contexts based on priorities of the service sessions, wherein the priorities of the service sessions are based on latency requirements for the service sessions; and
after the selecting the one or more session contexts, synchronizing, by the control plane, the one or more session contexts from the plurality of session contexts with the session context.

9. The method of claim 8 , further comprising storing, by the one or more nodes, the session context in a dedicated memory.

10. The method of claim 9 , wherein the obtaining, by the control plane, the plurality of session contexts is performed by acquiring the session context from the one or more nodes.

11. The method of claim 10 , further comprising acquiring, by the one or more nodes, a further session context by sending a request for the further session context to the control plane.

12. The method of claim 10 ,
wherein the session context is stored in the one or more nodes of the cluster.

13. The method of claim 8 , wherein the acquiring the session context includes:
sending, by the one or more nodes, a request for the session context to the further node; and
receiving, by the one or more nodes, the session context from the further node.

14. The method of claim 8 , further comprising:
receiving, by the one or more nodes, a further packet of a further service session;
generating, by the one or more nodes, a further session context associated with the further service session; and
sending, by the one or more nodes, the further session context to one or more further nodes of the cluster.

15. A non-transitory computer-readable medium having embodied thereon a program, the program providing instructions for a method for eliminating a redirection of data traffic in a cluster, the method comprising:
receiving, by one or more nodes of the cluster, from a forwarding node, a data packet associated with a service session;
determining, by the one or more nodes, that the one or more nodes is not assigned to process the service session, the service session including an existing service session processed by a further node in the cluster;
in response to the determination:
acquiring, by the one or more nodes, a session context associated with the service session from a separate node acting as a control plane, wherein a first time spent by the one or more nodes for the acquiring the session context from the control plane is less than a second time needed by the one or more nodes to redirect the data packet to the further node; and
processing, by the one or more nodes, the data packet based on the session context without forwarding the data packet to the further node;

obtaining, by the control plane, a plurality of session contexts of service sessions;
selecting, by the control plane, one or more session contexts from the plurality of session contexts based on priorities of the service sessions, wherein the priorities of the service sessions are based on latency requirements for the service sessions; and
after the selecting the one or more session contexts, synchronizing, by the control plane, the one or more session contexts from the plurality of session contexts with the session context.

Assignees

• A10 Networks Inc

Inventors

• Kamat Gurudeep
• Sankar Swaminathan
• Dosovitsky Gennady
• Jalan Rajkumar

Classifications

• H04L67/563

  Data redirection of data network streams · CPC title

• H04L67/01

  Protocols · CPC title

• H04L45/46

  Cluster building · CPC title

• H04L45/28

  using route fault recovery · CPC title

• H04L67/10

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title