question Re: unable to delete consumeKafka processor on canvas in Archives of Support Questions (Read Only)

unable to delete consumeKafka processor on canvas

ankit_jain — Thu, 29 Sep 2016 22:52:57 GMT

Please check attachment i''m not able to delete the consumeKafka processor. i also wanted to know what does the small icon on right-upper corner of processor with some number mean. i guessing this must show some kind of warning messages but nothing happens on mouse hover.nifi-processor-error.png

Re: unable to delete consumeKafka processor on canvas

andrewg — Thu, 29 Sep 2016 22:58:52 GMT

Which Kafka version are you using? The timeout handling varied greatly between 0.8, 0.9 and 0.10, Match the consumer processor to the broker version, please (0.8 -> Put/Get/Kafka, 0.9 -> Publish/Consume, 0.10 -> Publish/Consume_0_10).

You might be running into this issue: https://issues.apache.org/jira/browse/NIFI-2739

If you can't wait until NiFi 1.1 is released, this patch is already included in HDF 2.0

Re: unable to delete consumeKafka processor on canvas

andrewg — Thu, 29 Sep 2016 22:59:40 GMT

The number in the top-right corner of the processor is showing how many active threads there are executing for this component.

Re: unable to delete consumeKafka processor on canvas

alim — Thu, 29 Sep 2016 23:01:02 GMT

The icon/number in the right-upper corner is the number of tasks the processor is executing. More information about these "active tasks" can be found in the documentation (https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#processor_anatomy).

Re: unable to delete consumeKafka processor on canvas

myoung — Thu, 29 Sep 2016 23:27:29 GMT

@Ankit Jain

Sometimes you have to delete the connection between two processors before you can delete one of the processors. Try that to see if you can delete your processor.

Re: unable to delete consumeKafka processor on canvas

ankit_jain — Fri, 30 Sep 2016 14:16:34 GMT

i tried deleting the connection flow, it didn't work as well. later i restarted NIFI and processor came out of indefinite block state.