Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
3.5
-
None
-
None
Description
Today ReplicationHandler silently starts up, but when a slave tries to pull indexversion the (wrongly configured) master answers "0" instead of not answering at all which would be a better response.
Also, it should log a warning that ReplicationHandler is enabled but has no active master or slave section, and then disable the handler altogether.