Dynamic adjustment of wait time values

• US 10,389,513 B2
• Filed: 01/26/2017
• Issued: 08/20/2019
• Est. Priority Date: 01/26/2017
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Inventors: Lou, Ju-Chun, Hung, Chi-Yuan, Shih, I-Chun
• Primary Examiner(s): Pollack, Melvin H
• Application Number:
  US15/416,756
• Publication Number:
  US 20180212747A1
• Time in Patent Office: 936 Days
• Field of Search: 709248
• CPC Class Codes: H04L 41/147 for predicting network behaviour
• CPC Class Codes: H04L 43/0864 Round trip delays
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 7/0041 Delay of data signal

Abstract

Examples disclosed herein relate to a mechanism for dynamically adjusting wait time values. Some disclosed examples enable transmitting, by a source entity, a request for an action to a target entity. The action may be generated by the source entity. Some examples enable identifying a first wait time value for the source entity that indicates an amount of time that the source entity is allowed to wait for a response from the target entity between the transmission of the request and a timeout state. Some examples may enable dynamically adjusting the first wait time value based on an entity specification of the source or target entity to generate a second wait time value. Some examples may enable allowing the source entity to wait for the response from the target entity for at least the amount of time indicated in the second wait time value.

Claims

1. A method for dynamically adjusting wait time values, the method comprising:

transmitting, by a source entity, a request for an action to a target entity;

identifying an entity specification of the target entity, the entity specification comprising a hardware specification that describes a characteristic of a hardware component of the target entity;

identifying a first wait time value for the source entity that indicates an amount of time that the source entity is allowed to wait for a response from the target entity between the transmission of the request and a timeout state;

dynamically adjusting the first wait time value based on the hardware specification to generate a second wait time value; and

allowing the source entity to wait for the response from the target entity for at least an amount of time indicated by the second wait time value.

2. The method of claim 1, comprising:

determining that the timeout state occurs responsive to detecting that the response has not been received from the target entity within the amount of time indicated by the second wait time value after transmitting the request to the target entity.

3. The method of claim 1, wherein dynamically adjusting the first wait time value based on the hardware specification to generate the second wait time value comprises:

dynamically adjusting the first wait time value before a state of the source entity indicates a wait state.

4. The method of claim 3, wherein the second wait time value indicates the amount of time from the wait state to the timeout state.

5. The method of claim 1, wherein the action relates to at least one of:

a command distribution;

a process execution;

or

a communication protocol.

6. The method of claim 1, wherein the entity specification further comprises an events specification comprising information about an error event at the target entity, and

wherein dynamically adjusting the first wait time value to generate the second wait time value is further based on the events specification.

7. The method of claim 1, wherein identifying the entity specification comprises:

pinging the target entity for the entity specification; and

receiving the entity specification from the target entity.

8. The method of claim 6, wherein identifying the entity specification comprises:

receiving information in a system log of the target entity; and

determining the events specification based on the information in the system log.

9. The method of claim 1, wherein the entity specification comprises a plurality of factors, the method further comprising:

storing, in a learning database, a result of the request along with each of the plurality of factors and the second wait time value; and

dynamically adjusting the second wait time value based on the stored result to generate a third wait time value.

16. The method of claim 1, wherein the hardware specification describes a characteristic of a processor of the target entity.

17. The method of claim 1, wherein the hardware specification describes a characteristic of a memory of the target entity.

18. The method of claim 1, wherein the hardware specification describes a characteristic of a network interface controller of the target entity.

19. The method of claim 1, wherein the entity specification further comprises a software specification that describes a characteristic of a software of the target entity, and wherein dynamically adjusting the first wait time value to generate the second wait time value is further based on the software specification.

10. A non-transitory machine-readable storage medium comprising instructions that upon execution cause a source entity to:

identify an entity specification for a target entity, the entity specification comprising a software specification that describes a characteristic of a software of the target entity;

dynamically adjust a wait time from a first wait time value to a different second wait time value based on the software specification, the wait time indicating an amount of time that the source entity is allowed to wait for a response to a request before a timeout at the source entity;

send the request from the source entity to the target entity; and

determine whether to timeout at the source entity based on whether the response to the request has been received from the target entity within the wait time set to the second wait time value.

11. The non-transitory machine-readable storage medium of claim 10, wherein the request is a first request, and the instructions upon execution cause the source entity to:

store, in a learning database, a result of the first request along with the second wait time value and along with at least one of a plurality of factors in the entity specification of the target entity;

dynamically adjust the wait time from the second wait time value to a third time value based on the stored result in the learning database;

send a second request from the source entity to the target entity; and

allow the source entity to wait for a second response in response to the second request for at least an amount of time indicated by the third wait time value.

12. The non-transitory machine-readable storage medium of claim 10, wherein the instructions upon execution cause the source entity to:

dynamically adjust the wait time based on a network condition between the source entity and the target entity.

13. The non-transitory machine-readable storage medium of claim 10, wherein the entity specification further comprises a hardware specification that describes a characteristic of a hardware component of the target entity, and wherein dynamically adjusting the wait time from the first wait time value to the different second wait time value is further based on the hardware specification.

14. The non-transitory machine-readable storage medium of claim 10, wherein the software specification identifies a version of an operating system at the target entity, and wherein dynamically adjusting the wait time from the first wait time value to the different second wait time value is based on the version of the operating system at the target entity.

15. A system comprising:

a hardware processor; and

a non-transitory storage medium storing instructions executable on the hardware processor to;

identify an entity specification for a target entity, the entity specification comprising at least one of a hardware specification of the target entity or a software specification of the target entity, the hardware specification describing a characteristic of a hardware component of the target entity, and the software specification describing a characteristic of a software of the target entity;

dynamically adjust a wait time from a first wait time value to a different second wait time value based on the at least one of the hardware specification or the software specification, the wait time indicating an amount of time that the source entity is allowed to wait for a response to a request before a timeout at the source entity;

send the request from the source entity to the target entity; and

determine whether to timeout at the source entity based on whether the response to the request has been received from the target entity within the wait time set to the second wait time value.

20. The system of claim 15, wherein the entity specification comprises both the hardware specification and the software specification, and wherein dynamically adjusting the wait time from the first wait time value to the different second wait time value is based on the hardware specification and the software specification.