66 lines
1.7 KiB
Markdown
66 lines
1.7 KiB
Markdown
|
# 【WMS-UTR项目】pcap-tsgx01出现tsg_os_packet_io_rx_drop告警
|
|||
|
|
|
|||
|
|
| ID | Creation Date | Assignee | Status |
|
|||
|
|
|----|----------------|----------|--------|
|
|||
|
|
| OMPUB-1190 | 2024-03-22T14:32:27.000+0800 | 杨威 | 已关闭 |
|
|||
|
|
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
根据3月21号当天的告警发现pcap-tsgx01出现多条 tsg_os_packet_io_rx_drop告警，附件为当天的告警信息与pcap-tsgx01的监控信息**yangwei** commented on *2024-03-25T09:22:46.371+0800*:
|
|||
|
|
|
|||
|
|
* 现象
|
|||
|
|
** 丢包现象自3月21日 6:00AM前后开始，丢包计数持续波动，对应时段Firewall的CPU占用较高，整体丢包的趋势和CPU占用上涨与流量增长相关
|
|||
|
|
* 原因
|
|||
|
|
** NZ上Firewall对应业务计数显示No data（应该受OMPUB-1172 NZ页面部分部分监控指标未采集到影响），缺乏业务相关的指标，初步推测丢包和CPU占用上涨与日志发送量相关
|
|||
|
|
*** 截至3月21日，P19仅在MSH-TSG01上开启异步发送日志，其他日志量大的设备仍采用同步日志发送，流量增长后默认的日志发送模式（包处理线程直接调用rdkafka）可能造成丢包
|
|||
|
|
* 处理
|
|||
|
|
** 在所有tsgx设备开启异步日志发送
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
P19 WMS
|
|||
|
|
|
|||
|
|
!image-2024-03-25-09-11-58-116.png|width=388,height=276!
|
|||
|
|
|
|||
|
|
!image-2024-03-25-09-13-19-990.png|width=772,height=280!!image-2024-03-25-09-12-49-169.png|width=766,height=260!
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
**yangwei** commented on *2024-05-17T16:12:12.378+0800*:
|
|||
|
|
|
|||
|
|
至2024.5.16，WMS现场未再出现本issue中描述的rx_drop现象，暂时关闭本issue
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
## Attachments
|
|||
|
|
|
|||
|
|
**54088/alert-message-2024-03-22+10-56-34.xlsx**
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
**54134/image-2024-03-25-09-11-58-116.png**
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
**54135/image-2024-03-25-09-12-49-169.png**
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
**54136/image-2024-03-25-09-13-19-990.png**
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
**54087/pcap-tsgx01(1).html**
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|