[jira] [Resolved] (ACCUMULO-2835) Track explicit lengths of WALs for more accurate reporting

["Christopher Tubbs (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ACCUMULO-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher Tubbs resolved ACCUMULO-2835.
-----------------------------------------
    Resolution: Not A Bug

Closing this old stale issue that is not a bug. If there is more to be done here, please open a new issue or PR at https://github.com/apache/accumulo

> Track explicit lengths of WALs for more accurate reporting
> ----------------------------------------------------------
>
>                 Key: ACCUMULO-2835
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2835
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: replication
>            Reporter: Josh Elser
>            Priority: Minor
>
> Presently, during the normal ingest path, the length of each WAL isn't explicitly tracked. In practice, it isn't necessary because we can read until the end of the file (EOFException) and track progress only from the beginning. 
> This makes the bookkeeping easier, but it's then hard to assert intra-file progress for replication. The only accurate metric that can be made is the number of files needing replication, while the size actual amount of data that needs to be sent over the wire is unknown without reading the file to get the length in number of records.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)