Method and device for realizing automatic degradation

Abstract

The invention discloses a method and a device for realizing automatic degradation, and relates to the technical field of computers. A specific embodiment of the method comprises the following steps: receiving an access request; when the access request is abnormal, recording a time node when the abnormality occurs; when the number of the recorded time nodes is greater than a first threshold number,deleting the recorded earliest time node; and calculating a first time difference value between the earliest time node and the current time, and starting automatic degradation when the first time difference value is less than a first threshold time. According to the embodiment, automatic degradation is realized, human intervention is avoided, timed task triggering degradation is not needed, and the system performance is improved.

Description

technical field [0001] The invention relates to the field of computer technology, in particular to a method and device for realizing automatic downgrading. Background technique [0002] When obtaining services according to requests (such as accessing data sources, interfaces, etc.), it usually has a high dependence on the status of the accessed data sources or interfaces. The normal operation of the process needs to trigger degradation or change the dependence on the accessed interface and data source. At present, commonly used methods to trigger downgrade include: artificially modifying the configuration file and restarting the service or modifying the configuration online to change the dependence on the abnormal interface and data source, thereby triggering downgrade or offline access; The number of service failures or exceptions within a certain period of time triggers scheduled tasks to automatically downgrade the system. [0003] In the process of implementing the pre...

AI Technical Summary

Problems solved by technology

[0003] In the process of implementing the present invention, the inventor found that at least the following problems existed in the prior art: when obtaining services with high concurrent requests, manual intervention to modify the configuration file was slow, and before the configuration file was modified, the CPU of the server was prone to soaring, which in turn caused online Service avalanche; and by triggering scheduled tasks to achieve automatic system downgrade, a separate thread is required to regularly calculate whether to downgrade, especially when a large number of threads are required to monitor whether multiple interfaces and data sources are downgraded, which greatly increases the burden on the server , reducing the performance of the system

Images