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 07188200C50 for ; Sat, 8 Apr 2017 11:08:58 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0249A160B96; Sat, 8 Apr 2017 09:08:58 +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 45FE9160B88 for ; Sat, 8 Apr 2017 11:08:57 +0200 (CEST) Received: (qmail 46059 invoked by uid 500); 8 Apr 2017 09:08:56 -0000 Mailing-List: contact users-help@nifi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@nifi.apache.org Delivered-To: mailing list users@nifi.apache.org Received: (qmail 46049 invoked by uid 99); 8 Apr 2017 09:08:56 -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; Sat, 08 Apr 2017 09:08:56 +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 CE0B2C0D33 for ; Sat, 8 Apr 2017 09:08:55 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.102 X-Spam-Level: X-Spam-Status: No, score=-0.102 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=talktalk.net 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 1D3BU4ZnTzsm for ; Sat, 8 Apr 2017 09:08:53 +0000 (UTC) Received: from smtp-out-5.talktalk.net (smtp-out-5.talktalk.net [62.24.135.69]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 403185FDFB for ; Sat, 8 Apr 2017 09:08:53 +0000 (UTC) Received: from [192.168.100.100] ([79.69.160.44]) by smtp.talktalk.net with SMTP id wmMRcgdJRHGLwwmMRcU10B; Sat, 08 Apr 2017 10:08:47 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=talktalk.net; s=1605; t=1491642527; bh=jfrj5bDmvwQVy60pIYZZMmpWg/vglyk3eGKQ+9P/RVA=; h=From:Subject:To:References:Date:In-Reply-To; b=CAE8JOV5Zm4/Su5RuLZHHjb/6MLdbTUEDieZonDzUH4Q1n5GEFVwFePiqzvs0VnWY 15vG3bvOUeDaq1Ihz09GHb2jckBiSDq0xrTdcjTQtBj7RgDBWxx7I55gb0m5OZXnCI Dny79JnZAQ+tvi5NET6bBzdSysJ7htyB50w7IX6g= X-Originating-IP: [79.69.160.44] X-Spam: 0 X-OAuthority: v=2.2 cv=dsCZMBo4 c=1 sm=1 tr=0 a=UcoSuHY2SsTMFQk8QA/I9g==:117 a=UcoSuHY2SsTMFQk8QA/I9g==:17 a=IkcTkHD0fZMA:10 a=nN7BH9HXAAAA:8 a=rYGDFu4kXt1kA1H1SL8A:9 a=AaxkZ-2NGn3FDH50:21 a=O3pv4kiKo6LYmjAO:21 a=QEXdDO2ut3YA:10 From: Stephen-Talk Subject: Re: Is it possible to dynamically spawn a Processor Group ? To: users@nifi.apache.org References: <4b6252be-d427-c2a3-5f3b-2ded26566bd4@talktalk.net> <785c3bb9-9a15-b22d-85d2-e795111d3b15@talktalk.net> Message-ID: <66600a16-f3f2-f35c-69fd-8eb7c3b905de@talktalk.net> Date: Sat, 8 Apr 2017 10:08:44 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfMFKXWrCWVigOOqX3Q1rUyiqhfCL4c5dLl57tLsDpMm9dyumQ1YrfGwH/X1HoMq9LMA6ITe6609jz9fUwcp7+qyKssHHMkKc+CujtjPEscL3VcRv/4VF TuuTVZ5GZFBhNzBdm40/lfb1Jl3OYKjEV/GQxm1xTHU+MRB5CYaKTTzEdX402c3NlCa1UWgzpM8/vw== archived-at: Sat, 08 Apr 2017 09:08:58 -0000 Jeff, You hit the nail on the head. My "Concurrent Tasks" is set to 1. I shall have a fiddle with the numbers for both the threads, which is set to 10 and the concurrent tasks, and see if it helps. Thanks for your valuable assitance. Have a great weekend... Stephen On 07/04/2017 18:58, Jeff wrote: > Stephen, > > It would be good to see screenshots of your flow, and get a little more > information about your NiFi installation to help you get better > throughput of your data. Are you running NiFi as a single node? At > which processor in your flow are you noticing the queues backing up? In > the global settings menu, under "Controller Settings", what is "Maximum > Timer Driven Thread Count" set to? On your "MyImportProcessor" config, > on the "Scheduling" tab, what is "Concurrent Tasks" set to? > > In general terms, having more threads available to a processor means > you'll get greater throughput of the data, provided that your IO > configuration (disk read/write speed) can keep up. The number of > threads that NiFi is configured to use are made available to processors > as flowfiles are presented to a processor via an incoming queue based on > the number of concurrent tasks for which a processor is configured. > > In the UI, you can see how many tasks are currently being executed by > each processor, which will never be more than the "Maximum Timer Driven > Thread Count" (for processors configured to use timer-based scheduling). > > If you are experience backpressure on the incoming queue for > "MyImportProcessor", try increasing the number of "Concurrent Tasks" > available to that processor, and you may also want to increase the > number of "Maximum Timer Driven Tread Count". > > These are just some of the basics of getting more throughput in NiFi. > > On Thu, Apr 6, 2017 at 4:25 PM Stephen-Talk > > > wrote: > > Thanks for the quick reply. > > Yes, that is quite correct. > The scenario is the following: > > The input flow is a "GetFile" process that collects csv files > (>100,000 lines) which in turn queues the file and parses each line to a > locally built processor (MyImportProcessor say) that submits them via > the REST API to a Drupal website. > The process works fine, but it is very slow, and would like to speed it > up by splitting the csv file into chunks so that it can then spawn > "MyImportProcessor" as many times as required. > > > On 06/04/2017 20:47, Jeff wrote: > > Hello Stephen, > > > > It's possible to watch the status of NiFi, and upon observing a > > particular status in which you're interested, you can use the REST API > > to create new processor groups. You'd also have to populate that > > processor group with processors and other components. Based on the > > scenario you mentioned, though, it sounds like you are looking at > being > > able to scale up available processing (via more concurrent threads, or > > more nodes in a cluster) once a certain amount of data is queued > up and > > waiting to be processed, rather than adding components to the existing > > flow. Is that correct? > > > > On Thu, Apr 6, 2017 at 3:30 PM Stephen-Talk > > > >> > > wrote: > > > > Hi, I am just a Nifi Inquisitor, > > > > Is it, or could it be possible to Dynamically spawn a > "Processor Group" > > when the input flow reaches a certain threshold. > > > > Thanking you in aniticipation. > > Stephen > > >