Hi, we're using Nifi to ingest data from a JMS source with relatively high traffic (40-60msg per sec, see also my previous post http://apache-nifi-developer-list.39713.n7.nabble.com/session-recover-behaviour-in-nifi-jms-processor-td14940.html#a14944).
Our cluster setup is: * Nifi 1.1.1 * 3 Nifi nodes (nifi01, nifi02, nifi03) * JMS source is TIBCO We are consuming non-durable from a JMS topic; for this reason, we are using the "primary node only" execution mode in order not to consume a message several times (once per Nifi node). Screenshots of our configuration is attached. This works well in principle - until the master node changes. Then, we see reproducably the following pattern (node names are exemplary): 1) nifi01 is the current primary node, holds a connection to TIBCO, and successfully consumes messages 2) primary node switches from nifi01 to nifi02 3) nifi02 opens a connection to TIBCO and consumes messages successfully 4) nifi01 keeps the connection to TIBCO open, but stops consuming The last point causes trouble, because then TIBCO starts buffering messsages for the consumer nifi01, which does not consume messages -> buffer load increases and puts TIBCO under high pressure. My questions are: a) do we miss anything in our approach / could we make configuration etc. better (screenshots below)? b) I would have assumed that Nifi internally stops a particular processor in "primary node only" when the primary node switches; having a look a the nifi-jms-connector code https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-jms-bundle/nifi-jms-processors/src/main/java/org/apache/nifi/jms/processors/AbstractJMSProcessor.java it seems to me that the @onStopped close() method should do the right thing. Is that correct? I'm grateful for any feedback / pointers how to solve this issue. Many thanks, Dominik nifi_jms_connectionfactory.png <http://apache-nifi-developer-list.39713.n7.nabble.com/file/n15967/nifi_jms_connectionfactory.png> nifi_jms_properties.png <http://apache-nifi-developer-list.39713.n7.nabble.com/file/n15967/nifi_jms_properties.png> nifi_jms_scheduling.png <http://apache-nifi-developer-list.39713.n7.nabble.com/file/n15967/nifi_jms_scheduling.png> -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/nifi-jms-processor-not-closing-connection-properly-in-primary-node-only-execution-mode-tp15967.html Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
