hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-20952) Re-visit the WAL API
Date Tue, 02 Oct 2018 05:43:00 GMT

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

Hudson commented on HBASE-20952:
--------------------------------

Results for branch HBASE-20952
	[build #5 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-20952/5/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-20952/5//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-20952/5//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-20952/5//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Re-visit the WAL API
> --------------------
>
>                 Key: HBASE-20952
>                 URL: https://issues.apache.org/jira/browse/HBASE-20952
>             Project: HBase
>          Issue Type: Improvement
>          Components: wal
>            Reporter: Josh Elser
>            Priority: Major
>         Attachments: 20952.v1.txt
>
>
> 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).
> Other "systems" inside of HBase that use WALs are replication and backup&restore.
Replication has the use-case for "tail"'ing the WAL which we should provide via our new API.
B&R doesn't do anything fancy (IIRC). We should make sure all consumers are generally
going to be OK with the API we create.
> 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)

Mime
View raw message