Hi, Does anyone have any thoughts on this issue? This has been very frustrating to troubleshoot. It's basically trial and error for us. Any changes to the following configs have not helped.
* Spout/bolt parallelism * Increase executor receive queue * Increase worker transfer queue * Increase backpressure check millis * Increase Netty buffer high watermark We even restored the state to when the topology was continually processing before, but processing is still stopped. So it seems like something is going on and it is not our topology code/configs. Any help here is greatly appreciated. Thanks, Binh From: Le, Binh T. Sent: Monday, April 18, 2022 1:17 PM To: [email protected] Subject: Storm 2 Topology Stopped Processing Hi, We are upgrading our Storm 1 cluster to 2.2.0 and noticed a strange behavior. The topology is processing millions of messages fine. However, all of a sudden, processing just stopped. Capacity for all bolts got reduced to zero and stays at zero. Does anyone know what could possibly be going on here and how we can troubleshoot this issue? Thanks, Binh ________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy. ______________________________________________________________________________________ www.accenture.com
