[
https://issues.apache.org/jira/browse/HBASE-10925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977862#comment-13977862
]
Mikhail Antonov commented on HBASE-10925:
-----------------------------------------
bq. This should be a configuration
Sure, I just wanted to show the draft to validate approach. That shall be in
hbase-site.xml I think (what would be the appropriate default limit I wonder?
1Gg? I think size expressed in mb or gb is better than % of heapsize.)
bq. it is a bit of a pain having to do the above. I suppose we should add a
getSize to CellUtils
Yes - or may be in the Cell interface itself? I can add this in another patch,
yep.
bq. Was also thinking what if the Cell is offheap
I thought off-heap-related work is in design/prototyping stage? Will check out.
But anyway, it'd be off-heap (JVM-wise), but still in-process for HRS, right?
So still counts towards total memory usage on the server process, and should be
limited to reasonable size, or idea is that off-heap-allocated cells would be
taken care off.._manually_, and no Scanner-level checks are needed?
Also curious about how valid the first usecase actually is?
> Do not OOME, throw RowTooBigException instead
> ---------------------------------------------
>
> Key: HBASE-10925
> URL: https://issues.apache.org/jira/browse/HBASE-10925
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: Mikhail Antonov
> Attachments: HBASE-10925.patch
>
>
> If 10M columns in a row, throw a RowTooBigException rather than OOME when
> Get'ing or Scanning w/o in-row scan flag set.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
