stack commented on HBASE-15536:

bq. We can introduce a new config named 'max.wal.edit.size' which is used to 
limit the size of one atomic operation and set the default value less than 
16MB? This could make it possible to make AsyncFSWAL as our default WAL.

Where would we do the check? On client-side?

We would have to dissassemble the WALEdit to break it into 16MB pieces? Each 
edit would have same sequenceid?

> Make AsyncFSWAL as our default WAL
> ----------------------------------
>                 Key: HBASE-15536
>                 URL: https://issues.apache.org/jira/browse/HBASE-15536
>             Project: HBase
>          Issue Type: Sub-task
>          Components: wal
>    Affects Versions: 2.0.0
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Critical
>             Fix For: 2.0.0
>         Attachments: HBASE-15536-v1.patch, HBASE-15536-v2.patch, 
> HBASE-15536-v3.patch, HBASE-15536-v4.patch, HBASE-15536-v5.patch, 
> HBASE-15536.patch
> As it should be predicated on passing basic cluster ITBLL

This message was sent by Atlassian JIRA

Reply via email to