The error is logged due to a simple script that checks every 30 seconds for replication status. It shouldn't cause any other problems except making your log look spammy. As mentioned in this issue tracker report, we are aware of the issue and should be fixed in the next release.