[jira] [Commented] (ACCUMULO-2574) Define storage data structure for data that needs replication

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ACCUMULO-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004219#comment-14004219 ] 

ASF subversion and git services commented on ACCUMULO-2574:
-----------------------------------------------------------

Commit b53bbf08a35cf2ad82c9638fd81a67a671da71ab in accumulo's branch refs/heads/ACCUMULO-378 from [~elserj]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=b53bbf0 ]

ACCUMULO-2574 Change closedTime into createdTime

It's rather impossible to actually konw the exact point in time when
a WAL is no longer in use by any tablets. We can know when a tablet is
done with a WAL, but many tablets may be referencing it which convolutes
things.

Instead, we can get the same intent (global ordering of WALs for a tserver)
by recording the time in which the WAL was first created as this is something
that only occurs once in the lifetime of a file.


> Define storage data structure for data that needs replication
> -------------------------------------------------------------
>
>                 Key: ACCUMULO-2574
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2574
>             Project: Accumulo
>          Issue Type: Sub-task
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.7.0
>
>
> We need to track data that needs replication. At a minimum we need to track where the data came from (to support cycles in the replication graph), optional offsets into the file that needs replicating (important for WALs to avoid having to wait for a WAL to be closed before replicating).
> It might make sense to include where the data should be replicated to. Not sure if it makes sense to do that as late as possible or earlier on.



--
This message was sent by Atlassian JIRA
(v6.2#6252)