[
https://issues.apache.org/jira/browse/HBASE-18043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009145#comment-16009145
]
Anoop Sam John commented on HBASE-18043:
----------------------------------------
bq."hbase.server.keyvalue.maxsize";
Call it ....cell.maxsize? We try avoid KV naming
HRegion
/**
+hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java * Licensed
to the Apache Software Foundation (ASF) under one
This is by some mistake I believe.
This is per cell size limiting. Do we have some checks before accepting RPC
requests itself on the size? Avoiding service down by many large requests. We
would have read those request bytes making bad GC issues.. Just asking Andy.
Else +1
> Institute a hard limit for individual cell size that cannot be overridden by
> clients
> ------------------------------------------------------------------------------------
>
> Key: HBASE-18043
> URL: https://issues.apache.org/jira/browse/HBASE-18043
> Project: HBase
> Issue Type: Improvement
> Components: IPC/RPC, regionserver
> Affects Versions: 2.0.0
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-18043-branch-1.patch, HBASE-18043-branch-1.patch,
> HBASE-18043.patch, HBASE-18043.patch
>
>
> For sake of service protection we should not give absolute trust to clients
> regarding resource limits that can impact stability, like cell size limits.
> We should add a server side configuration that sets a hard limit for
> individual cell size that cannot be overridden by the client. We can keep the
> client side check, because it's expensive to reject a RPC that has already
> come in.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
