a lot of responses 502 from engines¶
Archived (pre-2022)
Preserved for reference only -- likely outdated. View original | Last updated: August 2018
Check Kibana with filter response:502:
[https://kibana.prd.fyber.com/app/kibana#/discover?_g=(refreshInterval:(display:Off,pause:!f,value:0),time:(from:now-15m,mode:quick,to:now))&_a=(columns:!(beat.hostname),index:AWFxLRzw4iaFRQsI2gxR,interval:auto,query:(query_string:(analyze_wildcard:!t,query:'response:502')),sort:!('@timestamp',desc))](https://kibana.prd.fyber.com/app/kibana#/discover?_g=(refreshInterval:(display:Off,pause:!f,value:0),time:(from:now-15m,mode:quick,to:now))&_a=(columns:!(beat.hostname),index:AWFxLRzw4iaFRQsI2gxR,interval:auto,query:(query_string:(analyze_wildcard:!t,query:)
If you see there are a lot of 502 responses from engines servers:
- check local kafka log /var/log/kafka/server.log
- If it stuck, try to reboot it (systemctl restart kafka-server).
- if it continuously restarting you should find message about corrupted topic partition. Find it inĀ /var/lib/kafka/logs/topic_partition/* and remove corrupted log file. After this kafka should able to start
If this was the cause and it was fixed 502, responses in kibana should go.