3.0 release has a memory leak, it has been identified, please merge. #2606
Assignees
Labels
Milestone
Comments
|
👍 I will find time to merge it into 3.0.
|
winlinvip
added a commit
that referenced
this issue
Oct 7, 2021
|
Fixed by e801174 |
winlinvip
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Using srs3.0 r5 version, we found a problem of slow memory growth. The cluster consists of 2 edges and 2 origin servers. There are some sources that are missing or closed, and the edge nodes frequently receive pull requests for these sources. At this time, the edge will continuously perform edge-pull operations between the 2 origin servers. After running for a long time, we noticed that the memory keeps increasing, although the growth is relatively slow (the speed of growth depends on the number of invalid pull requests).
We analyzed the subsequent updates of version 3.0 r5 and found no modifications addressing this issue. Then we compared it with version 4.0 and found that it has been changed in the 4.0 version, for more details refer to [reference].
b9355c1
Additionally, after encountering the issue, we tried using the gmc tool with srs3.0 r5 version, but it was not successful. We received the following error message. Do you have any suggestions?
TRANS_BY_GPT3The text was updated successfully, but these errors were encountered: