hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "terry zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6652) [replication]replicationQueueSizeCapacity and replicationQueueNbCapacity default value is too big, Slave regionserver maybe outmemory after master start replication
Date Fri, 24 Aug 2012 06:39:42 GMT

    [ https://issues.apache.org/jira/browse/HBASE-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440985#comment-13440985
] 

terry zhang commented on HBASE-6652:
------------------------------------

another case will case slave region server oom is master disable replication and restart many
times. When we enable replication master region server will start many recovery thread (many
zk node in replication/rs/xxx/). this will still let the slave rs work in very heavy load.
                
> [replication]replicationQueueSizeCapacity and replicationQueueNbCapacity default value
is too big, Slave regionserver maybe outmemory after master start replication
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-6652
>                 URL: https://issues.apache.org/jira/browse/HBASE-6652
>             Project: HBase
>          Issue Type: Bug
>          Components: replication
>    Affects Versions: 0.94.1
>            Reporter: terry zhang
>            Assignee: terry zhang
>
> now our replication replicationQueueSizeCapacity is set to 64M and replicationQueueNbCapacity
is set to 25000. So when a master cluster with many regionserver replicate to a small cluster
。 Slave rpc queue will full and out of memory .
> java.util.concurrent.ExecutionException: java.io.IOException: Call queue is full, is
ipc.server.max.callqueue.size too small?
>         at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
>         at java.util.concurrent.FutureTask.get(FutureTask.java:83)
>         at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchCallback(HConnectionManager.java:
> 1524)
>         at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1376)
>         at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:700)
>         at org.apache.hadoop.hbase.client.HTablePool$PooledHTable.batch(HTablePool.java:361)
>         at org.apache.hadoop.hbase.replication.regionserver.ReplicationSink.batch(ReplicationSink.java:172)
>         at org.apache.hadoop.hbase.replication.regionserver.ReplicationSink.replicateEntries(ReplicationSink.java:129)
>         at org.apache.hadoop.hbase.replication.regionserver.Replication.replicateLogEntries(Replication.java:139)
>         at org.apache.hadoop.hbase.regionserver.HRegionServer.replicateLogEntries(HRegionServer.java:4018)
>         at sun.reflect.GeneratedMethodAccessor41.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.apache.hadoop.hbase.ipc.WritableRpcEngine$Server.call(WritableRpcEngine.java:361)
>         at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1414)

--
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

       

Mime
View raw message