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 815CF200D3E for ; Thu, 16 Nov 2017 08:08:31 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 7E5B3160BE6; Thu, 16 Nov 2017 07:08:31 +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 9C5AD160BE5 for ; Thu, 16 Nov 2017 08:08:30 +0100 (CET) Received: (qmail 49080 invoked by uid 500); 16 Nov 2017 07:08:29 -0000 Mailing-List: contact dev-help@nifi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@nifi.apache.org Delivered-To: mailing list dev@nifi.apache.org Received: (qmail 49068 invoked by uid 99); 16 Nov 2017 07:08:29 -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; Thu, 16 Nov 2017 07:08:29 +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 5AC02C9517 for ; Thu, 16 Nov 2017 07:08:28 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.879 X-Spam-Level: * X-Spam-Status: No, score=1.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=fucs.org 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 3DfQDr6mKyw9 for ; Thu, 16 Nov 2017 07:08:26 +0000 (UTC) Received: from mail-lf0-f47.google.com (mail-lf0-f47.google.com [209.85.215.47]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id B26ED5FCFB for ; Thu, 16 Nov 2017 07:08:25 +0000 (UTC) Received: by mail-lf0-f47.google.com with SMTP id f125so28932041lff.4 for ; Wed, 15 Nov 2017 23:08:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fucs.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=cGt0jaeRclqszk2+Q+Ft41oEywzMtEwwWgoSHX3K2jo=; b=Dijd+mBhUSMdsP9bxKS3dUDoTl91dktTlM/BJ/HAI6sc6EUbThnTNsfcg34jAsv9cD /GVUm1OCdrqNlU7o7ukMF6+nS4cuhXcV2+ngE9gUgLqIMEEfeW0wlUq/GEeTcZDJ0M8Z e96C3HhMzgcapwCr8NUMX83KDj7i7lFirf0Mw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=cGt0jaeRclqszk2+Q+Ft41oEywzMtEwwWgoSHX3K2jo=; b=NzSqnpGV0GGa+yNhuLCQOcKNMmXBzYyiPRHQa/osYTx8T6JjFgQPpiflVrYDHbAU8I JJbxaElvedb0jsBbRtEeZwrJfsIKujnJphKDxqUKb9da4W/76CeAfjrdqyTGiTI885yV jnbtPrMdiI3IWEePF9XdXORw9pL1snM6JTbSYGz3tEDXXvuSgBxiI50V4gs1+GY7y4LH OHoSxFgTHMh1/hipFrT56IqbScKt2MZqGdanRcr8hiYwPD8/bzdPC2QqFnFauv9i+/63 DxOD+N4PN24yHzvudSgdntfaJTwTlPjRBd4MBNk7b4kLpscOh2tlsy30kCRLxYjpXk04 pQrQ== X-Gm-Message-State: AJaThX5DlOY8rVrMq7odJRNl910GzxI1SFiJz7WvTCu0WmIeAKYgBs2i 7GinM8mxzdBpDsr9kRhJaN3a6TdfrzU= X-Google-Smtp-Source: AGs4zMbQTSO74kz+SanXaoyAmN9kBgpmdBFQc0TENELT83idv8R3TVCJGX2xMDdx6GFgbN2KKk79vg== X-Received: by 10.25.193.145 with SMTP id r139mr180874lff.47.1510816104909; Wed, 15 Nov 2017 23:08:24 -0800 (PST) Received: from mail-lf0-f46.google.com (mail-lf0-f46.google.com. [209.85.215.46]) by smtp.gmail.com with ESMTPSA id v12sm110072ljd.15.2017.11.15.23.08.24 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Nov 2017 23:08:24 -0800 (PST) Received: by mail-lf0-f46.google.com with SMTP id r135so28961893lfe.5 for ; Wed, 15 Nov 2017 23:08:24 -0800 (PST) X-Received: by 10.46.89.69 with SMTP id n66mr273792ljb.26.1510816104544; Wed, 15 Nov 2017 23:08:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.46.70.9 with HTTP; Wed, 15 Nov 2017 23:08:23 -0800 (PST) X-Originating-IP: [125.7.24.158] In-Reply-To: References: From: Andre Date: Thu, 16 Nov 2017 18:08:23 +1100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: The mystery of ListSFTP that stops working To: dev@nifi.apache.org Content-Type: multipart/alternative; boundary="94eb2c073aec3b90b2055e144946" archived-at: Thu, 16 Nov 2017 07:08:31 -0000 --94eb2c073aec3b90b2055e144946 Content-Type: text/plain; charset="UTF-8" Hey Mark, Changing the scheduling doesn't seem to make a difference. I have noticed some instances where a nifi.sh dump causes a switch of the primary node and that unleashes the stuck processor but still not clear why it happens. I took a thread dump of the primary node while the thing was happening. Will upload to gist soon. Cheers On Thu, Nov 16, 2017 at 2:07 AM, Mark Payne wrote: > Andre, > > So I am guessing that backpressure is not an issue then if you're not > seeing it run :) > Have you tried reducing the scheduling period from 5 mins to something > like 5 seconds? > Of course, you may not want to actually be running it every 5 seconds in a > production environment, > but I am curious if it would cause it to start running or not... > > > On Nov 15, 2017, at 10:02 AM, Andre wrote: > > > > Mark, > > > > Timer driven, Primary Node, 5 min > > Yield is set to 1 sec > > Backpressure = 10k flows or 1GB > > nifi.administrative.yield.duration=30 sec > > > > Cheers > > > > > > On Thu, Nov 16, 2017 at 1:32 AM, Mark Payne > wrote: > > > >> Hey Andre, > >> > >> I have not seen this personally. Can you share how you have the > Scheduling > >> Tab configured? > >> Is it set to Timer-Driven with a period of "0 secs"? Also, what is the > >> Yield Duration set to? > >> Is there any backpressure configured on any of the outbound connections? > >> Additionally, what is the value of the "nifi.administrative.yield. > duration" > >> property in nifi.properties? > >> > >> Sorry - I know that's a barrage of questions. Hopefully it's something > >> easy that's just being overlooked, though :) > >> > >> -Mark > >> > >>> On Nov 15, 2017, at 4:58 AM, Andre wrote: > >>> > >>> Folks, > >>> > >>> Has anyone ever seen a situation where ListSFTP simply stops working? > >>> > >>> I have observed a few occurrences of seems to be some weird bug. > >>> > >>> Symptoms are: > >>> > >>> - Processor looks healthy (i.e. no bulletins) > >>> - State is stalled (i.e. no changes to new files or timestamps) > >>> - No signs of a stuck thread (i.e. processor doesn't display a thread > >> count) > >>> - UI displays processor "Task count = 0/0" > >>> - Neither stopping > starting nor stopping > disabling > enabling > > >>> starting processor seems to make a difference. > >>> > >>> Has anyone seen this? > >>> > >>> Cheers > >> > >> > > --94eb2c073aec3b90b2055e144946--