Hi,
I'm the NiPyApi author.
It's back tested to NiFi 1.1.2 generally, though I haven't specifically
tested these calls.

If you'd like to wrap the calls and put them in a PR that would be very
welcome, otherwise you're welcome to write your use case into an issue on
the GitHub repo and I'll take a look.

Thanks,
Dan

On Mon, 7 May 2018, 17:21 Andy LoPresto, <alopre...@apache.org> wrote:

> Tom,
>
> A temporary solution until you can upgrade would be to write a script
> (using whatever language you prefer — Groovy, Python, Bash, etc.) to call
> the NiFi API, list the controllers, and tell each to start. You could run
> this script when you restart NiFi and save the human-interaction through
> the UI.
>
> There are a couple tools that make this much easier (NiFi CLI [1] and
> NiPyApi [2]) but I’m not sure how compatible they will be with version 1.1.
> At the very least, they will show good implementations of the process, and
> you can simply chain a bunch of curl commands together if necessary.
>
> [1]
> https://github.com/apache/nifi/tree/master/nifi-toolkit/nifi-toolkit-cli
> [2] https://github.com/Chaffelson/nipyapi
>
>
> Andy LoPresto
> alopre...@apache.org
> *alopresto.apa...@gmail.com <alopresto.apa...@gmail.com>*
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> On May 7, 2018, at 8:28 AM, Joe Witt <joe.w...@gmail.com> wrote:
>
> Tom - understood.  You should not have to restart them manually so I
> suspect whatever you're running into has been addressed.  I know this is a
> lame answer but if you can try upgrading to see if that addresses it that
> would be very helpful.
>
> On Mon, May 7, 2018 at 10:49 AM, Cassidy, Thomas G (Tom) JR CTR USARMY
> MEDCOM JMLFDC (US) <thomas.g.cassidy....@mail.mil> wrote:
>
> Joe, we are on version 1.1 (Very old I know but we are planning to upgrade
>> in the near future). Just need a way to avoid having to go in and restart
>> controllers individually and instead start them all automatically after the
>> NiFi service gets restarted. Thanks -- tc
>>
>>
>>
>> Tom Cassidy
>>
>> JMLFDC Operations Manager
>>
>> Clinical Support Branch, Solution Delivery Division (SDD), Health
>> Information Technology (HIT), Defense Health Agency (DHA) JMLFDC - DXC - CTR
>>
>> 1674 Nelson Street, Ste. #121
>>
>> Fort Detrick, MD 21702
>>
>> 301-619-8744 (work)
>>
>> 301-471-4559 (cell)
>>
>> thomas.g.cassidy....@mail.mil
>>
>>
>>
>> *From:* Cassidy, Thomas G (Tom) JR CTR USARMY MEDCOM JMLFDC (US)
>> *Sent:* Thursday, May 03, 2018 4:17 PM
>> *To:* users@nifi.apache.org
>> *Subject:* RE: [Non-DoD Source] Re: Starting controller services
>>
>
>>
>> Nagios XI. How do I determine which version? I suspect its recent but not
>> the latest.
>>
>>
>>
>> Here are a couple of the controllers in use at the Process Group
>> Configuration level.
>>
> <image001.png>
>>
>
>>
>>
>>
>> Tom Cassidy
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: Joe Witt [mailto:joe.w...@gmail.com]
>> Sent: Thursday, May 03, 2018 4:13 PM
>> To: users@nifi.apache.org
>> Subject: [Non-DoD Source] Re: Starting controller services
>>
>>
>>
> Hello
>>
>>
>>
>> What version of NiFi are you on?  Can you share more about the controller
>> services/specific processor combinations where you're seeing this?
>>
>>
>>
>> Thanks
>>
>>
>>
>> On Thu, May 3, 2018 at 4:05 PM, Cassidy, Thomas G (Tom) JR CTR USARMY
>> MEDCOM JMLFDC (US) <thomas.g.cassidy....@mail.mil> wrote:
>>
>> > We are relatively new users of NiFi and think there might be a better
>> way of recovery than what we do now.
>>
>> >
>>
>> > Occasionally a flow will hang and the best way to recover is to bounce
>> the NiFi service.
>>
>> >
>>
>> > This is where the problem comes in:
>>
>> > We then go into the flows and find each controller service and enable
>> it to get the flow running again. Is there a setting or command that can be
>> used to automatically restart the controller services?
>>
>> >
>>
>> > Thanks for any help
>>
>> > Tom Cassidy
>>
>> >
>>
>> >
>>
>>
>>
>

Reply via email to