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 AE85A200BBD for ; Tue, 25 Oct 2016 03:09:02 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id AD223160B00; Tue, 25 Oct 2016 01:09:02 +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 01BFE160AEB for ; Tue, 25 Oct 2016 03:09:01 +0200 (CEST) Received: (qmail 83039 invoked by uid 500); 25 Oct 2016 01:09:01 -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 83028 invoked by uid 99); 25 Oct 2016 01:09:01 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Oct 2016 01:09:01 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id CBBDCC042F for ; Tue, 25 Oct 2016 01:09:00 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id ihxSY8DHdduY for ; Tue, 25 Oct 2016 01:09:00 +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 5ED565F478 for ; Tue, 25 Oct 2016 01:08:59 +0000 (UTC) Received: (qmail 82956 invoked by uid 99); 25 Oct 2016 01:08:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Oct 2016 01:08:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 66BF52C2A66 for ; Tue, 25 Oct 2016 01:08:58 +0000 (UTC) Date: Tue, 25 Oct 2016 01:08:58 +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: Tue, 25 Oct 2016 01:09:02 -0000 [ https://issues.apache.org/jira/browse/HELIX-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15603789#comment-15603789 ] ASF GitHub Bot commented on HELIX-636: -------------------------------------- Github user lei-xia commented on a diff in the pull request: https://github.com/apache/helix/pull/55#discussion_r84814968 --- Diff: helix-core/src/main/java/org/apache/helix/task/TaskDriver.java --- @@ -421,8 +428,7 @@ private void deleteJobFromScheduledQueue(final String queueName, final String jo // Delete the job from property store String jobPropertyPath = - Joiner.on("/") - .join(TaskConstants.REBALANCER_CONTEXT_ROOT, namespacedJobName); + Joiner.on("/").join(TaskConstants.REBALANCER_CONTEXT_ROOT, namespacedJobName); _propertyStore.remove(jobPropertyPath, AccessOption.PERSISTENT); --- End diff -- let us use removeJobContext() in the taskUtil? > 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)