Josh Elser created HBASE-20952:
----------------------------------

             Summary: Re-visit the WAL API
                 Key: HBASE-20952
                 URL: https://issues.apache.org/jira/browse/HBASE-20952
             Project: HBase
          Issue Type: Sub-task
            Reporter: Josh Elser


Take a step back from the current WAL implementations and think about what an 
HBase WAL API should look like. What are the primitive calls that we require to 
guarantee durability of writes with a high degree of performance?

The API needs to take the current implementations into consideration. We should 
also have a mind for what is happening in the Ratis LogService (but the 
LogService should not dictate what HBase's WAL API looks like RATIS-272).

The API may be "OK" (or OK in a part). We need to also consider other methods 
which were "bolted" on such as {{AbstractFSWAL}} and {{WALFileLengthProvider}}. 
Other corners of "WAL use" (like the {{WALSplitter}} should also be looked at 
to use WAL-APIs only).

We also need to make sure that adequate interface audience and stability 
annotations are chosen.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to