Replication Latency

[Noe Detore]

Hello,

I trying to influence replication latency with tserver.walog.max.age.  But
noticing no difference when setting the value low. Looking in the code of
org.apache.accumulo.tserver.log.TabletServerLogger:

protected void closeForReplication(Collection<CommitSession> sessions) {
   // TODO We can close the WAL here for replication purposes
 }

This to do is called by :
testLockAndRun(logSetLock, new TestCallWithWriteLock() {
     @Override
     boolean test() {
       return (logSizeEstimate.get() > maxSize) ||
((System.currentTimeMillis() - createTime) > maxAge);
     }

     @Override
     void withWriteLock() throws IOException {
       close();
       closeForReplication(sessions);
     }
   });
   return seq;
 }

I am still trying to understand what is happening here, but could this TODO
be the reason replication status records are not being updated with
'closed: true' sooner ?

Thank you
Noe