You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Bharath Vissapragada (Jira)" <ji...@apache.org> on 2019/11/08 05:40:00 UTC

[jira] [Updated] (HBASE-23259) Ability to run mini cluster using pre-determined available random ports

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

Bharath Vissapragada updated HBASE-23259:
-----------------------------------------
    Status: Patch Available  (was: Open)

> Ability to run mini cluster using pre-determined available random ports
> -----------------------------------------------------------------------
>
>                 Key: HBASE-23259
>                 URL: https://issues.apache.org/jira/browse/HBASE-23259
>             Project: HBase
>          Issue Type: Sub-task
>          Components: test
>    Affects Versions: 3.0.0
>            Reporter: Bharath Vissapragada
>            Assignee: Bharath Vissapragada
>            Priority: Major
>
> As noted in the code reviews for HBASE-18095, we need the ability to run the mini-cluster using a pre-determined set of random (and available) port numbers. When I say pre-determined, I mean the test knows these ports even before starting the mini cluster. 
> In short, the workflow is something like,
> {noformat}
> List<Ports> ports = getRandomAvailablePorts();
> startMiniCluster(conf, ports);
> {noformat}
> The reason we need this is that certain configs introduced in HBASE-18095 depend on the ports on which the master is expected to serve the RPCs. While that is known for regular deployments (like 16000 for master etc), it is totally random in the mini cluster tests. So we need to know them before hand for templating out the configs. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)