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

stack commented on HBASE-10312:
-------------------------------

+1

Very nice [~jdcryans]

> Flooding the cluster with administrative actions leads to collapse
> ------------------------------------------------------------------
>
>                 Key: HBASE-10312
>                 URL: https://issues.apache.org/jira/browse/HBASE-10312
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Andrew Purtell
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.99.0, 0.98.2, 0.96.3
>
>         Attachments: HBASE-10312.java
>
>
> Steps to reproduce:
> 1. Start a cluster.
> 2. Start an ingest process.
> 3. In the HBase shell, do this:
> {noformat}
> while true do
>    flush 'table'
> end
> {noformat}
> We should reject abuse via administrative requests like this.
> What happens on the cluster is the requests back up, leading to lots of these:
> {noformat}
> 2014-01-10 18:55:55,293 WARN  [Priority.RpcServer.handler=2,port=8120] 
> monitoring.TaskMonitor: Too many actions in action monitor! Purging some.
> {noformat}
> At this point we could lower a gate on further requests for actions until the 
> backlog clears.
> Continuing, all of the regionservers will eventually die with a 
> StackOverflowError of unknown origin because, stack overflow:
> {noformat}
> 2014-01-10 19:02:02,783 ERROR [Priority.RpcServer.handler=3,port=8120] 
> ipc.RpcServer: Unexpected throwable object java.lang.StackOverflowError
>         at java.util.ArrayList$SubList.add(ArrayList.java:965)
> [...]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to