[ https://issues.apache.org/jira/browse/ACCUMULO-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Elser updated ACCUMULO-2924: --------------------------------- Fix Version/s: (was: 1.7.0) 1.8.0 > Begin replication before WAL is marked as "closed" > -------------------------------------------------- > > Key: ACCUMULO-2924 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2924 > Project: Accumulo > Issue Type: Improvement > Components: replication > Reporter: Josh Elser > Priority: Minor > Fix For: 1.8.0 > > > Presently, we wait for a WAL to be closed before we start replicating the > data contained within. > In an "active" system (one that is continually ingesting a steady stream of > data), you don't really notice this lag. In a "fresh" system, there is a > noticeable wait before you start to get any replication flowing. This tends > to be a pain when you want to verify the correct configuration before walking > away for a coffee. > I don't believe there is anything that would break from removing this check, > but it will require a little testing to make sure the edge cases are solid. -- This message was sent by Atlassian JIRA (v6.3.4#6332)