Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

More fixup on the checksum verify description 

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1591126 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Michael Stack 2014-04-29 22:26:00 +00:00
parent 56c0f89c82
commit 36ad5f8e98
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
hbase-common/src/main/resources/hbase-default.xml
View File

@ -1027,16 +1027,16 @@ possible configurations would overwhelm and obscure the important.
<name>hbase.regionserver.checksum.verify</name> <name>hbase.regionserver.checksum.verify</name>
<value>true</value> <value>true</value>
<description> <description>
If set to true, HBase will verify checksums for hfile blocks. HBase If set to true (the default), HBase verifies the checksums for hfile
writes checksums inline with the data when it writes out hfiles. HDFS blocks. HBase writes checksums inline with the data when it writes out
writes checksums to a separate file from data necessitating extra seeks. hfiles. HDFS (as of this writing) writes checksums to a separate file
Setting this flag should save some on i/o. Checksum verification by than the data file necessitating extra seeks. Setting this flag saves
HDFS will be internally disabled on hfile streams when this flag is set. some on i/o. Checksum verification by HDFS will be internally disabled
If the hbase-checksum verification fails, we will switch back to using on hfile streams when this flag is set. If the hbase-checksum verification
HDFS checksums (so do not disable HDFS checksums! And besides this fails, we will switch back to using HDFS checksums (so do not disable HDFS
feature applies to hfiles only, not to WALs). If this parameter is set checksums! And besides this feature applies to hfiles only, not to WALs).
to false, then hbase will not verify any checksums, instead it will If this parameter is set to false, then hbase will not verify any checksums,
depend on checksum verification being done in the HDFS client. instead it will depend on checksum verification being done in the HDFS client.
</description> </description>
</property> </property>
<property> <property>