Return-Path: X-Original-To: apmail-nifi-users-archive@minotaur.apache.org Delivered-To: apmail-nifi-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 94E3118EB3 for ; Tue, 13 Oct 2015 21:06:58 +0000 (UTC) Received: (qmail 8526 invoked by uid 500); 13 Oct 2015 21:06:52 -0000 Delivered-To: apmail-nifi-users-archive@nifi.apache.org Received: (qmail 8506 invoked by uid 500); 13 Oct 2015 21:06:52 -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 8496 invoked by uid 99); 13 Oct 2015 21:06:52 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Oct 2015 21:06:52 +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 D9C5F1A2161 for ; Tue, 13 Oct 2015 21:06:51 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.999 X-Spam-Level: ** X-Spam-Status: No, score=2.999 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id CcQSZw7Q7XXf for ; Tue, 13 Oct 2015 21:06:42 +0000 (UTC) Received: from mail1.bemta8.messagelabs.com (mail1.bemta8.messagelabs.com [216.82.243.203]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 2BFFE4357F for ; Tue, 13 Oct 2015 21:06:42 +0000 (UTC) Received: from [216.82.241.196] by server-11.bemta-8.messagelabs.com id 0C/0A-22779-7527D165; Tue, 13 Oct 2015 21:06:31 +0000 X-Env-Sender: Chakrader.Dewaragatla@lifelock.com X-Msg-Ref: server-3.tower-46.messagelabs.com!1444770390!36611485!1 X-Originating-IP: [208.99.166.84] X-StarScan-Received: X-StarScan-Version: 6.13.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6915 invoked from network); 13 Oct 2015 21:06:31 -0000 Received: from unknown (HELO mail.lifelock.com) (208.99.166.84) by server-3.tower-46.messagelabs.com with AES128-SHA encrypted SMTP; 13 Oct 2015 21:06:31 -0000 From: Chakrader Dewaragatla To: "users@nifi.apache.org" Subject: Re: site to site setup - Remore instance not configured Thread-Topic: site to site setup - Remore instance not configured Thread-Index: AQHRBUiqq8U6X2D91kC0lMuG6OPQgZ5p632A Date: Tue, 13 Oct 2015 21:06:29 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.10.5.254] Content-Type: multipart/alternative; boundary="_000_D2429FB8F07chakraderdewaragatlalifelockcom_" MIME-Version: 1.0 --_000_D2429FB8F07chakraderdewaragatlalifelockcom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Thanks Matthew it worked, no errors this time. As noted below, we would like to consume http data on primary node and send= it back to cluster for processing. I have site to site setup with http listener(on primary node) =97> Input p= ort =97> SitetoSite to NCM cluster instance =97> putfile =97> S3upload . Does my setup achieve the purpose? Data movement from http listener to input port is not working and no errors= reported. Site-to-site admin document has limited information to understand. Thanks, -Chakri From: Matthew Clarke > Reply-To: "users@nifi.apache.org" > Date: Monday, October 12, 2015 at 4:49 PM To: "users@nifi.apache.org" > Subject: Re: site to site setup - Remore instance not configured For Site to Site properties the input socket host is optional. When it is c= onfigured it should be set the hostname or IP of the the system the NiFi in= stance is running on. you must however configure an input socket port on e= very instance. This includes all nodes and the NCM. If you cluster is conf= igured to run securely (HTTPS), you should also have input secure set to tr= ue. Make sure you have the ports you use open in the firewalls between sys= tems. On Oct 12, 2015 7:41 PM, "Chakrader Dewaragatla" > wrote: Hi =96 I have a use case to collect http post requests on a nifi-clustered = setup. My cluster has three nodes. Ncm =97> Slave 1 (Primary) =97> Slave 2. I would like to setup a http listener on primary node and establish site to= site connection to the same cluster for further processing data. So http p= ayload receive as follows http post =97> Slave 1 (ListenHttp )=97 > (Site-to-site) =97 > NCM (put f= ile) and (S3 upload) (I assume this data process by two slaves nodes) I have following error at site-to-site setup : Remote instance Is not conf= igured for site-to-site communications at this time. I followed the admin doc to set the properties, as follows (on slaves). # Site to Site properties nifi.remote.input.socket.host=3D10.83.14.59 (NCM ip) nifi.remote.input.socket.port=3D nifi.remote.input.secure=3Dfalse Any thoughts? Thanks, -Chakri ________________________________ The information contained in this transmission may contain privileged and c= onfidential information. It is intended only for the use of the person(s) n= amed above. If you are not the intended recipient, you are hereby notified = that any review, dissemination, distribution or duplication of this communi= cation is strictly prohibited. If you are not the intended recipient, pleas= e contact the sender by reply email and destroy all copies of the original = message. ________________________________ ________________________________ The information contained in this transmission may contain privileged and c= onfidential information. It is intended only for the use of the person(s) n= amed above. If you are not the intended recipient, you are hereby notified = that any review, dissemination, distribution or duplication of this communi= cation is strictly prohibited. If you are not the intended recipient, pleas= e contact the sender by reply email and destroy all copies of the original = message. ________________________________ --_000_D2429FB8F07chakraderdewaragatlalifelockcom_ Content-Type: text/html; charset="Windows-1252" Content-ID: <7094EDBBB8481F41A9666B92E6F6D8E8@lifelock.com> Content-Transfer-Encoding: quoted-printable
Thanks Matthew it worked, no errors this time. 
As noted below, we would like to consume http data on primary node and= send it back to cluster for processing. 

I have site to site setup with http listener(on primary node) =97> =  Input port  =97> SitetoSite to NCM cluster instance  =97= > putfile =97> S3upload . 
Does my setup achieve the purpose?

Data movement from http listener to input port is not working and no e= rrors reported.  

Site-to-site admin document has limited information to understand.&nbs= p;

Thanks,
-Chakri

From: Matthew Clarke <matt.clarke.138@gmail.com>
Reply-To: "users@nifi.apache.org" <users@nifi.apache.org>
Date: Monday, October 12, 2015 at 4= :49 PM
To: "users@nifi.apache.org" <users@nifi.apache.org>
Subject: Re: site to site setup - R= emore instance not configured

For Site to Site properties the input socket host is optiona= l. When it is configured it should be set the hostname or IP of the the sys= tem the NiFi instance is running on.  you must however configure an in= put socket port on every instance. This includes all nodes and the NCM.  If you cluster is configured to run = securely (HTTPS), you should also have input secure set to true.  Make= sure you have the ports you use open in the firewalls between systems.

On Oct 12, 2015 7:41 PM, "Chakrader Dewarag= atla" <Chakra= der.Dewaragatla@lifelock.com> wrote:
Hi =96 I have = a use case to collect http post requests on a nifi-clustered setup. My clus= ter has three nodes.

Ncm =97> Sl= ave 1 (Primary)
    =      =97> Slave 2.

I would like t= o setup a http listener on primary node and establish site to site connecti= on to the same cluster for further processing data. So http payload receive= as follows 

  http po= st =97> Slave 1 (ListenHttp )=97 > (Site-to-site) =97 > NCM (put f= ile) and (S3 upload) (I assume this data process by two slaves nodes)  = ;   

I have followi= ng error at site-to-site setup :  Remote instance Is not configured for site-to-site communications = at this time.

I followed the= admin doc to set the properties, as follows (on slaves).

# Site to Site pro= perties

nifi.remote.input.= socket.host=3D10.83.14.59    (NCM ip)

nifi.remote.input.= socket.port=3D

nifi.remote.input.= secure=3Dfalse



Any thoughts? 


Thanks,

-Chakri

The information contained in this transmission may contain privileged and c= onfidential information. It is intended only for the use of the person(s) n= amed above. If you are not the intended recipient, you are hereby notified = that any review, dissemination, distribution or duplication of this communication is strictly prohibited. = If you are not the intended recipient, please contact the sender by reply e= mail and destroy all copies of the original message.
The information contained in this transmission may contain privileged and c= onfidential information. It is intended only for the use of the person(s) n= amed above. If you are not the intended recipient, you are hereby notified = that any review, dissemination, distribution or duplication of this communication is strictly prohibited. = If you are not the intended recipient, please contact the sender by reply e= mail and destroy all copies of the original message.
--_000_D2429FB8F07chakraderdewaragatlalifelockcom_--