[ 
https://issues.apache.org/jira/browse/HBASE-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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

        

Reply via email to