[
https://issues.apache.org/jira/browse/HBASE-10961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13966061#comment-13966061
]
Nick Dimiduk commented on HBASE-10961:
--------------------------------------
The comment right below the changed line indicates that the blocksize was
purposefully was set to 64 bytes.
{noformat}
// set block size to 64 to making 2 kvs into one block, bypassing the
walkForwardInSingleRow
{noformat}
There's a discrepancy between this test and this line from
TestFromClientSideWithCoprocessor.
{noformat}
conf.setBoolean("hbase.table.sanity.checks", true); // enable for below tests
{noformat}
> TestFromClientSideWithCoprocessor#testGetClosestRowBefore fails due to
> invalid block size
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-10961
> URL: https://issues.apache.org/jira/browse/HBASE-10961
> Project: HBase
> Issue Type: Sub-task
> Reporter: Ted Yu
> Assignee: Ted Yu
> Priority: Minor
> Fix For: hbase-10070
>
> Attachments: 10961-v1.txt
>
>
> I saw the following test failure:
> {code}
> testGetClosestRowBefore(org.apache.hadoop.hbase.client.TestFromClientSideWithCoprocessor)
> Time elapsed: 0.003 sec <<< ERROR!
> org.apache.hadoop.hbase.DoNotRetryIOException:
> org.apache.hadoop.hbase.DoNotRetryIOException: Block size for column family
> info must be between 1K and 16MB Set hbase.table.sanity.checks to false at
> conf or table descriptor if you want to bypass sanity checks
> at
> org.apache.hadoop.hbase.master.HMaster.sanityCheckTableDescriptor(HMaster.java:1828)
> at
> org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1747)
> at
> org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1873)
> {code}
> This was due to block size of 64 passed to TEST_UTIL.createTable() call.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
