You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/04/04 18:00:00 UTC
[jira] [Reopened] (HBASE-20329) Add note for operators to refguide
on AsyncFSWAL
[ https://issues.apache.org/jira/browse/HBASE-20329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack reopened HBASE-20329:
---------------------------
Reopening to add an addendum that answers this question from mailing list:
*ASYNC_WAL and visibility*
{quote}
Hi all,
I cannot find any good information about ASYNC_WAL semantics.
As much as I understand the worst I can get - data loss in case of region
failure.
But the question I have - can it affect visibility in any way? Does it
still follow the principle "When a client receives a "success" response for
any mutation, that mutation is immediately visible to both that client and
any client with whom it later communicates through side channels" ?
Another question - is data loss possible in any situation other than region
failure?
{quote}
[~anoop.hbase] answered it. The doc now has note on possible dataloss but need to add the bit on visibility.
> Add note for operators to refguide on AsyncFSWAL
> ------------------------------------------------
>
> Key: HBASE-20329
> URL: https://issues.apache.org/jira/browse/HBASE-20329
> Project: HBase
> Issue Type: Sub-task
> Components: documentation, wal
> Reporter: stack
> Assignee: stack
> Priority: Critical
> Fix For: 3.0.0
>
> Attachments: HBASE-20329.master.001.patch
>
>
> Need a few notes in refguide on this new facility.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)