Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 9F6BE200BBD for ; Tue, 25 Oct 2016 00:39:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 9E145160AEB; Mon, 24 Oct 2016 22:39:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E7619160B00 for ; Tue, 25 Oct 2016 00:39:04 +0200 (CEST) Received: (qmail 11679 invoked by uid 500); 24 Oct 2016 22:39:04 -0000 Mailing-List: contact commits-help@helix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@helix.apache.org Delivered-To: mailing list commits@helix.apache.org Received: (qmail 11670 invoked by uid 99); 24 Oct 2016 22:39:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Oct 2016 22:39:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 91474C0CA4 for ; Mon, 24 Oct 2016 22:39:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -7.019 X-Spam-Level: X-Spam-Status: No, score=-7.019 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id y7e0zN3RC1Qy for ; Mon, 24 Oct 2016 22:39:01 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id 33D435FC1F for ; Mon, 24 Oct 2016 22:39:00 +0000 (UTC) Received: (qmail 10919 invoked by uid 99); 24 Oct 2016 22:38:59 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Oct 2016 22:38:59 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 481FB2C1F5A for ; Mon, 24 Oct 2016 22:38:59 +0000 (UTC) Date: Mon, 24 Oct 2016 22:38:59 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: commits@helix.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HELIX-636) JobQueue capacity is full due to job not cleaned up MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 24 Oct 2016 22:39:05 -0000 [ https://issues.apache.org/jira/browse/HELIX-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15603450#comment-15603450 ] ASF GitHub Bot commented on HELIX-636: -------------------------------------- GitHub user dasahcc opened a pull request: https://github.com/apache/helix/pull/55 [HELIX-636] Add Java API and REST API for clean up JobQueue Since JobQueue never cleans up the jobs in the final stage (FAILED, COMPLETED, ABORTED), JobQueue will reach the capacity limit when jobs keep adding in. 1. Current fix will be adding an API in TaskDriver to clean up the final statge. To clean up the jobs in the final states, call the API cleanUpJobQueue() 2. As JobQueue is dynamic queue running, JobQueue should not be failed due to job failed threshold. Fix it with check whether failing due to other jobs fail is for JobQueue or generic workflow. You can merge this pull request into a Git repository by running: $ git pull https://github.com/dasahcc/helix helix-0.6.x Alternatively you can review and apply these changes as the patch at: https://github.com/apache/helix/pull/55.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #55 ---- commit 927ad62eb17edeff255866c38d3b2aa7a4eb5da7 Author: Junkai Xue Date: 2016-10-24T22:34:29Z Add Java API and REST API for clean up JobQueue To clean up the jobs in the final states, provide a Java API and REST API in helix. ---- > JobQueue capacity is full due to job not cleaned up > --------------------------------------------------- > > Key: HELIX-636 > URL: https://issues.apache.org/jira/browse/HELIX-636 > Project: Apache Helix > Issue Type: Bug > Components: helix-core > Affects Versions: 0.6.4 > Reporter: Junkai Xue > Assignee: Junkai Xue > Fix For: 0.6.x > > > Since JobQueue never cleans up the jobs in the final stage (FAILED, COMPLETED, ABORTED), JobQueue will reach the capacity limit when jobs keep adding in. > Fix: Current fix will be adding an API in TaskDriver to clean up the final statge. -- This message was sent by Atlassian JIRA (v6.3.4#6332)