18402400. DISTRIBUTED WORKLOAD REASSIGNMENT FOLLOWING COMMUNICATION FAILURE simplified abstract (Microsoft Technology Licensing, LLC)
Contents
- 1 DISTRIBUTED WORKLOAD REASSIGNMENT FOLLOWING COMMUNICATION FAILURE
- 1.1 Organization Name
- 1.2 Inventor(s)
- 1.3 DISTRIBUTED WORKLOAD REASSIGNMENT FOLLOWING COMMUNICATION FAILURE - A simplified explanation of the abstract
- 1.4 Simplified Explanation
- 1.5 Potential Applications
- 1.6 Problems Solved
- 1.7 Benefits
- 1.8 Potential Commercial Applications
- 1.9 Possible Prior Art
- 1.10 Original Abstract Submitted
DISTRIBUTED WORKLOAD REASSIGNMENT FOLLOWING COMMUNICATION FAILURE
Organization Name
Microsoft Technology Licensing, LLC
Inventor(s)
David Kruse of Kirkland WA (US)
Vladimir Petter of Bellevue WA (US)
Lokesh Srinivas Koppolu of Redmond WA (US)
DISTRIBUTED WORKLOAD REASSIGNMENT FOLLOWING COMMUNICATION FAILURE - A simplified explanation of the abstract
This abstract first appeared for US patent application 18402400 titled 'DISTRIBUTED WORKLOAD REASSIGNMENT FOLLOWING COMMUNICATION FAILURE
Simplified Explanation
The patent application abstract describes a system and method for identifying situations where a workload has been reassigned to a new node during a failure between nodes. It involves using a generation identifier to track the assignment of workloads to nodes and ensure proper processing.
- The system employs a generation identifier to track the assignment of workloads to nodes.
- A master node assigns a workload to a worker node, which sends a request to access target data with the associated generation identifier.
- In case of a failure between nodes, the master node reassigns the workload to another worker node with a different generation identifier.
- The old worker node receives an indication that the workload has been reassigned and stops processing it.
Potential Applications
This technology can be applied in distributed computing systems, cloud computing environments, and data storage systems where workload reassignment during node failures is crucial.
Problems Solved
1. Efficient workload management during node failures. 2. Ensuring data integrity and continuity of processing in distributed systems.
Benefits
1. Improved system reliability and fault tolerance. 2. Seamless workload reassignment without data loss. 3. Enhanced performance and resource utilization in distributed environments.
Potential Commercial Applications
Optimizing cloud computing services, enhancing data storage systems, and improving the scalability of distributed applications.
Possible Prior Art
Prior art may include similar systems and methods for workload reassignment and fault tolerance in distributed computing environments.
Unanswered Questions
How does this technology impact system scalability in large-scale distributed environments?
This technology can potentially improve system scalability by efficiently managing workload reassignment during node failures, ensuring continuous processing without disruptions.
What are the potential security implications of using generation identifiers in workload management?
The use of generation identifiers can enhance system security by ensuring proper workload assignment and tracking, but potential vulnerabilities related to identifier management and authentication need to be considered.
Original Abstract Submitted
A generation identifier is employed with various systems and methods in order to identify situations where a workload has been reassigned to a new node and where a workload is still being processed by an old node during a failure between nodes. A master node may assign a workload to a worker node. The worker node sends a request to access target data. The request may be associated with a generation identifier and workload identifier that identifies the node and workload. At some point, a failure occurs between the master node and worker node. The master node reassigns the workload to another worker node. The new worker node accesses the target data with a different generation identifier, indicating to the storage system that the workload has been reassigned. The old worker node receives an indication from the storage system that the workload has been reassigned and stops processing the workload.