-
Notifications
You must be signed in to change notification settings - Fork 312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zk c client 3.7 does not run well with zk server 3.4 #1092
Comments
@foreverneverer have you checked the zookeeper server side log? |
meta server log and zk client log are not at the same time, I'm not sure if they are related. Could you paste the 3 parties logs and make sure they are at the same time? |
This issuse seems related to this problem, https://issues.apache.org/jira/browse/ZOOKEEPER-1998. |
The log was copied from different time, but the log detail is same, I don't re-produce the log |
added |
The issue seem say |
This issue exists in all zk client versions, this patch just add a new API (i.e. |
OK, how add .patch file? I can try it |
zk c client 3.7.0 already have this patch . I add config on https://github.com/apache/incubator-pegasus/pull/1100/files, try it |
Great! But I have test it and it doesn't work well. the log: Pegasus:
Zookeeper:
|
Bug Report
XiaoMi/rdsn#979 upgrade zk c client to 3.7(from 3.4.10) for kerberos, but it sometime can't access zk server 3.4.5
In my test, when I upgrade the meta to latest pegasus server, the meta error log:
ERR_INCONSISTENT_STATE
is from zk errorZRUNTIMEINCONSISTENCY
, see the zk error log:In server side, zk find some connection was closed by client:
The above bug does not always occur, I only find the bug in one cluster of our company, The following resolution will be ok:
Related jira:
https://issues.apache.org/jira/browse/ZOOKEEPER-4603
The text was updated successfully, but these errors were encountered: