You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/07/01 20:42:00 UTC

[jira] [Updated] (HBASE-14075) HBaseClusterManager should use port(if given) to find pid

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

Andrew Kyle Purtell updated HBASE-14075:
----------------------------------------
      Assignee:     (was: Yu Li)
    Resolution: Abandoned
        Status: Resolved  (was: Patch Available)

> HBaseClusterManager should use port(if given) to find pid
> ---------------------------------------------------------
>
>                 Key: HBASE-14075
>                 URL: https://issues.apache.org/jira/browse/HBASE-14075
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Yu Li
>            Priority: Minor
>         Attachments: HBASE-14075-master_v2.patch, HBASE-14075-master_v3.patch, HBASE-14075-master_v4.patch, HBASE-14075-master_v5.patch, HBASE-14075-master_v6.patch, HBASE-14075-master_v7.patch, HBASE-14075.patch
>
>
> This issue is found while we run ITBLL in distributed cluster. Our testing env is kind of special that we run multiple regionserver instance on a single physical machine, so {noformat}ps -ef | grep proc_regionserver{noformat} will return more than one line, thus cause the tool might check/kill the wrong process
> Actually in HBaseClusterManager we already introduce port as a parameter for methods like isRunning, kill, etc. So the only thing to do here is to get pid through port if port is given



--
This message was sent by Atlassian Jira
(v8.20.10#820010)