Mailing-List: contact users-help@nifi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@nifi.apache.org
From: Mark Payne <markap14@hotmail.com>
To: "users@nifi.apache.org" <users@nifi.apache.org>
Subject: Re: Clustering Best Practices?
Thread-Topic: Clustering Best Practices?
Thread-Index: AQHSucV7uZ8jtNLb10u+SqpCMK5feaHONkqA
Date: Thu, 20 Apr 2017 12:52:16 +0000
Message-ID: <BLUPR15MB04358BD7B19815F18A61AF82CE1B0@BLUPR15MB0435.namprd15.prod.outlook.com>
References: <CAEqJCe0hu4KfpxMe=pCu+PC3-CvqFuy2G+FB8VnTaf2DO+Upww@mail.gmail.com>
In-Reply-To: <CAEqJCe0hu4KfpxMe=pCu+PC3-CvqFuy2G+FB8VnTaf2DO+Upww@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1;SN1NAM04HT075;5:q1ZPWPjdeQ/DSCpbC16nDUeDbnVhpBXR7g0oD9L2AuAW7izOUcauvSDZ7gtQkcEXqaRZ0m6MNiVuldm9s9R+b7wh+2tKoghyILgw38ZQttIMUP+YxyPFtGBJYWR1LtIqxpZALra0OXZRPfV731k3FQ==;24:wQCeJt+5WkHpvd9NfwfCVLctZrPiOsPRe6GOQZq5kVlMXmHH0UpSuFLsndsDyT86nacub2q17I/TAG3ISiiDktU8c4d8mCXjVhosSR+V/1U=;7:V5zK5FAwl6Lyc5A51INFifXLf74s9XM6jFKO7CNv/0whqAFWDirROIIqCSicDOSsy1La1Lq9ZUmam91XAE8B7s2yjsErgUPn+pG87+cdk3usl9lgNaSlH/jYw/Bl4mG/smkBhXkv+axUd3wc48tXfCiGEvrQ8lwfABLCqnce4q32HahgJw48TZeSb6qTYIngS9v6yNesQfm+IFIz+09Wt6xzQwoKbI9d5OXpIco8eeVge5KLo7X/R1zzFHAjLtJF13f8pMdquXioGvM9twJ/WDlT1hlCxBF9tq1U20HKOPQ6p7YbScE8YdfyjnobKvvl
x-incomingheadercount: 42
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI;SFV:NSPM;SFS:(7070007)(98901004);DIR:OUT;SFP:1901;SCL:1;SRVR:SN1NAM04HT075;H:BLUPR15MB0435.namprd15.prod.outlook.com;FPR:;SPF:None;LANG:en;
x-ms-office365-filtering-correlation-id: db7475ef-b6cc-4add-c53a-08d487ec0f56
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031322274)(1603101448)(1601125374)(1701031045);SRVR:SN1NAM04HT075;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(444000031);SRVR:SN1NAM04HT075;BCL:0;PCL:0;RULEID:;SRVR:SN1NAM04HT075;
x-forefront-prvs: 02830F0362
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-ID: <642755A55A28D745B600ADC1F891959E@namprd15.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Apr 2017 12:52:16.4368
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1NAM04HT075
archived-at: Thu, 20 Apr 2017 12:52:30 -0000

Jim,

I would offer you a few bits of advice. First, NiFi relies on ZooKeeper to =
coordinate which node is responsible
to act as the Cluster Coordinator and which node should be the Primary Node=
. NiFi does allow you to start
and embedded ZooKeeper, but for production use, it is recommended that you =
use an external ZooKeeper
running on different boxes.

Secondly, the default timeouts used for clustering (the "nifi.cluster.node.=
connection.timeout" and
"nifi.cluster.node.read.timeout" properties in nifi.properties) are set to =
5 seconds. This is okay for a "getting started"
type of cluster. However, if you start processing large numbers of FlowFile=
s, the JVM's garbage collection can sometimes
cause some fairly lengthy pauses. This could cause timeouts. So I would rec=
ommend increasing that to 10-15 seconds
or more.

Finally, the "nifi.zookeeper.connect.timeout" and "nifi.zookeeper.session.t=
imeout" default to 3 seconds, as this is what
the ZooKeeper default is. However, I've heard some people indicate that the=
y saw frequent ZooKeeper timeouts, which caused
the Primary Node and Cluster Coordinator to change frequently. Changing the=
 value to 5 or 10 seconds was much better.

Thanks
-Mark

> On Apr 20, 2017, at 7:01 AM, James McMahon <jsmcmahon3@gmail.com> wrote:
>=20
> Good morning. I have established an initial single-threaded NiFi server i=
nstance for my customers. It works well, but I anticipate increasing usage =
as groups learn more about it. I also want to move beyond our single thread=
ed-ness.
>=20
> I would like to take the next step in the evolution of our NiFi capabilit=
y, implementing a clustered NiFi server configuration to help me address th=
e following requirements:
> 1. increase our fault tolerance
> 2. permit our configuration to scale to peak processing demands during bu=
lk data loads and as more customers begin to leverage our NiFi instance
> 3. permit our configuration to load balance
>=20
> I do intend to begin by reading through the clustering sections in the Ni=
Fi Sys Admin guide. I am also interested in hearing from our user community=
, particularly regarding clustering "best practices" and practical insights=
 based on your experiences. Thanks in advance for any insights you are will=
ing to share.  -Jim