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 DB1A4200D08 for ; Wed, 6 Sep 2017 23:30:12 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D9FF51609BA; Wed, 6 Sep 2017 21:30:12 +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 3518B1609D7 for ; Wed, 6 Sep 2017 23:30:12 +0200 (CEST) Received: (qmail 19651 invoked by uid 500); 6 Sep 2017 21:30:10 -0000 Mailing-List: contact jira-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@kafka.apache.org Delivered-To: mailing list jira@kafka.apache.org Received: (qmail 19640 invoked by uid 99); 6 Sep 2017 21:30:10 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Sep 2017 21:30:10 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 5A35D1A6B25 for ; Wed, 6 Sep 2017 21:30:10 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id AN6voA3FjBai for ; Wed, 6 Sep 2017 21:30:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id CF94C61034 for ; Wed, 6 Sep 2017 21:30:04 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6816FE06CF for ; Wed, 6 Sep 2017 21:30:03 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1AE142415D for ; Wed, 6 Sep 2017 21:30:02 +0000 (UTC) Date: Wed, 6 Sep 2017 21:30:02 +0000 (UTC) From: "Randall Hauch (JIRA)" To: jira@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KAFKA-5741) Prioritize threads in Connect distributed worker process MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 06 Sep 2017 21:30:13 -0000 [ https://issues.apache.org/jira/browse/KAFKA-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156062#comment-16156062 ] Randall Hauch commented on KAFKA-5741: -------------------------------------- Thanks for replying, [~ewencp]. After looking into this, it's not clear to me that this is an appropriate approach to take. Will investigate more whether this is actually a problem or simply a symptom of another issue. > Prioritize threads in Connect distributed worker process > -------------------------------------------------------- > > Key: KAFKA-5741 > URL: https://issues.apache.org/jira/browse/KAFKA-5741 > Project: Kafka > Issue Type: Improvement > Components: KafkaConnect > Affects Versions: 0.11.0.0 > Reporter: Randall Hauch > Priority: Critical > > Connect's distributed worker process uses the {{DistributedHerder}} to perform all administrative operations, including: starting, stopping, pausing, resuming, reconfiguring connectors; rebalancing; etc. The {{DistributedHerder}} uses a single threaded executor service to do all this work and to do it sequentially. If this thread gets preempted for any reason (e.g., connector tasks are bogging down the process, DoS, etc.), then the herder's membership in the group may be dropped, causing a rebalance. > This herder thread should be run at a much higher priority than all of the other threads in the system. -- This message was sent by Atlassian JIRA (v6.4.14#64029)