[
https://issues.apache.org/jira/browse/HBASE-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13429661#comment-13429661
]
Himanshu Vashishtha commented on HBASE-6515:
--------------------------------------------
Not yet, but yes, will test in that direction.
While using ycsb, I see it does support 6MB waledit object.
HTable's write buffer can also play interesting role here; it creates one
WALEdit object per table flush. Setting it to a higher value may cause this
exception. Given that current rpc can handle 64 MB arrays, this is something to
look for.
I will report back the default limit soon.
> Setting request size with protobuf
> ----------------------------------
>
> Key: HBASE-6515
> URL: https://issues.apache.org/jira/browse/HBASE-6515
> Project: HBase
> Issue Type: Bug
> Components: ipc, replication
> Affects Versions: 0.96.0
> Reporter: Himanshu Vashishtha
> Priority: Critical
>
> While running replication on upstream code, I am hitting the size-limit
> exception while sending WALEdits to a different cluster.
> {code}
> com.google.protobuf.InvalidProtocolBufferException: IPC server unable to read
> call parameters: Protocol message was too large. May be malicious. Use
> CodedInputStream.setSizeLimit() to increase the size limit.
> {code}
> Do we have a property to set some max size or something?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
