You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@nifi.apache.org by Ryan H <ry...@gmail.com> on 2019/03/27 17:58:48 UTC
Changing All Stopped Processors to Disabled
Hi All,
Is there a good way to change all processors on the canvas that are stopped
to a disabled state instead? The problem is that we have a large amount of
processors on our canvas that are in the stopped state which is killing the
UI performance (wouldn't want to go to each of the 2,000 stopped processors
individually and mark as disabled). We just learned that this isn't an
issue (with regard to UI performance) when processors are in the disabled
state due to the way status checks are performed. I'm sure this could be
scripted with NiPy or something else, but just wanted to throw the question
out to the community first before delving into this.
Cheers,
Ryan H
Re: Changing All Stopped Processors to Disabled
Posted by Matt Gilman <ma...@gmail.com>.
Ryan,
If you're running 1.7 or later you can enable or disable in bulk just like
you can start or stop. It's supported right in NiFi UI. You can use actions
out of the Operate palette or the context menu.
https://issues.apache.org/jira/browse/NIFI-5066
Matt
On Wed, Mar 27, 2019 at 2:07 PM Andy LoPresto <al...@apache.org> wrote:
> Ryan,
>
> Reading through your email, my immediate suggestion was NiPyAPI. I think
> Dan has wrapped some useful query methods there that could make this quite
> easy. Obviously you are aware of it, but it’s still my best recommendation
> for now.
>
>
> Andy LoPresto
> alopresto@apache.org
> *alopresto.apache@gmail.com <al...@gmail.com>*
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>
> On Mar 27, 2019, at 10:58 AM, Ryan H <ry...@gmail.com>
> wrote:
>
> Hi All,
>
> Is there a good way to change all processors on the canvas that are
> stopped to a disabled state instead? The problem is that we have a large
> amount of processors on our canvas that are in the stopped state which is
> killing the UI performance (wouldn't want to go to each of the 2,000
> stopped processors individually and mark as disabled). We just learned that
> this isn't an issue (with regard to UI performance) when processors are in
> the disabled state due to the way status checks are performed. I'm sure
> this could be scripted with NiPy or something else, but just wanted to
> throw the question out to the community first before delving into this.
>
> Cheers,
>
> Ryan H
>
>
>
Re: Changing All Stopped Processors to Disabled
Posted by Ryan H <ry...@gmail.com>.
Sounds like the ability to disable at the Process Group exists after 1.7, I
retract my question!
-Ryan H
On Wed, Mar 27, 2019 at 2:18 PM Ryan H <ry...@gmail.com>
wrote:
> @Mark, we are on version 1.5 and there is a definite slow down, at least
> for us with UI responsiveness (initial load of canvas upon logging in is
> close to a minute with about 2,000 processors on the canvas, with about
> 1,500 in the stopped state). We are planning on upgrading to 1.8.0 soon...
> Should there be a significant improvement in 1.8.0?
>
> @Andy, thanks for the suggestion. I agree that NiPyApi would foot the bill
> on this one.
>
> Would this be a decent feature request? The ability to start/stop at the
> process group level currently exists. Does it make sense to also be able to
> disable at the Process Group level (not sure if there is a good case for it
> other than this scenario)?
>
>
> -Ryan H
>
> On Wed, Mar 27, 2019 at 2:07 PM Andy LoPresto <al...@apache.org>
> wrote:
>
>> Ryan,
>>
>> Reading through your email, my immediate suggestion was NiPyAPI. I think
>> Dan has wrapped some useful query methods there that could make this quite
>> easy. Obviously you are aware of it, but it’s still my best recommendation
>> for now.
>>
>>
>> Andy LoPresto
>> alopresto@apache.org
>> *alopresto.apache@gmail.com <al...@gmail.com>*
>> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>>
>> On Mar 27, 2019, at 10:58 AM, Ryan H <ry...@gmail.com>
>> wrote:
>>
>> Hi All,
>>
>> Is there a good way to change all processors on the canvas that are
>> stopped to a disabled state instead? The problem is that we have a large
>> amount of processors on our canvas that are in the stopped state which is
>> killing the UI performance (wouldn't want to go to each of the 2,000
>> stopped processors individually and mark as disabled). We just learned that
>> this isn't an issue (with regard to UI performance) when processors are in
>> the disabled state due to the way status checks are performed. I'm sure
>> this could be scripted with NiPy or something else, but just wanted to
>> throw the question out to the community first before delving into this.
>>
>> Cheers,
>>
>> Ryan H
>>
>>
>>
Re: Changing All Stopped Processors to Disabled
Posted by Ryan H <ry...@gmail.com>.
@Mark, we are on version 1.5 and there is a definite slow down, at least
for us with UI responsiveness (initial load of canvas upon logging in is
close to a minute with about 2,000 processors on the canvas, with about
1,500 in the stopped state). We are planning on upgrading to 1.8.0 soon...
Should there be a significant improvement in 1.8.0?
@Andy, thanks for the suggestion. I agree that NiPyApi would foot the bill
on this one.
Would this be a decent feature request? The ability to start/stop at the
process group level currently exists. Does it make sense to also be able to
disable at the Process Group level (not sure if there is a good case for it
other than this scenario)?
-Ryan H
On Wed, Mar 27, 2019 at 2:07 PM Andy LoPresto <al...@apache.org> wrote:
> Ryan,
>
> Reading through your email, my immediate suggestion was NiPyAPI. I think
> Dan has wrapped some useful query methods there that could make this quite
> easy. Obviously you are aware of it, but it’s still my best recommendation
> for now.
>
>
> Andy LoPresto
> alopresto@apache.org
> *alopresto.apache@gmail.com <al...@gmail.com>*
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>
> On Mar 27, 2019, at 10:58 AM, Ryan H <ry...@gmail.com>
> wrote:
>
> Hi All,
>
> Is there a good way to change all processors on the canvas that are
> stopped to a disabled state instead? The problem is that we have a large
> amount of processors on our canvas that are in the stopped state which is
> killing the UI performance (wouldn't want to go to each of the 2,000
> stopped processors individually and mark as disabled). We just learned that
> this isn't an issue (with regard to UI performance) when processors are in
> the disabled state due to the way status checks are performed. I'm sure
> this could be scripted with NiPy or something else, but just wanted to
> throw the question out to the community first before delving into this.
>
> Cheers,
>
> Ryan H
>
>
>
Re: Changing All Stopped Processors to Disabled
Posted by Andy LoPresto <al...@apache.org>.
Ryan,
Reading through your email, my immediate suggestion was NiPyAPI. I think Dan has wrapped some useful query methods there that could make this quite easy. Obviously you are aware of it, but it’s still my best recommendation for now.
Andy LoPresto
alopresto@apache.org
alopresto.apache@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On Mar 27, 2019, at 10:58 AM, Ryan H <ry...@gmail.com> wrote:
>
> Hi All,
>
> Is there a good way to change all processors on the canvas that are stopped to a disabled state instead? The problem is that we have a large amount of processors on our canvas that are in the stopped state which is killing the UI performance (wouldn't want to go to each of the 2,000 stopped processors individually and mark as disabled). We just learned that this isn't an issue (with regard to UI performance) when processors are in the disabled state due to the way status checks are performed. I'm sure this could be scripted with NiPy or something else, but just wanted to throw the question out to the community first before delving into this.
>
> Cheers,
>
> Ryan H
Re: Changing All Stopped Processors to Disabled
Posted by Mark Payne <ma...@hotmail.com>.
Ryan,
In later versions of NiFi (1.8.0 I believe) the validation is done in the background instead of in the web request,
so stopped processors won't slow down the UI. We also do allow the user to select 1 or more components and
disable/enable the components in bulk. Older versions did not allow for that.
Thanks
-Mark
> On Mar 27, 2019, at 1:58 PM, Ryan H <ry...@gmail.com> wrote:
>
> Hi All,
>
> Is there a good way to change all processors on the canvas that are stopped to a disabled state instead? The problem is that we have a large amount of processors on our canvas that are in the stopped state which is killing the UI performance (wouldn't want to go to each of the 2,000 stopped processors individually and mark as disabled). We just learned that this isn't an issue (with regard to UI performance) when processors are in the disabled state due to the way status checks are performed. I'm sure this could be scripted with NiPy or something else, but just wanted to throw the question out to the community first before delving into this.
>
> Cheers,
>
> Ryan H