Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

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.