[jira] Updated: (HBASE-1271) Allow multiple tests to run on one machine

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

     [ https://issues.apache.org/jira/browse/HBASE-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Evgeny Ryabitskiy updated HBASE-1271:
-------------------------------------

    Attachment: HBASE-1271.patch

Fixing to region server:

 * Previously all info servers for HRS were bind on one port, so it was imposible to start multiple HRS with info servers on one node
 * Now if port is in use, info server binds on next port (port++)

{code}
09/04/24 14:01:54 INFO regionserver.HRegionServer: Faild binding http info server to port: 60030
 09/04/24 14:01:54 INFO regionserver.HRegionServer: Attempt to bind http info server to port: 60031
{code}

Fixing to test framework:

 * LocalHBaseCluster. If Masters port is busy... try port++
 * MiniZooKeeperCluster. Same thing if port is busy try next one.


Still need to check working of MiniZooKeeperCluster. Not shure for my changes.


How I was testing my changes:

 * Run 3 HRS and master on one laptop (info server is turned on), everything is working... jsp GUI for master show links for all HRS info servers

 * Run ant test task with all tests... + running at same time JUnits... no colisions
 * Run 2 ant tasks with all tests at same time. No collisions.

> Allow multiple tests to run on one machine
> ------------------------------------------
>
>                 Key: HBASE-1271
>                 URL: https://issues.apache.org/jira/browse/HBASE-1271
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: test
>            Reporter: Nitay Joffe
>            Assignee: Evgeny Ryabitskiy
>            Priority: Minor
>             Fix For: 0.20.0
>
>         Attachments: HBASE-1271.patch
>
>
> Currently, if we try to run two tests on one machine (e.g. in two checkouts) the second one will fail because its servers won't be able to bind to ports. We should use random ports in our servers in the tests to fix this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.