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

[jira] [Resolved] (HBASE-22852) hbase nightlies leaking gpg-agents

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

Sean Busbey resolved HBASE-22852.
---------------------------------
    Fix Version/s: 2.1.7
                   2.2.1
                   2.3.0
                   3.0.0
       Resolution: Fixed

> hbase nightlies leaking gpg-agents
> ----------------------------------
>
>                 Key: HBASE-22852
>                 URL: https://issues.apache.org/jira/browse/HBASE-22852
>             Project: HBase
>          Issue Type: Bug
>          Components: build
>            Reporter: Allen Wittenauer
>            Assignee: Rushabh S Shah
>            Priority: Major
>             Fix For: 3.0.0, 2.3.0, 2.2.1, 2.1.7
>
>
> FYI, just triggered yetus master, which includes code to find and kill long-running processes still attached to the Jenkins workspace directory.  It came up with this:
> https://builds.apache.org/view/S-Z/view/Yetus/job/yetus-github-multibranch/job/master/134/console
> {code}
> USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
>  jenkins    752  0.0  0.0  93612   584 ?        Ss   Aug12   0:00 gpg-agent --homedir /home/jenkins/jenkins-slave/workspace/HBase_Nightly_HBASE-20952/downloads-hadoop-2/.gpg --use-standard-socket --daemon
>  Killing 752 ***
> {code}
> (repeat 10s of times, which slightly different dates, pids, versions, etc)
> Also, be aware that any other process running on the node (such as the other executor) has extremely easy access to whatever gpg creds you are using...



--
This message was sent by Atlassian Jira
(v8.3.2#803003)