You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@apache.org by Allen Wittenauer <aw...@effectivemachines.com> on 2017/06/23 03:56:07 UTC
Tons of nodes offline/broken
Hi all.
Just noticed that there are a ton of H nodes offline and qnode3 is failing builds because it is out of space.
Thanks.
Re: Tons of nodes offline/broken
Posted by Allen Wittenauer <aw...@effectivemachines.com>.
> On Jun 23, 2017, at 10:03 AM, Daniel Pono Takamori <po...@apache.org> wrote:
>
> Looks like this is relatively adaptable to deploying for other builds,
> if not generalizable to use in a cron. Thanks a bunch!
You're welcome. For those that have never seen Apache Yetus activate it's cleanup mode, here's a sample:
https://builds.apache.org/job/PreCommit-YETUS-Build/589/consoleFull
Re: Tons of nodes offline/broken
Posted by Daniel Pono Takamori <po...@apache.org>.
Looks like this is relatively adaptable to deploying for other builds,
if not generalizable to use in a cron. Thanks a bunch!
On Fri, Jun 23, 2017 at 9:23 AM, Allen Wittenauer
<aw...@effectivemachines.com> wrote:
>
>> On Jun 23, 2017, at 7:11 AM, Allen Wittenauer <aw...@effectivemachines.com> wrote:
>>
>>
>>> On Jun 22, 2017, at 11:12 PM, Daniel Pono Takamori <po...@apache.org> wrote:
>>>
>>> Docker filled up /var/ so I cleared out the old images. Going to work
>>> on making sure docker isn't a disk hog in the future.
>>
>>
>> ha. Kind of ironic that my Yetus job failed... it would have cleaned it up. I guess we should probably make a way to run Yetus' docker cleanup code independently. We could then schedule a job to run every X days to do the cleanup automatically.
>
>
> Filed YETUS-523 with a patch to add a 'docker-cleanup' command that just triggers Yetus' Docker cleanup code.
Re: Tons of nodes offline/broken
Posted by Allen Wittenauer <aw...@effectivemachines.com>.
> On Jun 23, 2017, at 7:11 AM, Allen Wittenauer <aw...@effectivemachines.com> wrote:
>
>
>> On Jun 22, 2017, at 11:12 PM, Daniel Pono Takamori <po...@apache.org> wrote:
>>
>> Docker filled up /var/ so I cleared out the old images. Going to work
>> on making sure docker isn't a disk hog in the future.
>
>
> ha. Kind of ironic that my Yetus job failed... it would have cleaned it up. I guess we should probably make a way to run Yetus' docker cleanup code independently. We could then schedule a job to run every X days to do the cleanup automatically.
Filed YETUS-523 with a patch to add a 'docker-cleanup' command that just triggers Yetus' Docker cleanup code.
Re: Tons of nodes offline/broken
Posted by Allen Wittenauer <aw...@effectivemachines.com>.
> On Jun 22, 2017, at 11:12 PM, Daniel Pono Takamori <po...@apache.org> wrote:
>
> Docker filled up /var/ so I cleared out the old images. Going to work
> on making sure docker isn't a disk hog in the future.
ha. Kind of ironic that my Yetus job failed... it would have cleaned it up. I guess we should probably make a way to run Yetus' docker cleanup code independently. We could then schedule a job to run every X days to do the cleanup automatically.
Re: Tons of nodes offline/broken
Posted by Daniel Pono Takamori <po...@apache.org>.
Docker filled up /var/ so I cleared out the old images. Going to work
on making sure docker isn't a disk hog in the future.
Sent an e-mail to Y! about getting the H nodes kicked, thanks for
letting us know.
On Thu, Jun 22, 2017 at 8:56 PM, Allen Wittenauer
<aw...@effectivemachines.com> wrote:
>
> Hi all.
>
> Just noticed that there are a ton of H nodes offline and qnode3 is failing builds because it is out of space.
>
> Thanks.