You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@nifi.apache.org by "Cassidy, Thomas G (Tom) JR CTR USARMY MEDCOM JMLFDC (USA)" <th...@mail.mil> on 2018/11/14 18:15:40 UTC

RE: [Non-DoD Source] Re: rotating servers

Joe thanks for the question. I checked and it was written inhouse a while back so you're right it is something we need to look at. Thanks -- tc

Tom Cassidy


-----Original Message-----
From: Joe Witt [mailto:joe.witt@gmail.com] 
Sent: Wednesday, November 14, 2018 12:10 PM
To: users@nifi.apache.org
Subject: [Non-DoD Source] Re: rotating servers

Tom,

Just want to make sure I'm following here but the custom Controller Service you reference is where this logic lives/should live.  Right?

If that is the case then you'll want to focus on improving the behavior of the controller service to switch over.

If that is not the case can you share what role NiFi or the framework of NiFi would play that you think might be causing this?

Thanks
On Wed, Nov 14, 2018 at 11:53 AM Cassidy, Thomas G (Tom) JR CTR USARMY MEDCOM JMLFDC (USA) <th...@mail.mil> wrote:
>
> We have created a controller service for JBOSS-BT-JNDIService. The 
> "java.naming.provider.url (target host and port)" has been configured to use 3 different JBOSS servers.
>
> The problem is that NiFi seems to always use the first server and only rarely moves onto the 2nd or 3rd when the first is busy (?).
>
> Is there a way to force NiFi to rotate through the 3 servers instead of always trying #1?
>
> Thanks -- Tom