[jira] [Commented] (HBASE-4518) TestServerCustomProtocol is flaky
[
https://issues.apache.org/jira/browse/HBASE-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13143028#comment-13143028
]
Hudson commented on HBASE-4518:
---
Integrated in HBase-TRUNK #2406 (See
[https://builds.apache.org/job/HBase-TRUNK/2406/])
HBASE-4518 TestServerCustomProtocol fails intermittently
garyh :
Files :
* /hbase/trunk/CHANGES.txt
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/TestServerCustomProtocol.java
TestServerCustomProtocol is flaky
-
Key: HBASE-4518
URL: https://issues.apache.org/jira/browse/HBASE-4518
Project: HBase
Issue Type: Test
Components: coprocessors, test
Affects Versions: 0.92.0
Reporter: Gary Helmling
Assignee: Gary Helmling
Fix For: 0.92.0
Attachments: HBASE-4518.patch,
org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol-output.txt,
org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol.txt
TestServerCustomProtocol has been showing some intermittent failures in
Jenkins due to what looks like region transitions.
Here is the most recent failure:
{noformat}
Results :
Failed tests:
testRowRange(org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol):
Results should contain region
test,bbb,1317332645939.aea9154349b9e0dc207e2e9476702763. for row 'bbb'
{noformat}
--
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
[jira] [Commented] (HBASE-4518) TestServerCustomProtocol is flaky
[
https://issues.apache.org/jira/browse/HBASE-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13143054#comment-13143054
]
Hudson commented on HBASE-4518:
---
Integrated in HBase-0.92 #104 (See
[https://builds.apache.org/job/HBase-0.92/104/])
HBASE-4518 TestServerCustomProtocol fails intermittently
garyh :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/regionserver/TestServerCustomProtocol.java
TestServerCustomProtocol is flaky
-
Key: HBASE-4518
URL: https://issues.apache.org/jira/browse/HBASE-4518
Project: HBase
Issue Type: Test
Components: coprocessors, test
Affects Versions: 0.92.0
Reporter: Gary Helmling
Assignee: Gary Helmling
Fix For: 0.92.0
Attachments: HBASE-4518.patch,
org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol-output.txt,
org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol.txt
TestServerCustomProtocol has been showing some intermittent failures in
Jenkins due to what looks like region transitions.
Here is the most recent failure:
{noformat}
Results :
Failed tests:
testRowRange(org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol):
Results should contain region
test,bbb,1317332645939.aea9154349b9e0dc207e2e9476702763. for row 'bbb'
{noformat}
--
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
[jira] [Commented] (HBASE-4518) TestServerCustomProtocol is flaky
[
https://issues.apache.org/jira/browse/HBASE-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13142244#comment-13142244
]
stack commented on HBASE-4518:
--
I shouldn't have said anything. My mention of this issue caused the test to
start failing up on jenkins again.
TestServerCustomProtocol is flaky
-
Key: HBASE-4518
URL: https://issues.apache.org/jira/browse/HBASE-4518
Project: HBase
Issue Type: Bug
Components: coprocessors, test
Affects Versions: 0.92.0
Reporter: Gary Helmling
Fix For: 0.92.0
Attachments:
org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol-output.txt,
org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol.txt
TestServerCustomProtocol has been showing some intermittent failures in
Jenkins due to what looks like region transitions.
Here is the most recent failure:
{noformat}
Results :
Failed tests:
testRowRange(org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol):
Results should contain region
test,bbb,1317332645939.aea9154349b9e0dc207e2e9476702763. for row 'bbb'
{noformat}
--
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
[jira] [Commented] (HBASE-4518) TestServerCustomProtocol is flaky
[
https://issues.apache.org/jira/browse/HBASE-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13142294#comment-13142294
]
stack commented on HBASE-4518:
--
This line:
{code}
+util.getConfiguration().set(CoprocessorHost.REGION_COPROCESSOR_CONF_KEY,
+PingHandler.class.getName());
{code}
does what
{code}
-// TODO: use a test coprocessor for registration (once merged with CP code)
-// sleep here is an ugly hack to allow region transitions to finish
-Thread.sleep(5000);
-for (JVMClusterUtil.RegionServerThread t :
- cluster.getRegionServerThreads()) {
- for (HRegionInfo r : t.getRegionServer().getOnlineRegions()) {
-t.getRegionServer().getOnlineRegion(r.getRegionName())
-.registerProtocol(PingProtocol.class, new PingHandler());
- }
-}
{code}
... used to do?
If so, +1 on commit if patch-build gives back reasonable results.
TestServerCustomProtocol is flaky
-
Key: HBASE-4518
URL: https://issues.apache.org/jira/browse/HBASE-4518
Project: HBase
Issue Type: Bug
Components: coprocessors, test
Affects Versions: 0.92.0
Reporter: Gary Helmling
Assignee: Gary Helmling
Fix For: 0.92.0
Attachments: HBASE-4518.patch,
org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol-output.txt,
org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol.txt
TestServerCustomProtocol has been showing some intermittent failures in
Jenkins due to what looks like region transitions.
Here is the most recent failure:
{noformat}
Results :
Failed tests:
testRowRange(org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol):
Results should contain region
test,bbb,1317332645939.aea9154349b9e0dc207e2e9476702763. for row 'bbb'
{noformat}
--
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
[jira] [Commented] (HBASE-4518) TestServerCustomProtocol is flaky
[
https://issues.apache.org/jira/browse/HBASE-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13142307#comment-13142307
]
Gary Helmling commented on HBASE-4518:
--
@Stack,
Yes, for some reason in the original code I was being a bit too clever and
registering the protocol handler directly. Maybe it was before all the
connecting bits had been filled in yet... In any case, the manual registration
in the original code would mean that the PingHandler would not get
re-registered if a region closed on one RS and was reopened on another. So
that is a flaw. And the test code should really be doing what we tell people
to do with endpoints, which is to configure them as coprocessors.
TestServerCustomProtocol is flaky
-
Key: HBASE-4518
URL: https://issues.apache.org/jira/browse/HBASE-4518
Project: HBase
Issue Type: Bug
Components: coprocessors, test
Affects Versions: 0.92.0
Reporter: Gary Helmling
Assignee: Gary Helmling
Fix For: 0.92.0
Attachments: HBASE-4518.patch,
org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol-output.txt,
org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol.txt
TestServerCustomProtocol has been showing some intermittent failures in
Jenkins due to what looks like region transitions.
Here is the most recent failure:
{noformat}
Results :
Failed tests:
testRowRange(org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol):
Results should contain region
test,bbb,1317332645939.aea9154349b9e0dc207e2e9476702763. for row 'bbb'
{noformat}
--
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
[jira] [Commented] (HBASE-4518) TestServerCustomProtocol is flaky
[
https://issues.apache.org/jira/browse/HBASE-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13142400#comment-13142400
]
Hadoop QA commented on HBASE-4518:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12501985/HBASE-4518.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
-1 javadoc. The javadoc tool appears to have generated -165 warning
messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
-1 findbugs. The patch appears to introduce 42 new Findbugs (version
1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.master.TestDistributedLogSplitting
org.apache.hadoop.hbase.TestGlobalMemStoreSize
org.apache.hadoop.hbase.master.TestMasterFailover
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/141//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/141//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/141//console
This message is automatically generated.
TestServerCustomProtocol is flaky
-
Key: HBASE-4518
URL: https://issues.apache.org/jira/browse/HBASE-4518
Project: HBase
Issue Type: Bug
Components: coprocessors, test
Affects Versions: 0.92.0
Reporter: Gary Helmling
Assignee: Gary Helmling
Fix For: 0.92.0
Attachments: HBASE-4518.patch,
org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol-output.txt,
org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol.txt
TestServerCustomProtocol has been showing some intermittent failures in
Jenkins due to what looks like region transitions.
Here is the most recent failure:
{noformat}
Results :
Failed tests:
testRowRange(org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol):
Results should contain region
test,bbb,1317332645939.aea9154349b9e0dc207e2e9476702763. for row 'bbb'
{noformat}
--
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
[jira] [Commented] (HBASE-4518) TestServerCustomProtocol is flaky
[
https://issues.apache.org/jira/browse/HBASE-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13141481#comment-13141481
]
stack commented on HBASE-4518:
--
This has not failed in ages. Can we close Gary?
TestServerCustomProtocol is flaky
-
Key: HBASE-4518
URL: https://issues.apache.org/jira/browse/HBASE-4518
Project: HBase
Issue Type: Bug
Components: coprocessors, test
Affects Versions: 0.92.0
Reporter: Gary Helmling
Fix For: 0.92.0
TestServerCustomProtocol has been showing some intermittent failures in
Jenkins due to what looks like region transitions.
Here is the most recent failure:
{noformat}
Results :
Failed tests:
testRowRange(org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol):
Results should contain region
test,bbb,1317332645939.aea9154349b9e0dc207e2e9476702763. for row 'bbb'
{noformat}
--
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
[jira] [Commented] (HBASE-4518) TestServerCustomProtocol is flaky
[
https://issues.apache.org/jira/browse/HBASE-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13141837#comment-13141837
]
Ted Yu commented on HBASE-4518:
---
I got the following when running test suite for latest TRUNK:
{code}
testRowRange(org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol)
Time elapsed: 0.057 sec FAILURE!
java.lang.AssertionError: Results should contain region
test,ccc,1320196026392.a22c262d449fa04ca4beeeb78afaf650. for row 'ccc'
at org.junit.Assert.fail(Assert.java:91)
at org.junit.Assert.assertTrue(Assert.java:43)
at
org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol.verifyRegionResults(TestServerCustomProtocol.java:328)
at
org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol.verifyRegionResults(TestServerCustomProtocol.java:320)
at
org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol.testRowRange(TestServerCustomProtocol.java:220)
{code}
TestServerCustomProtocol is flaky
-
Key: HBASE-4518
URL: https://issues.apache.org/jira/browse/HBASE-4518
Project: HBase
Issue Type: Bug
Components: coprocessors, test
Affects Versions: 0.92.0
Reporter: Gary Helmling
Fix For: 0.92.0
TestServerCustomProtocol has been showing some intermittent failures in
Jenkins due to what looks like region transitions.
Here is the most recent failure:
{noformat}
Results :
Failed tests:
testRowRange(org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol):
Results should contain region
test,bbb,1317332645939.aea9154349b9e0dc207e2e9476702763. for row 'bbb'
{noformat}
--
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
[jira] [Commented] (HBASE-4518) TestServerCustomProtocol is flaky
[
https://issues.apache.org/jira/browse/HBASE-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13141849#comment-13141849
]
Gary Helmling commented on HBASE-4518:
--
I just tried and am still able to trigger failures locally as well:
{noformat}
Running org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol
Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 25.045 sec
FAILURE!
Results :
Failed tests:
testRowRange(org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol):
Results should contain region
test,bbb,1320200292803.20c8a68e32824178b128060aff59386d. for row 'bbb'
{noformat}
I'll dig into it tonight.
TestServerCustomProtocol is flaky
-
Key: HBASE-4518
URL: https://issues.apache.org/jira/browse/HBASE-4518
Project: HBase
Issue Type: Bug
Components: coprocessors, test
Affects Versions: 0.92.0
Reporter: Gary Helmling
Fix For: 0.92.0
Attachments:
org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol-output.txt,
org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol.txt
TestServerCustomProtocol has been showing some intermittent failures in
Jenkins due to what looks like region transitions.
Here is the most recent failure:
{noformat}
Results :
Failed tests:
testRowRange(org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol):
Results should contain region
test,bbb,1317332645939.aea9154349b9e0dc207e2e9476702763. for row 'bbb'
{noformat}
--
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
