Incorrect ReplicationSourceWALReader. totalBufferUsed may cause replication hang up

When we read a new WAL Entry in ReplicationSourceWALReader.readWALEntries, we add ReplicationSourceWALReader.totalBufferUsed by the size of new entry in ReplicationSourceWALReader.addEntryToBatch, but the whole WALEntryBatch may not be put to the ReplicationSourceWALReader.entryBatchQueue because of exception(eg. exception thrown by WALEntryFilter.filter for following WAL Entry), and the ReplicationSourceWALReader.totalBufferUsed is not decreased in this case. Because the ReplicationSourceWALReader.totalBufferUsed is actually scoped to ReplicationSourceManager, after a long run, replication to all peers may hang up.