[ZOOKEEPER-1992] backward compatibility of zoo.cfg

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 3.5.0
• Fix Version/s: 3.5.0
• Hadoop Flags: Reviewed
• Assignee: Hongchao Deng
• Reporter: Hongchao Deng
• Created: 28/Jul/14 02:05
• Updated: 02/Aug/14 19:00
• Resolved: 01/Aug/14 05:43

Description

This issue supersedes our discussion in ZOOKEEPER-1989.

To summarize, ZK users can seamlessly upgrade 3.4 to 3.5. But two things will happen:
1. the server list will be separated out as a dynamic file (the original should be backup automatically).
2. Client port is mandatory on reconfig. So when reconfig the server itself (its id), the client port in config file will be removed and replaced by the one in reconfig (written in dynamic file).

Issue Links

• contains: ZOOKEEPER-1999 Converting CRLF to LF in DynamicConfigBackwardCompatibilityTest
• duplicates: ZOOKEEPER-1989 backward compatibility of zoo.cfg
• requires: ZOOKEEPER-1997 server with a single line server list shouldn't be StandaloneEnabled

Sub-Tasks

• Keep the client port upon parsing config: Resolved
• Safely remove client port in old config file on reconfig itself: Resolved