Project:
| View Revisions: Issue #38007 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0038007: LogClient can generate too many useless requests if server is struggling | ||
| Revision | 2018-02-27 11:41 by marvintm | ||
| Description | Currently, the logclient is sent every 30 seconds, and the request has a timeout of 20 seconds. Normally, this is fine, and there is more than enough time to send even the maximum page size in these 20 seconds. However, sometimes the backend server may be struggling for some other reason, or the bandwidth in the store may not be enough, and finally the request cannot be completed in this time. In this case, as the interval is currently 30 seconds, the terminal will every 30 seconds send another request, which most likely will also fail, thus eventually flooding the server with these requests, and wasting a significant amount of network bandwidth and server resources. We don't want to change the interval because in normal cases we want to send the logclient information as soon as possible. However, we can increase the timeout of the logclient by default, and the terminal should behave smartly and should not generate another request if the previous one is still being processed. With these two changes, the terminal will no longer flood the server with requests in case it's struggling, but instead will automatically adjust itself, and stop sending the logclient information if the server is not able to absorb it. |
||
| Revision | 2018-02-27 11:40 by marvintm | ||
| Description | Currently, the logclient is sent every 30 seconds, and the request has a timeout of 20 seconds. Normally, this is fine, and there is more than enough time to send even the maximum page size in these 20 seconds. However, sometimes the backend server may be struggling for some other reason, or the bandwidth in the store may not be enough, and finally the request cannot be completed in this time. In this case, as the interval is currently 30 seconds, the terminal will every 30 seconds send another request, which most likely will also fail, thus eventually flooding the server with these requests, and wasting a significant amount of network bandwidth and server resources. We don't want to change the interval because in normal cases we want to send the logclient information as soon as possible. However, we want to increase the timeout of the logclient by default, and the terminal should behave smartly and should not generate another request if the previous one is still being processed. With these two changes, the terminal will no longer flood the server with requests in case it's struggling, but instead will automatically adjust itself, and stop sending the logclient information if the server is not able to absorb it. |
||
| Revision | 2018-02-27 11:40 by marvintm | ||
| Description | Currently, the logclient is sent every 30 seconds, and the request has a timeout of 20 seconds. Normally, this is fine, and there is more than enough time to send even the maximum page size in these 20 seconds. However, sometimes the backend server may be struggling for some other reason, or the bandwidth in the store may not be enough, and finally the request cannot be completed in this time. In this case, as the interval is currently 30 seconds, the terminal will every 30 seconds send another request, which most likely will also fail, thus eventually flooding the server with these requests, and wasting a significant amount of network bandwidth. We don't want to change the interval because in normal cases we want to send the logclient information as soon as possible. However, we want to increase the timeout of the logclient by default, and the terminal should behave smartly and should not generate another request if the previous one is still being processed. With these two changes, the terminal will no longer flood the server with requests in case it's struggling, but instead will automatically adjust itself, and stop sending the logclient information if the server is not able to absorb it. |
||
| Revision | 2018-02-27 11:39 by marvintm | ||
| Description | Currently, the logclient is sent every 30 seconds, and the request has a timeout of 20 seconds. Normally, this is fine, and there is more than enough time to send even the maximum page size in this 20 seconds. However, sometimes the backend server may be struggling for some other reason, or the bandwidth in the store may not be enough, and finally the request cannot be completed in this time. In this case, as the interval is currently 30 seconds, the terminal will every 30 seconds send another request, which most likely will also fail, thus eventually flooding the server with these requests, and wasting a significant amount of network bandwidth. We don't want to change the interval because in normal cases we want to send the logclient information as soon as possible. However, we want to increase the timeout of the logclient by default, and the terminal should behave smartly and should not generate another request if the previous one is still being processed. With these two changes, the terminal will no longer flood the server with requests in case it's struggling, but instead will automatically adjust itself, and stop sending the logclient information if the server is not able to absorb it. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |