Just upgraded a Stream cluster with 4.03. When performing the Commit to update the workers got "block timeout reached" message. Can be related to the amount of changes (195)? Is there any settings to change the timeout limit for updates?
Page 1 / 1
Is this a Cribl Cloud instance or an on-prem instance?
On-Prem
Reply
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.