Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

zookeeper test Maximum Request Latency is failing. How to fix the root cause?

avatar
New Contributor

Message reads:

Maximum request latency: 182,469 ms. Maximum client-negotiable session timeout: 60,000 ms. Percentage of maximum client-negotiable session timeout: 304.12%. Critical threshold: 100.00%.

 

The description of this measure is:

... the ratio of the maximum request latency to the maximum client-negotiable session timeout...

 

This failure occured about 9-10 hours after upgrade to 5.4.1.

1 ACCEPTED SOLUTION

avatar
Expert Contributor

Rebooting the cluster resolved the error message/warning. If you experience this same error message after upgrading to 5.4.1 please open a support case with Cloudera. Thank you kindly.

View solution in original post

1 REPLY 1

avatar
Expert Contributor

Rebooting the cluster resolved the error message/warning. If you experience this same error message after upgrading to 5.4.1 please open a support case with Cloudera. Thank you kindly.