[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13970524#comment-13970524
]
Hudson commented on HBASE-10312:
FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #264 (See
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/264/])
HBASE-10312 Flooding the cluster with administrative actions leads to collapse
(jdcryans: rev 1587743)
*
/hbase/branches/0.98/hbase-server/src/main/java/org/apache/hadoop/hbase/monitoring/TaskMonitor.java
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
Priority: Critical
Fix For: 0.99.0, 0.94.19, 0.98.2, 0.96.3
Attachments: HBASE-10312-0.94.patch, HBASE-10312.patch
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)
[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13970531#comment-13970531
]
Hudson commented on HBASE-10312:
SUCCESS: Integrated in HBase-TRUNK #5088 (See
[https://builds.apache.org/job/HBase-TRUNK/5088/])
HBASE-10312 Flooding the cluster with administrative actions leads to collapse
(jdcryans: rev 1587742)
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/monitoring/TaskMonitor.java
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
Priority: Critical
Fix For: 0.99.0, 0.94.19, 0.98.2, 0.96.3
Attachments: HBASE-10312-0.94.patch, HBASE-10312.patch
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)
[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13970149#comment-13970149
]
Lars Hofhansl commented on HBASE-10312:
---
You ready to commit [~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
Priority: Critical
Fix For: 0.99.0, 0.94.19, 0.98.2, 0.96.3
Attachments: HBASE-10312-0.94.patch, HBASE-10312.patch
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)
[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13970152#comment-13970152
]
Jean-Daniel Cryans commented on HBASE-10312:
Doing now.
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
Priority: Critical
Fix For: 0.99.0, 0.94.19, 0.98.2, 0.96.3
Attachments: HBASE-10312-0.94.patch, HBASE-10312.patch
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)
[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13970315#comment-13970315
]
Hudson commented on HBASE-10312:
FAILURE: Integrated in HBase-0.94-JDK7 #113 (See
[https://builds.apache.org/job/HBase-0.94-JDK7/113/])
HBASE-10312 Flooding the cluster with administrative actions leads to collapse
(jdcryans: rev 1587745)
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/monitoring/TaskMonitor.java
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
Priority: Critical
Fix For: 0.99.0, 0.94.19, 0.98.2, 0.96.3
Attachments: HBASE-10312-0.94.patch, HBASE-10312.patch
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)
[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13970336#comment-13970336
]
Hudson commented on HBASE-10312:
FAILURE: Integrated in HBase-0.94-on-Hadoop-2 #71 (See
[https://builds.apache.org/job/HBase-0.94-on-Hadoop-2/71/])
HBASE-10312 Flooding the cluster with administrative actions leads to collapse
(jdcryans: rev 1587745)
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/monitoring/TaskMonitor.java
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
Priority: Critical
Fix For: 0.99.0, 0.94.19, 0.98.2, 0.96.3
Attachments: HBASE-10312-0.94.patch, HBASE-10312.patch
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)
[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13970382#comment-13970382
]
Hudson commented on HBASE-10312:
SUCCESS: Integrated in HBase-0.94-security #467 (See
[https://builds.apache.org/job/HBase-0.94-security/467/])
HBASE-10312 Flooding the cluster with administrative actions leads to collapse
(jdcryans: rev 1587745)
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/monitoring/TaskMonitor.java
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
Priority: Critical
Fix For: 0.99.0, 0.94.19, 0.98.2, 0.96.3
Attachments: HBASE-10312-0.94.patch, HBASE-10312.patch
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)
[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13970392#comment-13970392
]
Hudson commented on HBASE-10312:
SUCCESS: Integrated in HBase-0.94 #1348 (See
[https://builds.apache.org/job/HBase-0.94/1348/])
HBASE-10312 Flooding the cluster with administrative actions leads to collapse
(jdcryans: rev 1587745)
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/monitoring/TaskMonitor.java
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
Priority: Critical
Fix For: 0.99.0, 0.94.19, 0.98.2, 0.96.3
Attachments: HBASE-10312-0.94.patch, HBASE-10312.patch
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)
[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13970425#comment-13970425
]
Hudson commented on HBASE-10312:
FAILURE: Integrated in hbase-0.96-hadoop2 #265 (See
[https://builds.apache.org/job/hbase-0.96-hadoop2/265/])
HBASE-10312 Flooding the cluster with administrative actions leads to collapse
(jdcryans: rev 1587744)
*
/hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/monitoring/TaskMonitor.java
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
Priority: Critical
Fix For: 0.99.0, 0.94.19, 0.98.2, 0.96.3
Attachments: HBASE-10312-0.94.patch, HBASE-10312.patch
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)
[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13970433#comment-13970433
]
Hudson commented on HBASE-10312:
FAILURE: Integrated in HBase-0.98 #280 (See
[https://builds.apache.org/job/HBase-0.98/280/])
HBASE-10312 Flooding the cluster with administrative actions leads to collapse
(jdcryans: rev 1587743)
*
/hbase/branches/0.98/hbase-server/src/main/java/org/apache/hadoop/hbase/monitoring/TaskMonitor.java
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
Priority: Critical
Fix For: 0.99.0, 0.94.19, 0.98.2, 0.96.3
Attachments: HBASE-10312-0.94.patch, HBASE-10312.patch
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)
[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13970434#comment-13970434
]
Hudson commented on HBASE-10312:
FAILURE: Integrated in hbase-0.96 #386 (See
[https://builds.apache.org/job/hbase-0.96/386/])
HBASE-10312 Flooding the cluster with administrative actions leads to collapse
(jdcryans: rev 1587744)
*
/hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/monitoring/TaskMonitor.java
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
Priority: Critical
Fix For: 0.99.0, 0.94.19, 0.98.2, 0.96.3
Attachments: HBASE-10312-0.94.patch, HBASE-10312.patch
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)
[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968765#comment-13968765
]
Hadoop QA commented on HBASE-10312:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12640097/HBASE-10312.patch
against trunk revision .
ATTACHMENT ID: 12640097
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/9279//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9279//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9279//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9279//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9279//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9279//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9279//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9279//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9279//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9279//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9279//console
This message is automatically generated.
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.patch
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)
[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968993#comment-13968993
]
Jean-Daniel Cryans commented on HBASE-10312:
Another reason the current code is bad is that subList returns of a view of the
original list, meaning that if you sub list enough you get the stack overflow.
http://programmingtipsandtraps.blogspot.com/2013/05/javautillistsublist-stackoverflowerror.html
It seems it can just slowly happen overtime as long as a region server is not
rebooted.
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.patch
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)
[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13969008#comment-13969008
]
Andrew Purtell commented on HBASE-10312:
bq. It seems it can just slowly happen overtime as long as a region server is
not rebooted.
Nice
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.patch
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)
[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13969010#comment-13969010
]
Jean-Daniel Cryans commented on HBASE-10312:
[~apurtell] so I take it that you're +1 on the patch? :)
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.patch
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)
[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13969014#comment-13969014
]
Andrew Purtell commented on HBASE-10312:
+1
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.patch
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)
[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13969042#comment-13969042
]
Hadoop QA commented on HBASE-10312:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12640172/HBASE-10312-0.94.patch
against trunk revision .
ATTACHMENT ID: 12640172
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9283//console
This message is automatically generated.
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-0.94.patch, HBASE-10312.patch
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)
[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13969075#comment-13969075
]
Lars Hofhansl commented on HBASE-10312:
---
+1 including 0.94. Thanks [~jdcryans]. Upped it to Critical, since this is
bad.
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
Priority: Critical
Fix For: 0.99.0, 0.94.19, 0.98.2, 0.96.3
Attachments: HBASE-10312-0.94.patch, HBASE-10312.patch
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)
[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13969088#comment-13969088
]
sinfox commented on HBASE-10312:
I have fix the StackOverflowError in
https://issues.apache.org/jira/browse/HBASE-10981, It is a wrong use of subList.
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
Priority: Critical
Fix For: 0.99.0, 0.94.19, 0.98.2, 0.96.3
Attachments: HBASE-10312-0.94.patch, HBASE-10312.patch
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)
[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13967232#comment-13967232
]
Hadoop QA commented on HBASE-10312:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org
against trunk revision .
ATTACHMENT ID: http:
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9262//console
This message is automatically generated.
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)
[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Commented] (HBASE-10312) Flooding the cluster with administrative actions leads to collapse
[
https://issues.apache.org/jira/browse/HBASE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868196#comment-13868196
]
Andrew Purtell commented on HBASE-10312:
With the AccessController active only users granted ADMIN privilege can do
this, so it's not a critical issue unless enabling security is not an option
for the deployment.
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
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.1.5#6160)
