[jira] [Commented] (HBASE-6632) [0.92 UNIT TESTS] testCreateTableRPCTimeOut sets rpc timeout to 1500ms and leaves it (testHundredsOfTable fails w/ 1500ms timeout)

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on HBASE-6632:
-------------------------------

Integrated in HBase-0.94 #414 (See [https://builds.apache.org/job/HBase-0.94/414/])
    HBASE-6632 [0.92 UNIT TESTS] testCreateTableRPCTimeOut sets rpc timeout to 1500ms and leaves it (testHundredsOfTable fails w/ 1500ms timeout) (Revision 1375898)

     Result = SUCCESS
stack : 
Files : 
* /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/client/TestAdmin.java

                
> [0.92 UNIT TESTS] testCreateTableRPCTimeOut sets rpc timeout to 1500ms and leaves it (testHundredsOfTable fails w/ 1500ms timeout)
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-6632
>                 URL: https://issues.apache.org/jira/browse/HBASE-6632
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.92.2, 0.94.2
>
>         Attachments: 6632-trunk.txt, 6632.txt
>
>
> I see that in 0.92 #502 and #501 that TestAdmin.testHundredsOfTable fails because socket times out after 1500ms.  I see in TestAdmin that before this test runs, testCreateTableRPCTimeOut sets the socket timeout to 1500 and then does not set it back.  Maybe the obnoxious testHundredsOfTable will pass more often if it has the default rpc timeout.

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