You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Alexander Shraer (JIRA)" <ji...@apache.org> on 2014/03/17 18:13:45 UTC

[jira] [Commented] (ZOOKEEPER-1896) Reconfig error messages when upgrading from 3.4.6 to 3.5.0

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13938052#comment-13938052 ] 

Alexander Shraer commented on ZOOKEEPER-1896:
---------------------------------------------

It looks like both receiving and sending server are already running 3.5.0 in this scenario ? 
otherwise backCompatibility36 should have been true (unless something changed in the message format
for 3.4.6 and we didn't update trunk). 

If both servers are running 3.5.0, I'd suggest to print out the config to see why configFromString is complaining. 

 

> Reconfig error messages when upgrading from 3.4.6 to 3.5.0
> ----------------------------------------------------------
>
>                 Key: ZOOKEEPER-1896
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1896
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.5.0
>            Reporter: Raul Gutierrez Segales
>            Priority: Minor
>             Fix For: 3.5.0
>
>
> When upgrading from 3.4.6 (rc0 actually) to 3.5.0 (trunk as of two weeks ago actually) I got this error message:
> {noformat}
> 2014-02-26 22:12:15,446 - ERROR [WorkerReceiver[myid=4]] - Something went wrong while processing config received from 3
> {noformat}
> According to [~fpj]:
> bq. I think you’re right that the reconfig error is harmless, but we shouldn’t be getting it. The problem is that it is not detecting that we are in backward compatibility mode. We need to fix it for 3.5.0 and perhaps ZOOKEEPER-1805 is the right place for doing it.
> cc: [~shralex]



--
This message was sent by Atlassian JIRA
(v6.2#6252)