write: Will we wait for L4 feedback? Also, Customer is complaining that L2 has increased…
- User
write: Will we wait for L4 feedback? Also, Customer is complaining that L2 has increased on some nodes, I think all have to be handled in one Jira.
- Assistant
Shall we hold off on making any further changes until we receive feedback from L4? Additionally, it seems that the customer has noticed an increase in L2 on certain nodes. Perhaps we should consolidate and address all of these issues in a single Jira ticket for better tracking and resolution.
- User
write: Please note that L2 capacity alert is not the cause for the DTs to go unready After engineering has reviewed the events for July 9th after enabling GC. It appears that re-enabling GC possibly triggered lot of vnest requests and GC stalls, causing dt unready. But we will review the situation with L4 too. Regarding the L2 capacity, I will have a look and discuss with L3 to see if it is related or this needs to be handled on another SR
- Assistant
Please be aware that the L2 capacity alert is not the root cause of the DTs going unready. Upon engineering's review of the events from July 9th after GC was enabled, it seems that re-enabling GC may have resulted in numerous vnest requests and GC stalls, subsequently leading to the DTs becoming unready. We will also consult with L4 to further assess the situation.
As for the L2 capacity issue, I will investigate and collaborate with L3 to determine if it is linked to the aforementioned events or if it needs to be addressed in a separate service request.