为什么Hbase需要WAL?

本文介绍了为什么Hbase需要WAL?的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

我是Hbase的新手，我发现Hbase会将所有操作写入WAL和memstore.

解决方案

WAL用于恢复目的.通过 MapR文档，可以使您更加了解hbase架构. /p>

当客户端发出Put请求时，第一步是将数据写入预写日志WAL:

将编辑内容附加到存储在磁盘上的WAL文件的末尾.
WAL用于在服务器崩溃时恢复尚未持久的数据.

将数据写入WAL之后，它将放置在MemStore中.然后，放置请求确认将返回给客户端.

如果启用了 .. 是

如果WAL被禁用，则可以通过消除写入WAL的额外开销来直接对文件进行操作.

注意:

一般情况下WAL将被禁用以进行突变(行级突变)/执行写入操作.如果这样做的话，根本的警告是，不要恢复……意味着数据丢失.另外，如果您正在使用SOLR，它将在WAL上运行，因此SOLR文档将不会更新.如果没有，您可以禁用WAL

进一步阅读，请参见我的回答

I'm new to Hbase, and I found that Hbase will write all the operations to WAL and memstore.

解决方案

WAL is for recovery purpose. lets understand hbase architecture in a close way by MapR docs.

When the client issues a Put request, the first step is to write the data to the write-ahead log, the WAL:

Edits are appended to the end of the WAL file that is stored on disk.
The WAL is used to recover not-yet-persisted data in case a server crashes.

Once the data is written to the WAL, it is placed in the MemStore. Then, the put request acknowledgement returns to the client.

If WAL is enabled.. Yes

If WAL is disabled it can operate on the files directly by removing additional overhead of writing in to WAL.

NOTE:

General cases WAL will be disabled for mutation(Row-level mutations)/write performance purpose. Underlying caveat if you do so is, dont wont be recoverable... means data loss. Also if you are using SOLR, which will work on WAL and hence SOLR documents wont be updated. if dont have the case you can go ahead with disabling WAL