17949995. AN APPROACH TO GRACEFULLY RESOLVE RETRY STORMS simplified abstract (International Business Machines Corporation)
Contents
- 1 AN APPROACH TO GRACEFULLY RESOLVE RETRY STORMS
- 1.1 Organization Name
- 1.2 Inventor(s)
- 1.3 AN APPROACH TO GRACEFULLY RESOLVE RETRY STORMS - 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
AN APPROACH TO GRACEFULLY RESOLVE RETRY STORMS
Organization Name
International Business Machines Corporation
Inventor(s)
AN APPROACH TO GRACEFULLY RESOLVE RETRY STORMS - A simplified explanation of the abstract
This abstract first appeared for US patent application 17949995 titled 'AN APPROACH TO GRACEFULLY RESOLVE RETRY STORMS
Simplified Explanation
The method described in the abstract involves setting a retry locker parameter to control retries of service requests in a service mesh network. When a pod in the call chain is unavailable, the retry locker parameter is unlocked for the previous pod to allow a retry to the unavailable pod. If the previous pod reaches a retry limit, the retry locker parameter is unlocked for all pods in the call chain and a service termination message is sent to the requester.
- Setting retry locker parameter to locked state for each pod in the call chain
- Unlocking retry locker parameter for previous pod just before an unavailable pod
- Sending service termination message if previous pod reaches retry limit
Potential Applications
This technology could be applied in various distributed systems where service requests need to be managed and retried efficiently.
Problems Solved
1. Efficient management of retries in a service mesh network 2. Handling unavailable pods in a call chain without impacting the overall service request
Benefits
1. Improved reliability and resilience in service mesh networks 2. Reduced impact of unavailable pods on service performance
Potential Commercial Applications
Optimizing service request handling in cloud computing environments
Possible Prior Art
Prior art may include similar retry mechanisms in distributed systems or network protocols.
Unanswered Questions
How does this method handle retries for different types of service requests?
The method does not specify if it can differentiate between different types of service requests and adjust retry behavior accordingly.
What impact does unlocking the retry locker parameter have on overall network performance?
The abstract does not provide information on how unlocking the retry locker parameter for multiple pods in the call chain may affect the performance of the network as a whole.
Original Abstract Submitted
A method includes, in response to receiving an incoming service request and establishing a call chain of pods of a service mesh network, setting a retry locker parameter to a locked state for each pod in the call chain. A locked retry locker parameter prevents the pod from initiating retries of a service request. The method includes, in response to determining that a pod in the call chain is unavailable, setting the retry locker parameter to an unlocked state for a previous pod just prior to the pod that is unavailable. The unlocked state allows a retry to the pod that is unavailable. In response to the previous pod reaching a retry limit, the method includes setting the retry locker parameter to unlocked for each pod in the call chain and sending a service termination message to a service requester.
