accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam J Shook (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4751) Some WALs don't replicate due to lacking a createdTime entry
Date Wed, 06 Dec 2017 20:29:00 GMT


Adam J Shook commented on ACCUMULO-4751:

I have attached some logs tracking a particular WAL file.  You can see that it has a {{createdTime}}
but at some point a deleting entry must be written (note the timestamp change but the {{createdTime}}
is gone) and then other entries added.

> Some WALs don't replicate due to lacking a createdTime entry
> ------------------------------------------------------------
>                 Key: ACCUMULO-4751
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.7.3, 1.8.1
>            Reporter: Adam J Shook
>            Assignee: Adam J Shook
>         Attachments: repl_logs.txt
> From what I can tell, the below error is thrown when no data for a particular table is
written to a WAL, but the file is closed.  This would be because the {{Status}} entry from
the {{StatusUtil}} for {{fileClosed}} is pre-built and therefore does not have a {{createdTime}}.
 This prevents a WAL from being replicated until a {{createdTime}} entry is added manually.
> From the Accumulo master:
> {code}
> Status record ([begin: 0 end: 0 infiniteEnd: true closed: true]) for hdfs://namenode:9000/accumulo/wal/
in table 7l was written to metadata table which lacked createdTime
> {code}
> There are two solutions I have in mind:
> 1. Update the {{StatusUtil}} such that every returned {{Status}} object sets the {{createdTime}}
to {{System.currentTimeMillis}} if not explicitly given.
> 2. Update the Accumulo Master to set the {{createdTime}} to the WAL's modification time
in HDFS if the WAL is closed but there is no {{createdTime}}.

This message was sent by Atlassian JIRA

View raw message