[
https://issues.apache.org/jira/browse/HBASE-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664922#action_12664922
]
stack commented on HBASE-1134:
------------------------------
Just saw your comment on IRC:
{code}
02:31 < jdcryans> I think the OOME should be a blocker for 0.19
02:32 < jdcryans> After updating our prod, someone used a piece of software
with the 0.18 client in it and it OOME'd the master
{code}
I agree... if any 0.18 client can make master OOME, then yes, I think also it a
blocker.
> OOME in HMaster when HBaseRPC is older than 0.19
> ------------------------------------------------
>
> Key: HBASE-1134
> URL: https://issues.apache.org/jira/browse/HBASE-1134
> Project: Hadoop HBase
> Issue Type: Bug
> Components: ipc
> Reporter: Jean-Daniel Cryans
> Assignee: Jean-Daniel Cryans
> Priority: Blocker
> Fix For: 0.19.0
>
> Attachments: hbase-1134.patch
>
>
> When the Master receives a RPC call from any other version than 0.19, it gets:
> {code}
> 2009-01-17 22:04:00,266 WARN org.apache.hadoop.ipc.HBaseServer: Out of Memory
> in server select
> java.lang.OutOfMemoryError: Java heap space
> at
> org.apache.hadoop.hbase.ipc.HBaseRPC$Invocation.readFields(HBaseRPC.java:142)
> at
> org.apache.hadoop.hbase.ipc.HBaseServer$Connection.processData(HBaseServer.java:847)
> at
> org.apache.hadoop.hbase.ipc.HBaseServer$Connection.readAndProcess(HBaseServer.java:814)
> at
> org.apache.hadoop.hbase.ipc.HBaseServer$Listener.doRead(HBaseServer.java:399)
> at
> org.apache.hadoop.hbase.ipc.HBaseServer$Listener.run(HBaseServer.java:308)
> {code}
> Easy to recreate by just starting a local 0.19 HBase and using the 0.18 shell
> to create a table.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
