[
https://issues.apache.org/jira/browse/ACCUMULO-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14006717#comment-14006717
]
ASF subversion and git services commented on ACCUMULO-2835:
-----------------------------------------------------------
Commit 2425fd24be9c53bc3d42900b4ffc61043929d210 in accumulo's branch
refs/heads/ACCUMULO-378 from [~elserj]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=2425fd2 ]
ACCUMULO-2835 Log a todo
> 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
> Assignee: 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
(v6.2#6252)
