[jira] [Commented] (NIFI-5498) QueryDatabaseTable unable to store state in Zookeeper
[
https://issues.apache.org/jira/browse/NIFI-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575454#comment-16575454
]
Daniel commented on NIFI-5498:
--
Gotcha! My line of thinking was "well if it's creator only, and a single node,
it should be able to read what it creates". Regardless, many thanks again for
your help.
> QueryDatabaseTable unable to store state in Zookeeper
> -
>
> Key: NIFI-5498
> URL: https://issues.apache.org/jira/browse/NIFI-5498
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Affects Versions: 1.7.1
>Reporter: Daniel
>Priority: Critical
>
> Running NiFi 1.7.1 in a clustered environment, external zookeeper. I'm
> getting the following stack trace when running any of my QueryDatabaseTable
> processors:
> {code:java}
> eryDatabaseTable[id=a26cafd1-56e4-3f52-99f5-8143abe3ce3a] failed to update
> State Manager, maximum observed values will not be recorded:
> java.io.IOException: Fai
> led to set cluster-wide state in ZooKeeper for component with ID
> a26cafd1-56e4-3f52-99f5-8143abe3ce3a
> java.io.IOException: Failed to set cluster-wide state in ZooKeeper for
> component with ID a26cafd1-56e4-3f52-99f5-8143abe3ce3a
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:343)
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:283)
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:228)
> at
> org.apache.nifi.controller.state.manager.StandardStateManagerProvider$1.setState(StandardStateManagerProvider.java:271)
> at
> org.apache.nifi.controller.state.StandardStateManager.setState(StandardStateManager.java:79)
> at
> org.apache.nifi.controller.lifecycle.TaskTerminationAwareStateManager.setState(TaskTerminationAwareStateManager.java:64)
> at
> org.apache.nifi.processors.standard.QueryDatabaseTable.onTrigger(QueryDatabaseTable.java:430)
> at
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1165)
> at
> org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:203)
> at
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:117)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.zookeeper.KeeperException$InvalidACLException:
> KeeperErrorCode = InvalidACL for
> /nifi/components/a26cafd1-56e4-3f52-99f5-8143abe3ce3a
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:121)
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:783)
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.createNode(ZooKeeperStateProvider.java:360)
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:321)
> ... 16 common frames omitted
> {code}
> The processors do work, but their inability to store state limits their
> usage, and the error message floods the log file. Any suggestions would be
> welcomed.
> Other things to note:
> * All my other processors (AMQP, Kafka, GetHTTP, ExecuteSQL) work okay.
> * I've reproduced this in several environments of mine, including a single
> node, two node and three node cluster.
> * I thought originally this might be related to the fact that I didn't create
> the processor, but imported it from a NiFi registry, but I created one at the
> root of my NiFi flow and had the same result.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (NIFI-5498) QueryDatabaseTable unable to store state in Zookeeper
[
https://issues.apache.org/jira/browse/NIFI-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575416#comment-16575416
]
Daniel commented on NIFI-5498:
--
Hah! That did it. You're the man [~bende]! Thanks.
> QueryDatabaseTable unable to store state in Zookeeper
> -
>
> Key: NIFI-5498
> URL: https://issues.apache.org/jira/browse/NIFI-5498
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Affects Versions: 1.7.1
>Reporter: Daniel
>Priority: Critical
>
> Running NiFi 1.7.1 in a clustered environment, external zookeeper. I'm
> getting the following stack trace when running any of my QueryDatabaseTable
> processors:
> {code:java}
> eryDatabaseTable[id=a26cafd1-56e4-3f52-99f5-8143abe3ce3a] failed to update
> State Manager, maximum observed values will not be recorded:
> java.io.IOException: Fai
> led to set cluster-wide state in ZooKeeper for component with ID
> a26cafd1-56e4-3f52-99f5-8143abe3ce3a
> java.io.IOException: Failed to set cluster-wide state in ZooKeeper for
> component with ID a26cafd1-56e4-3f52-99f5-8143abe3ce3a
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:343)
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:283)
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:228)
> at
> org.apache.nifi.controller.state.manager.StandardStateManagerProvider$1.setState(StandardStateManagerProvider.java:271)
> at
> org.apache.nifi.controller.state.StandardStateManager.setState(StandardStateManager.java:79)
> at
> org.apache.nifi.controller.lifecycle.TaskTerminationAwareStateManager.setState(TaskTerminationAwareStateManager.java:64)
> at
> org.apache.nifi.processors.standard.QueryDatabaseTable.onTrigger(QueryDatabaseTable.java:430)
> at
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1165)
> at
> org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:203)
> at
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:117)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.zookeeper.KeeperException$InvalidACLException:
> KeeperErrorCode = InvalidACL for
> /nifi/components/a26cafd1-56e4-3f52-99f5-8143abe3ce3a
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:121)
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:783)
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.createNode(ZooKeeperStateProvider.java:360)
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:321)
> ... 16 common frames omitted
> {code}
> The processors do work, but their inability to store state limits their
> usage, and the error message floods the log file. Any suggestions would be
> welcomed.
> Other things to note:
> * All my other processors (AMQP, Kafka, GetHTTP, ExecuteSQL) work okay.
> * I've reproduced this in several environments of mine, including a single
> node, two node and three node cluster.
> * I thought originally this might be related to the fact that I didn't create
> the processor, but imported it from a NiFi registry, but I created one at the
> root of my NiFi flow and had the same result.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (NIFI-5498) QueryDatabaseTable unable to store state in Zookeeper
[
https://issues.apache.org/jira/browse/NIFI-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel resolved NIFI-5498.
--
Resolution: Fixed
> QueryDatabaseTable unable to store state in Zookeeper
> -
>
> Key: NIFI-5498
> URL: https://issues.apache.org/jira/browse/NIFI-5498
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Affects Versions: 1.7.1
>Reporter: Daniel
>Priority: Critical
>
> Running NiFi 1.7.1 in a clustered environment, external zookeeper. I'm
> getting the following stack trace when running any of my QueryDatabaseTable
> processors:
> {code:java}
> eryDatabaseTable[id=a26cafd1-56e4-3f52-99f5-8143abe3ce3a] failed to update
> State Manager, maximum observed values will not be recorded:
> java.io.IOException: Fai
> led to set cluster-wide state in ZooKeeper for component with ID
> a26cafd1-56e4-3f52-99f5-8143abe3ce3a
> java.io.IOException: Failed to set cluster-wide state in ZooKeeper for
> component with ID a26cafd1-56e4-3f52-99f5-8143abe3ce3a
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:343)
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:283)
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:228)
> at
> org.apache.nifi.controller.state.manager.StandardStateManagerProvider$1.setState(StandardStateManagerProvider.java:271)
> at
> org.apache.nifi.controller.state.StandardStateManager.setState(StandardStateManager.java:79)
> at
> org.apache.nifi.controller.lifecycle.TaskTerminationAwareStateManager.setState(TaskTerminationAwareStateManager.java:64)
> at
> org.apache.nifi.processors.standard.QueryDatabaseTable.onTrigger(QueryDatabaseTable.java:430)
> at
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1165)
> at
> org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:203)
> at
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:117)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.zookeeper.KeeperException$InvalidACLException:
> KeeperErrorCode = InvalidACL for
> /nifi/components/a26cafd1-56e4-3f52-99f5-8143abe3ce3a
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:121)
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:783)
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.createNode(ZooKeeperStateProvider.java:360)
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:321)
> ... 16 common frames omitted
> {code}
> The processors do work, but their inability to store state limits their
> usage, and the error message floods the log file. Any suggestions would be
> welcomed.
> Other things to note:
> * All my other processors (AMQP, Kafka, GetHTTP, ExecuteSQL) work okay.
> * I've reproduced this in several environments of mine, including a single
> node, two node and three node cluster.
> * I thought originally this might be related to the fact that I didn't create
> the processor, but imported it from a NiFi registry, but I created one at the
> root of my NiFi flow and had the same result.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (NIFI-5498) QueryDatabaseTable unable to store state in Zookeeper
[
https://issues.apache.org/jira/browse/NIFI-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575413#comment-16575413
]
Daniel commented on NIFI-5498:
--
[~bende] thanks for your response, I'm currently testing with an open
zookeeper. The setting is set to `CreatorOnly` though, I'll try and switch it
to `Open`, but it's worth noting this even happens in a single node cluster.
> QueryDatabaseTable unable to store state in Zookeeper
> -
>
> Key: NIFI-5498
> URL: https://issues.apache.org/jira/browse/NIFI-5498
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Affects Versions: 1.7.1
>Reporter: Daniel
>Priority: Critical
>
> Running NiFi 1.7.1 in a clustered environment, external zookeeper. I'm
> getting the following stack trace when running any of my QueryDatabaseTable
> processors:
> {code:java}
> eryDatabaseTable[id=a26cafd1-56e4-3f52-99f5-8143abe3ce3a] failed to update
> State Manager, maximum observed values will not be recorded:
> java.io.IOException: Fai
> led to set cluster-wide state in ZooKeeper for component with ID
> a26cafd1-56e4-3f52-99f5-8143abe3ce3a
> java.io.IOException: Failed to set cluster-wide state in ZooKeeper for
> component with ID a26cafd1-56e4-3f52-99f5-8143abe3ce3a
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:343)
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:283)
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:228)
> at
> org.apache.nifi.controller.state.manager.StandardStateManagerProvider$1.setState(StandardStateManagerProvider.java:271)
> at
> org.apache.nifi.controller.state.StandardStateManager.setState(StandardStateManager.java:79)
> at
> org.apache.nifi.controller.lifecycle.TaskTerminationAwareStateManager.setState(TaskTerminationAwareStateManager.java:64)
> at
> org.apache.nifi.processors.standard.QueryDatabaseTable.onTrigger(QueryDatabaseTable.java:430)
> at
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1165)
> at
> org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:203)
> at
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:117)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.zookeeper.KeeperException$InvalidACLException:
> KeeperErrorCode = InvalidACL for
> /nifi/components/a26cafd1-56e4-3f52-99f5-8143abe3ce3a
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:121)
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:783)
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.createNode(ZooKeeperStateProvider.java:360)
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:321)
> ... 16 common frames omitted
> {code}
> The processors do work, but their inability to store state limits their
> usage, and the error message floods the log file. Any suggestions would be
> welcomed.
> Other things to note:
> * All my other processors (AMQP, Kafka, GetHTTP, ExecuteSQL) work okay.
> * I've reproduced this in several environments of mine, including a single
> node, two node and three node cluster.
> * I thought originally this might be related to the fact that I didn't create
> the processor, but imported it from a NiFi registry, but I created one at the
> root of my NiFi flow and had the same result.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (NIFI-5498) QueryDatabaseTable unable to store state in Zookeeper
[
https://issues.apache.org/jira/browse/NIFI-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575138#comment-16575138
]
Daniel commented on NIFI-5498:
--
Not knowing a lot about Zookeeper, could this potentially be related to a
missing step when setting up an external Zookeeper?
> QueryDatabaseTable unable to store state in Zookeeper
> -
>
> Key: NIFI-5498
> URL: https://issues.apache.org/jira/browse/NIFI-5498
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Affects Versions: 1.7.1
>Reporter: Daniel
>Priority: Critical
>
> Running NiFi 1.7.1 in a clustered environment, external zookeeper. I'm
> getting the following stack trace when running any of my QueryDatabaseTable
> processors:
> {code:java}
> eryDatabaseTable[id=a26cafd1-56e4-3f52-99f5-8143abe3ce3a] failed to update
> State Manager, maximum observed values will not be recorded:
> java.io.IOException: Fai
> led to set cluster-wide state in ZooKeeper for component with ID
> a26cafd1-56e4-3f52-99f5-8143abe3ce3a
> java.io.IOException: Failed to set cluster-wide state in ZooKeeper for
> component with ID a26cafd1-56e4-3f52-99f5-8143abe3ce3a
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:343)
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:283)
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:228)
> at
> org.apache.nifi.controller.state.manager.StandardStateManagerProvider$1.setState(StandardStateManagerProvider.java:271)
> at
> org.apache.nifi.controller.state.StandardStateManager.setState(StandardStateManager.java:79)
> at
> org.apache.nifi.controller.lifecycle.TaskTerminationAwareStateManager.setState(TaskTerminationAwareStateManager.java:64)
> at
> org.apache.nifi.processors.standard.QueryDatabaseTable.onTrigger(QueryDatabaseTable.java:430)
> at
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1165)
> at
> org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:203)
> at
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:117)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.zookeeper.KeeperException$InvalidACLException:
> KeeperErrorCode = InvalidACL for
> /nifi/components/a26cafd1-56e4-3f52-99f5-8143abe3ce3a
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:121)
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:783)
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.createNode(ZooKeeperStateProvider.java:360)
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:321)
> ... 16 common frames omitted
> {code}
> The processors do work, but their inability to store state limits their
> usage, and the error message floods the log file. Any suggestions would be
> welcomed.
> Other things to note:
> * All my other processors (AMQP, Kafka, GetHTTP, ExecuteSQL) work okay.
> * I've reproduced this in several environments of mine, including a single
> node, two node and three node cluster.
> * I thought originally this might be related to the fact that I didn't create
> the processor, but imported it from a NiFi registry, but I created one at the
> root of my NiFi flow and had the same result.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (NIFI-4723) PublishAMQP 1.4.0 support Expression Language
[ https://issues.apache.org/jira/browse/NIFI-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16573510#comment-16573510 ] Daniel commented on NIFI-4723: -- See https://github.com/apache/nifi/pull/2936 > PublishAMQP 1.4.0 support Expression Language > -- > > Key: NIFI-4723 > URL: https://issues.apache.org/jira/browse/NIFI-4723 > Project: Apache NiFi > Issue Type: Improvement > Components: Examples, Extensions >Reporter: bat-hen >Priority: Major > > Hi, > there is no support to Expression Language in PublishAMQP? for: > Host Name > Port > User Name > Password > we want to do deployment with template and we cant use Expression Language in > rabbitmq.:| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-5498) QueryDatabaseTable unable to store state in Zookeeper
[
https://issues.apache.org/jira/browse/NIFI-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel updated NIFI-5498:
-
Description:
Running NiFi 1.7.1 in a clustered environment, external zookeeper. I'm getting
the following stack trace when running any of my QueryDatabaseTable processors:
{code:java}
eryDatabaseTable[id=a26cafd1-56e4-3f52-99f5-8143abe3ce3a] failed to update
State Manager, maximum observed values will not be recorded:
java.io.IOException: Fai
led to set cluster-wide state in ZooKeeper for component with ID
a26cafd1-56e4-3f52-99f5-8143abe3ce3a
java.io.IOException: Failed to set cluster-wide state in ZooKeeper for
component with ID a26cafd1-56e4-3f52-99f5-8143abe3ce3a
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:343)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:283)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:228)
at
org.apache.nifi.controller.state.manager.StandardStateManagerProvider$1.setState(StandardStateManagerProvider.java:271)
at
org.apache.nifi.controller.state.StandardStateManager.setState(StandardStateManager.java:79)
at
org.apache.nifi.controller.lifecycle.TaskTerminationAwareStateManager.setState(TaskTerminationAwareStateManager.java:64)
at
org.apache.nifi.processors.standard.QueryDatabaseTable.onTrigger(QueryDatabaseTable.java:430)
at
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1165)
at
org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:203)
at
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:117)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.zookeeper.KeeperException$InvalidACLException:
KeeperErrorCode = InvalidACL for
/nifi/components/a26cafd1-56e4-3f52-99f5-8143abe3ce3a
at org.apache.zookeeper.KeeperException.create(KeeperException.java:121)
at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:783)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.createNode(ZooKeeperStateProvider.java:360)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:321)
... 16 common frames omitted
{code}
The processors do work, but their inability to store state limits their usage,
and the error message floods the log file. Any suggestions would be welcomed.
Other things to note:
* All my other processors (AMQP, Kafka, GetHTTP, ExecuteSQL) work okay.
* I've reproduced this in several environments of mine, including a single
node, two node and three node cluster.
* I thought originally this might be related to the fact that I didn't create
the processor, but imported it from a NiFi registry, but I created one at the
root of my NiFi flow and had the same result.
was:
Running NiFi 1.7.1 in a clustered environment, external zookeeper. I'm getting
the following stack trace when running any of my QueryDatabaseTable processors:
{code:java}
eryDatabaseTable[id=a26cafd1-56e4-3f52-99f5-8143abe3ce3a] failed to update
State Manager, maximum observed values will not be recorded:
java.io.IOException: Fai
led to set cluster-wide state in ZooKeeper for component with ID
a26cafd1-56e4-3f52-99f5-8143abe3ce3a
java.io.IOException: Failed to set cluster-wide state in ZooKeeper for
component with ID a26cafd1-56e4-3f52-99f5-8143abe3ce3a
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:343)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:283)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:228)
at
org.apache.nifi.controller.state.manager.StandardStateManagerProvider$1.setState(StandardStateManagerProvider.java:271)
at
org.apache.nifi.controlle
[jira] [Commented] (NIFI-2415) GenerateTableFetch/QueryDatabaseTable cannot store state
[
https://issues.apache.org/jira/browse/NIFI-2415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16573292#comment-16573292
]
Daniel commented on NIFI-2415:
--
I opened NIFI-5498.
> GenerateTableFetch/QueryDatabaseTable cannot store state
>
>
> Key: NIFI-2415
> URL: https://issues.apache.org/jira/browse/NIFI-2415
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Haimo Liu
>Assignee: Matt Burgess
>Priority: Critical
> Fix For: 1.0.0, 1.0.0-Beta
>
> Attachments: Screen Shot 2016-07-27 at 11.10.45 PM.png
>
>
> running NIFI in a clustered mode, 7/27 build
> Both GenerateTableFetch and QueryDatabaseTable cannot store state in a
> clustered mode (checked ListFile, can store state successfully)
> see attached screenshot, trace below:
> 2016-07-27 23:25:00,014 INFO [ProcessThread(sid:1 cport:-1):]
> o.a.z.server.PrepRequestProcessor Got user-level KeeperException when
> processing sessionid:0x2562f7875130009 type:create cxid:0xe4d
> zxid:0x73733 txntype:-1 reqpath:n/a Error
> Path:/nifi/components/2f810bb3-0156-1000--16128f8b
> Error:KeeperErrorCode = InvalidACL for
> /nifi/components/2f810bb3-0156-1000--16128f8b
> 2016-07-27 23:25:00,017 WARN [Framework Task Thread Thread-1]
> o.a.n.c.s.m.StandardStateManagerProvider Component with ID {} was removed
> from NiFi instance but failed to clear clustered state for the component
> java.io.IOException: Failed to set cluster-wide state in ZooKeeper for
> component with ID 2f810bb3-0156-1000--16128f8b
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:343)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:283)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:228)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.clear(ZooKeeperStateProvider.java:453)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.state.StandardStateManager.clear(StandardStateManager.java:85)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.state.manager.StandardStateManagerProvider.onComponentRemoved(StandardStateManagerProvider.java:276)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.groups.StandardProcessGroup$1.run(StandardProcessGroup.java:730)
> [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [na:1.8.0_77]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [na:1.8.0_77]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [na:1.8.0_77]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [na:1.8.0_77]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [na:1.8.0_77]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [na:1.8.0_77]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]
> Caused by: org.apache.zookeeper.KeeperException$InvalidACLException:
> KeeperErrorCode = InvalidACL for
> /nifi/components/2f810bb3-0156-1000--16128f8b
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:121)
> ~[zookeeper-3.4.6.jar:3.4.6-1569965]
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> ~[zookeeper-3.4.6.jar:3.4.6-1569965]
> at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:783)
> ~[zookeeper-3.4.6.jar:3.4.6-1569965]
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.createNode(ZooKeeperStateProvider.java:360)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:321)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> ... 13 common frames omitted
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (NIFI-5498) QueryDatabaseTable unable to store state in Zookeeper
[
https://issues.apache.org/jira/browse/NIFI-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel updated NIFI-5498:
-
Description:
Running NiFi 1.7.1 in a clustered environment, external zookeeper. I'm getting
the following stack trace when running any of my QueryDatabaseTable processors:
{code:java}
eryDatabaseTable[id=a26cafd1-56e4-3f52-99f5-8143abe3ce3a] failed to update
State Manager, maximum observed values will not be recorded:
java.io.IOException: Fai
led to set cluster-wide state in ZooKeeper for component with ID
a26cafd1-56e4-3f52-99f5-8143abe3ce3a
java.io.IOException: Failed to set cluster-wide state in ZooKeeper for
component with ID a26cafd1-56e4-3f52-99f5-8143abe3ce3a
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:343)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:283)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:228)
at
org.apache.nifi.controller.state.manager.StandardStateManagerProvider$1.setState(StandardStateManagerProvider.java:271)
at
org.apache.nifi.controller.state.StandardStateManager.setState(StandardStateManager.java:79)
at
org.apache.nifi.controller.lifecycle.TaskTerminationAwareStateManager.setState(TaskTerminationAwareStateManager.java:64)
at
org.apache.nifi.processors.standard.QueryDatabaseTable.onTrigger(QueryDatabaseTable.java:430)
at
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1165)
at
org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:203)
at
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:117)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.zookeeper.KeeperException$InvalidACLException:
KeeperErrorCode = InvalidACL for
/nifi/components/a26cafd1-56e4-3f52-99f5-8143abe3ce3a
at org.apache.zookeeper.KeeperException.create(KeeperException.java:121)
at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:783)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.createNode(ZooKeeperStateProvider.java:360)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:321)
... 16 common frames omitted
{code}
The processors do work, but their inability to store state limits their usage,
and the error message floods the log file. Any suggestions would be welcomed.
Other things to note:
* All my other processors (AMQP, Kafka, GetHTTP) work okay.
* I've reproduced this in several environments of mine, including a single
node, two node and three node cluster.
* I thought originally this might be related to the fact that I didn't create
the processor, but imported it from a NiFi registry, but I created one at the
root of my NiFi flow and had the same result.
was:
Running NiFi 1.7.1 in a clustered environment, external zookeeper. I'm getting
the following stack trace when running any of my QueryDatabaseTable processors:
{code:java}
eryDatabaseTable[id=a26cafd1-56e4-3f52-99f5-8143abe3ce3a] failed to update
State Manager, maximum observed values will not be recorded:
java.io.IOException: Fai
led to set cluster-wide state in ZooKeeper for component with ID
a26cafd1-56e4-3f52-99f5-8143abe3ce3a
java.io.IOException: Failed to set cluster-wide state in ZooKeeper for
component with ID a26cafd1-56e4-3f52-99f5-8143abe3ce3a
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:343)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:283)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:228)
at
org.apache.nifi.controller.state.manager.StandardStateManagerProvider$1.setState(StandardStateManagerProvider.java:271)
at
org.apache.nifi.controller.state.Stan
[jira] [Updated] (NIFI-5498) QueryDatabaseTable unable to store state in Zookeeper
[
https://issues.apache.org/jira/browse/NIFI-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel updated NIFI-5498:
-
Description:
Running NiFi 1.7.1 in a clustered environment, external zookeeper. I'm getting
the following stack trace when running any of my QueryDatabaseTable processors:
{code:java}
eryDatabaseTable[id=a26cafd1-56e4-3f52-99f5-8143abe3ce3a] failed to update
State Manager, maximum observed values will not be recorded:
java.io.IOException: Fai
led to set cluster-wide state in ZooKeeper for component with ID
a26cafd1-56e4-3f52-99f5-8143abe3ce3a
java.io.IOException: Failed to set cluster-wide state in ZooKeeper for
component with ID a26cafd1-56e4-3f52-99f5-8143abe3ce3a
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:343)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:283)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:228)
at
org.apache.nifi.controller.state.manager.StandardStateManagerProvider$1.setState(StandardStateManagerProvider.java:271)
at
org.apache.nifi.controller.state.StandardStateManager.setState(StandardStateManager.java:79)
at
org.apache.nifi.controller.lifecycle.TaskTerminationAwareStateManager.setState(TaskTerminationAwareStateManager.java:64)
at
org.apache.nifi.processors.standard.QueryDatabaseTable.onTrigger(QueryDatabaseTable.java:430)
at
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1165)
at
org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:203)
at
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:117)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.zookeeper.KeeperException$InvalidACLException:
KeeperErrorCode = InvalidACL for
/nifi/components/a26cafd1-56e4-3f52-99f5-8143abe3ce3a
at org.apache.zookeeper.KeeperException.create(KeeperException.java:121)
at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:783)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.createNode(ZooKeeperStateProvider.java:360)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:321)
... 16 common frames omitted
{code}
The processors do work, but their inability to store state limits their usage,
and the error message floods the log file. Any suggestions would be welcomed.
Other things to note:
All my other processors (AMQP, Kafka, GetHTTP) work okay. I've reproduced this
in several environments of mine, including a single node, two node and three
node cluster.
was:
Running NiFi 1.7.1 in a clustered environment, external zookeeper. I'm getting
the following stack trace when running any of my QueryDatabaseTable processors:
{code:java}
eryDatabaseTable[id=a26cafd1-56e4-3f52-99f5-8143abe3ce3a] failed to update
State Manager, maximum observed values will not be recorded:
java.io.IOException: Fai
led to set cluster-wide state in ZooKeeper for component with ID
a26cafd1-56e4-3f52-99f5-8143abe3ce3a
java.io.IOException: Failed to set cluster-wide state in ZooKeeper for
component with ID a26cafd1-56e4-3f52-99f5-8143abe3ce3a
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:343)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:283)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:228)
at
org.apache.nifi.controller.state.manager.StandardStateManagerProvider$1.setState(StandardStateManagerProvider.java:271)
at
org.apache.nifi.controller.state.StandardStateManager.setState(StandardStateManager.java:79)
at
org.apache.nifi.controller.lifecycle.TaskTerminationAwareStateManager.setState(TaskTerminationAwareStateManager.java:64)
at
org.apa
[jira] [Created] (NIFI-5498) QueryDatabaseTable unable to store state in Zookeeper
Daniel created NIFI-5498:
Summary: QueryDatabaseTable unable to store state in Zookeeper
Key: NIFI-5498
URL: https://issues.apache.org/jira/browse/NIFI-5498
Project: Apache NiFi
Issue Type: Improvement
Components: Extensions
Affects Versions: 1.7.1
Reporter: Daniel
Running NiFi 1.7.1 in a clustered environment, external zookeeper. I'm getting
the following stack trace when running any of my QueryDatabaseTable processors:
{code:java}
eryDatabaseTable[id=a26cafd1-56e4-3f52-99f5-8143abe3ce3a] failed to update
State Manager, maximum observed values will not be recorded:
java.io.IOException: Fai
led to set cluster-wide state in ZooKeeper for component with ID
a26cafd1-56e4-3f52-99f5-8143abe3ce3a
java.io.IOException: Failed to set cluster-wide state in ZooKeeper for
component with ID a26cafd1-56e4-3f52-99f5-8143abe3ce3a
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:343)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:283)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:228)
at
org.apache.nifi.controller.state.manager.StandardStateManagerProvider$1.setState(StandardStateManagerProvider.java:271)
at
org.apache.nifi.controller.state.StandardStateManager.setState(StandardStateManager.java:79)
at
org.apache.nifi.controller.lifecycle.TaskTerminationAwareStateManager.setState(TaskTerminationAwareStateManager.java:64)
at
org.apache.nifi.processors.standard.QueryDatabaseTable.onTrigger(QueryDatabaseTable.java:430)
at
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1165)
at
org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:203)
at
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:117)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.zookeeper.KeeperException$InvalidACLException:
KeeperErrorCode = InvalidACL for
/nifi/components/a26cafd1-56e4-3f52-99f5-8143abe3ce3a
at org.apache.zookeeper.KeeperException.create(KeeperException.java:121)
at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:783)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.createNode(ZooKeeperStateProvider.java:360)
at
org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:321)
... 16 common frames omitted
{code}
The processors do work, but their inability to store state limits their usage,
and the error message floods the log file. Any suggestions would be welcomed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (NIFI-2415) GenerateTableFetch/QueryDatabaseTable cannot store state
[
https://issues.apache.org/jira/browse/NIFI-2415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16571821#comment-16571821
]
Daniel commented on NIFI-2415:
--
Thanks [~mattyb149], mine is similar but not the same. I'll open a new ticket
rather than kick this dead horse. Thanks for your response.
> GenerateTableFetch/QueryDatabaseTable cannot store state
>
>
> Key: NIFI-2415
> URL: https://issues.apache.org/jira/browse/NIFI-2415
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Haimo Liu
>Assignee: Matt Burgess
>Priority: Critical
> Fix For: 1.0.0, 1.0.0-Beta
>
> Attachments: Screen Shot 2016-07-27 at 11.10.45 PM.png
>
>
> running NIFI in a clustered mode, 7/27 build
> Both GenerateTableFetch and QueryDatabaseTable cannot store state in a
> clustered mode (checked ListFile, can store state successfully)
> see attached screenshot, trace below:
> 2016-07-27 23:25:00,014 INFO [ProcessThread(sid:1 cport:-1):]
> o.a.z.server.PrepRequestProcessor Got user-level KeeperException when
> processing sessionid:0x2562f7875130009 type:create cxid:0xe4d
> zxid:0x73733 txntype:-1 reqpath:n/a Error
> Path:/nifi/components/2f810bb3-0156-1000--16128f8b
> Error:KeeperErrorCode = InvalidACL for
> /nifi/components/2f810bb3-0156-1000--16128f8b
> 2016-07-27 23:25:00,017 WARN [Framework Task Thread Thread-1]
> o.a.n.c.s.m.StandardStateManagerProvider Component with ID {} was removed
> from NiFi instance but failed to clear clustered state for the component
> java.io.IOException: Failed to set cluster-wide state in ZooKeeper for
> component with ID 2f810bb3-0156-1000--16128f8b
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:343)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:283)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:228)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.clear(ZooKeeperStateProvider.java:453)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.state.StandardStateManager.clear(StandardStateManager.java:85)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.state.manager.StandardStateManagerProvider.onComponentRemoved(StandardStateManagerProvider.java:276)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.groups.StandardProcessGroup$1.run(StandardProcessGroup.java:730)
> [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [na:1.8.0_77]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [na:1.8.0_77]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [na:1.8.0_77]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [na:1.8.0_77]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [na:1.8.0_77]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [na:1.8.0_77]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]
> Caused by: org.apache.zookeeper.KeeperException$InvalidACLException:
> KeeperErrorCode = InvalidACL for
> /nifi/components/2f810bb3-0156-1000--16128f8b
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:121)
> ~[zookeeper-3.4.6.jar:3.4.6-1569965]
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> ~[zookeeper-3.4.6.jar:3.4.6-1569965]
> at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:783)
> ~[zookeeper-3.4.6.jar:3.4.6-1569965]
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.createNode(ZooKeeperStateProvider.java:360)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:321)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> ... 13 common frames omitted
--
This message was sent by Atlassian
[jira] [Commented] (NIFI-2415) GenerateTableFetch/QueryDatabaseTable cannot store state
[
https://issues.apache.org/jira/browse/NIFI-2415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16571786#comment-16571786
]
Daniel commented on NIFI-2415:
--
Still seeing this, what was the fix then if not a bug?
> GenerateTableFetch/QueryDatabaseTable cannot store state
>
>
> Key: NIFI-2415
> URL: https://issues.apache.org/jira/browse/NIFI-2415
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Haimo Liu
>Assignee: Matt Burgess
>Priority: Critical
> Fix For: 1.0.0, 1.0.0-Beta
>
> Attachments: Screen Shot 2016-07-27 at 11.10.45 PM.png
>
>
> running NIFI in a clustered mode, 7/27 build
> Both GenerateTableFetch and QueryDatabaseTable cannot store state in a
> clustered mode (checked ListFile, can store state successfully)
> see attached screenshot, trace below:
> 2016-07-27 23:25:00,014 INFO [ProcessThread(sid:1 cport:-1):]
> o.a.z.server.PrepRequestProcessor Got user-level KeeperException when
> processing sessionid:0x2562f7875130009 type:create cxid:0xe4d
> zxid:0x73733 txntype:-1 reqpath:n/a Error
> Path:/nifi/components/2f810bb3-0156-1000--16128f8b
> Error:KeeperErrorCode = InvalidACL for
> /nifi/components/2f810bb3-0156-1000--16128f8b
> 2016-07-27 23:25:00,017 WARN [Framework Task Thread Thread-1]
> o.a.n.c.s.m.StandardStateManagerProvider Component with ID {} was removed
> from NiFi instance but failed to clear clustered state for the component
> java.io.IOException: Failed to set cluster-wide state in ZooKeeper for
> component with ID 2f810bb3-0156-1000--16128f8b
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:343)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:283)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:228)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.clear(ZooKeeperStateProvider.java:453)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.state.StandardStateManager.clear(StandardStateManager.java:85)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.state.manager.StandardStateManagerProvider.onComponentRemoved(StandardStateManagerProvider.java:276)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.groups.StandardProcessGroup$1.run(StandardProcessGroup.java:730)
> [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [na:1.8.0_77]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [na:1.8.0_77]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [na:1.8.0_77]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [na:1.8.0_77]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [na:1.8.0_77]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [na:1.8.0_77]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]
> Caused by: org.apache.zookeeper.KeeperException$InvalidACLException:
> KeeperErrorCode = InvalidACL for
> /nifi/components/2f810bb3-0156-1000--16128f8b
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:121)
> ~[zookeeper-3.4.6.jar:3.4.6-1569965]
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> ~[zookeeper-3.4.6.jar:3.4.6-1569965]
> at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:783)
> ~[zookeeper-3.4.6.jar:3.4.6-1569965]
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.createNode(ZooKeeperStateProvider.java:360)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.setState(ZooKeeperStateProvider.java:321)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> ... 13 common frames omitted
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (NIFI-5488) Support
[ https://issues.apache.org/jira/browse/NIFI-5488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel resolved NIFI-5488. -- Resolution: Invalid > Support > > > Key: NIFI-5488 > URL: https://issues.apache.org/jira/browse/NIFI-5488 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Daniel >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-5489) Support Attribute Expressions with AMQP Processors
Daniel created NIFI-5489: Summary: Support Attribute Expressions with AMQP Processors Key: NIFI-5489 URL: https://issues.apache.org/jira/browse/NIFI-5489 Project: Apache NiFi Issue Type: Improvement Affects Versions: 1.7.1 Reporter: Daniel Particularly the fields: host, virtualhost and username. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-5488) Support
Daniel created NIFI-5488: Summary: Support Key: NIFI-5488 URL: https://issues.apache.org/jira/browse/NIFI-5488 Project: Apache NiFi Issue Type: Improvement Reporter: Daniel -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-5483) Make Integration Tests Work With Large Flow Files
Daniel created NIFI-5483: Summary: Make Integration Tests Work With Large Flow Files Key: NIFI-5483 URL: https://issues.apache.org/jira/browse/NIFI-5483 Project: Apache NiFi Issue Type: Improvement Components: Tools and Build Affects Versions: 1.7.1 Reporter: Daniel It seems, at it's current state, integration tests do not work with very large files (such as over 2 GB). I believe this stems from the fact that MockFlowFile uses a byte array to to copy data and a byte array can not hold over 2147483647 bytes. For things like BigQuery, which supports a 15 terabyte payload, testing becomes difficult. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-5472) Trackpad Support / AKA pan canvas with scroll
Daniel created NIFI-5472: Summary: Trackpad Support / AKA pan canvas with scroll Key: NIFI-5472 URL: https://issues.apache.org/jira/browse/NIFI-5472 Project: Apache NiFi Issue Type: Improvement Components: Core UI Reporter: Daniel Hi, many canvas based apps support so called "trackpad mode", which allow you to pan the canvas using the scroll up/down or left/right gestures. To zoom, you instead use the pinch gesture. This would be a wonder addition for trackpad users. Thanks for the consideration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-4535) Set the Page Title to the name of the Root Process Group
[ https://issues.apache.org/jira/browse/NIFI-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16480393#comment-16480393 ] Daniel commented on NIFI-4535: -- Brilliant idea. > Set the Page Title to the name of the Root Process Group > > > Key: NIFI-4535 > URL: https://issues.apache.org/jira/browse/NIFI-4535 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Peter Wicks >Priority: Minor > > NiFi's UI has a hard coded page title of NiFi. I have many servers and it's > hard to keep track of the tabs in Chrome. > Please change the Title of the page so it matches the name of the Root > processor group. This way I can name the root group by server/instance, and > easily identify the right tab/window. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-5160) ConsumeAMQP Processor should support Expression Language
Daniel created NIFI-5160: Summary: ConsumeAMQP Processor should support Expression Language Key: NIFI-5160 URL: https://issues.apache.org/jira/browse/NIFI-5160 Project: Apache NiFi Issue Type: Improvement Reporter: Daniel The following fields should support expression language: queue host name port user name virtual host -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-5160) ConsumeAMQP Processor should support Expression Language
[ https://issues.apache.org/jira/browse/NIFI-5160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel updated NIFI-5160: - Description: ConsumeAMQP Processor should support Expression Language. The following fields should support expression language: queue host name port user name virtual host was: The following fields should support expression language: queue host name port user name virtual host > ConsumeAMQP Processor should support Expression Language > > > Key: NIFI-5160 > URL: https://issues.apache.org/jira/browse/NIFI-5160 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Daniel >Priority: Major > > ConsumeAMQP Processor should support Expression Language. The following > fields should support expression language: > > queue > host name > port > user name > virtual host -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (NIFI-4260) ExecuteFlumeSink not working with Sink Type "avro".
[
https://issues.apache.org/jira/browse/NIFI-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158821#comment-16158821
]
Daniel edited comment on NIFI-4260 at 9/8/17 4:17 PM:
--
can you please upload the modified
*nifi-flume-nar-1.3.0.nar*
and the
*nifi-flume-nar-1.2.0.3.0.1.0-43.nar*
as a quick-fix for us?
was (Author: dash42):
can you please upload the modified
*nifi-flume-nar-1.3.0.nar
*and the
*nifi-flume-nar-1.2.0.3.0.1.0-43.nar
*as a quick-fix for us?
> ExecuteFlumeSink not working with Sink Type "avro".
> ---
>
> Key: NIFI-4260
> URL: https://issues.apache.org/jira/browse/NIFI-4260
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.2.0, 1.3.0
>Reporter: Sebastian Schlitte
>
> After upgrading NiFi from 1.1.2 to 1.2.0, ExecuteFlumeSink with sink type
> "avro" stops transmitting data and throws the error quoted below. The problem
> persists after upgrading to 1.3.0.
> Replacing avro-ipc-1.7.4.jar with avro-ipc-1.8.1.jar in
> nifi-flume-nar-1.3.0.nar solves the issue.
> {{2017-08-02 10:28:51,142 ERROR [Timer-Driven Process Thread-6]
> o.a.n.processors.flume.ExecuteFlumeSink
> ExecuteFlumeSink[id=98da368f-015d-1000--9
> 6768472] ExecuteFlumeSink[id=98da368f-015d-1000--96768472] failed to
> process due to org.apache.nifi.processor.exception.ProcessException: Flume
> event delivery failed; rolling back session: {}
> org.apache.nifi.processor.exception.ProcessException: Flume event delivery
> failed
> at
> org.apache.nifi.processors.flume.ExecuteFlumeSink.onTrigger(ExecuteFlumeSink.java:145)
> at
> org.apache.nifi.processors.flume.AbstractFlumeProcessor.onTrigger(AbstractFlumeProcessor.java:148)
> at
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1118)
> at
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:144)
> at
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
> at
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.flume.EventDeliveryException: Failed to send events
> at
> org.apache.flume.sink.AbstractRpcSink.process(AbstractRpcSink.java:392)
> at
> org.apache.nifi.processors.flume.ExecuteFlumeSink.onTrigger(ExecuteFlumeSink.java:143)
> ... 12 common frames omitted
> Caused by: org.apache.flume.EventDeliveryException: NettyAvroRpcClient {
> host: target.linux.dummy, port: 14100 }: Failed to send batch
> at
> org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:315)
> at
> org.apache.flume.sink.AbstractRpcSink.process(AbstractRpcSink.java:376)
> ... 13 common frames omitted
> Caused by: org.apache.flume.EventDeliveryException: NettyAvroRpcClient {
> host: target.linux.dummy, port: 14100 }: RPC request exception
> at
> org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:365)
> at
> org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:303)
> ... 14 common frames omitted
> Caused by: java.util.concurrent.ExecutionException:
> java.lang.AbstractMethodError:
> org.apache.avro.specific.SpecificFixed.getSchema()Lorg/apache/avro/S
> chema;
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at
> org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:357)
> ... 15 common frames omitted
> Caused by: java.lang.AbstractMethodError:
> org.apache.avro.specific.SpecificFixed.getSchema()Lorg/apache/avro/Schema;
> at
> org.apache.avro.specific.SpecificFixed.(SpecificFixed.java:36)
> at org.apache.avro.ipc.MD5.(MD5.java:16)
> at org.apache.avro.ipc.Requestor.writeHandshake(Requestor.java:200)
> at org.apache.avro.ipc.Requestor.access$300(Requestor.java:52)
> at org.apach
[jira] [Comment Edited] (NIFI-4260) ExecuteFlumeSink not working with Sink Type "avro".
[
https://issues.apache.org/jira/browse/NIFI-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158821#comment-16158821
]
Daniel edited comment on NIFI-4260 at 9/8/17 4:17 PM:
--
can you please upload the modified
*nifi-flume-nar-1.3.0.nar
*and the
*nifi-flume-nar-1.2.0.3.0.1.0-43.nar
*as a quick-fix for us?
was (Author: dash42):
can you please upload the modified nifi-flume-nar-1.3.0.nar as a quick-fix for
us?
> ExecuteFlumeSink not working with Sink Type "avro".
> ---
>
> Key: NIFI-4260
> URL: https://issues.apache.org/jira/browse/NIFI-4260
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.2.0, 1.3.0
>Reporter: Sebastian Schlitte
>
> After upgrading NiFi from 1.1.2 to 1.2.0, ExecuteFlumeSink with sink type
> "avro" stops transmitting data and throws the error quoted below. The problem
> persists after upgrading to 1.3.0.
> Replacing avro-ipc-1.7.4.jar with avro-ipc-1.8.1.jar in
> nifi-flume-nar-1.3.0.nar solves the issue.
> {{2017-08-02 10:28:51,142 ERROR [Timer-Driven Process Thread-6]
> o.a.n.processors.flume.ExecuteFlumeSink
> ExecuteFlumeSink[id=98da368f-015d-1000--9
> 6768472] ExecuteFlumeSink[id=98da368f-015d-1000--96768472] failed to
> process due to org.apache.nifi.processor.exception.ProcessException: Flume
> event delivery failed; rolling back session: {}
> org.apache.nifi.processor.exception.ProcessException: Flume event delivery
> failed
> at
> org.apache.nifi.processors.flume.ExecuteFlumeSink.onTrigger(ExecuteFlumeSink.java:145)
> at
> org.apache.nifi.processors.flume.AbstractFlumeProcessor.onTrigger(AbstractFlumeProcessor.java:148)
> at
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1118)
> at
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:144)
> at
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
> at
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.flume.EventDeliveryException: Failed to send events
> at
> org.apache.flume.sink.AbstractRpcSink.process(AbstractRpcSink.java:392)
> at
> org.apache.nifi.processors.flume.ExecuteFlumeSink.onTrigger(ExecuteFlumeSink.java:143)
> ... 12 common frames omitted
> Caused by: org.apache.flume.EventDeliveryException: NettyAvroRpcClient {
> host: target.linux.dummy, port: 14100 }: Failed to send batch
> at
> org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:315)
> at
> org.apache.flume.sink.AbstractRpcSink.process(AbstractRpcSink.java:376)
> ... 13 common frames omitted
> Caused by: org.apache.flume.EventDeliveryException: NettyAvroRpcClient {
> host: target.linux.dummy, port: 14100 }: RPC request exception
> at
> org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:365)
> at
> org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:303)
> ... 14 common frames omitted
> Caused by: java.util.concurrent.ExecutionException:
> java.lang.AbstractMethodError:
> org.apache.avro.specific.SpecificFixed.getSchema()Lorg/apache/avro/S
> chema;
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at
> org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:357)
> ... 15 common frames omitted
> Caused by: java.lang.AbstractMethodError:
> org.apache.avro.specific.SpecificFixed.getSchema()Lorg/apache/avro/Schema;
> at
> org.apache.avro.specific.SpecificFixed.(SpecificFixed.java:36)
> at org.apache.avro.ipc.MD5.(MD5.java:16)
> at org.apache.avro.ipc.Requestor.writeHandshake(Requestor.java:200)
> at org.apache.avro.ipc.Requestor.access$300(Requestor.java:52)
> at org.apache.avro.ipc.Requestor$Request.getBytes(Requestor.j
