Thanks Joe. Any insights, what might be triggering this issue on a cluster that is been running for quite some time without any issue? And this happens only on one of the node in the cluster?
Thanks, Ravi Papisetti On 25/01/18, 4:26 PM, "Joe Witt" <[email protected]> wrote: Ravi, I replied to your github/pr comment. You will need to upgrade to get the fix which has been released or you'll need to create your own patched build. Thanks Joe On Thu, Jan 25, 2018 at 5:12 PM, Ravi Papisetti (rpapiset) <[email protected]> wrote: > Hi, > > > > Our NiFi cluster is impacted with > https://issues.apache.org/jira/browse/NIFI-4092?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&focusedCommentId=16150041#comment-16150041 > > > > At this point we are not be able to upgrade our environment, is there any > workaround here to resolve this issue? > > > > Few clarifications: > > 1. We have 3 node cluster, but this warning happens only on one of the > node which is being elected as Primary node (all three are identical). > Primary node is going into connecting state just a second after getting into > “Connected” state. > > 2. This cluster is being in run state for quite some time, this issue > is just popped up, only updates on this environment is updated templates and > new processgroups got created. > > > > Wondering what could have triggered this issue and looking for workaround to > resolve this issue. > > > > Appreciate any help here. > > > > Thanks, > > Ravi Papisetti > > > >
