[ACCUMULO-4751] Some WALs don't replicate due to lacking a createdTime entry

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7.3, 1.8.1
• Fix Version/s: 1.9.0
• Labels: pull-request-available
• Assignee: Adam J. Shook
• Reporter: Adam J. Shook
• Created: 04/Dec/17 16:28
• Updated: 23/Apr/19 16:12
• Resolved: 31/Dec/17 02:08

Description

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:

Status record ([begin: 0 end: 0 infiniteEnd: true closed: true]) for hdfs://namenode:9000/accumulo/wal/tserver.example.com+31732/f922df9c-3ffc-49ee-8d0c-261c7a05fea2 in table 7l was written to metadata table which lacked createdTime

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.

Issue Links

• links to: GitHub Pull Request #339