[
https://issues.apache.org/jira/browse/HBASE-12930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-12930:
--------------------------
Fix Version/s: (was: 2.0.0)
> Check single row size not exceed configured max row size across families for
> Get/Scan
> -------------------------------------------------------------------------------------
>
> Key: HBASE-12930
> URL: https://issues.apache.org/jira/browse/HBASE-12930
> Project: HBase
> Issue Type: Improvement
> Components: Scanners
> Reporter: Jianwei Cui
> Priority: Minor
>
> StoreScanner#next will check the 'totalBytesRead' not exceed configured
> ‘hbase.table.max.rowsize’ for each family. However, if there are several
> families, the single row will also achieve unexpected big size even if
> 'totalBytesRead' of each family not exceed 'hbase.table.max.rowsize'. This
> may cause the region server fail because of OOM. What about checking single
> row size across families in StoreScanner#next(List<Cell>, int)?
> {code}
> long totalBytesRead = 0;
> // ==> compute the size of cells have been read
> for (Cell cell : outResult) {
> totalBytesRead += CellUtil.estimatedSerializedSizeOf(old);
> }
> LOOP: while((cell = this.heap.peek()) != null) {
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
