[ https://issues.apache.org/jira/browse/NIFI-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396248#comment-15396248 ]
Mark Payne commented on NIFI-2337: ---------------------------------- This appears to be a result of CURATOR-337 - there is a bug in the LeaderSelector class that results in this stack trace always being logged if we close a LeaderSelector when we are not the leader. Interestingly, this the only thing logged by this entire class, so I will create a PR that simply shuts off the logger for this class in the meantime. > IllegalMonitorStateException when disconnecting node > ---------------------------------------------------- > > Key: NIFI-2337 > URL: https://issues.apache.org/jira/browse/NIFI-2337 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework > Affects Versions: 1.0.0 > Reporter: Mark Payne > Assignee: Mark Payne > Fix For: 1.0.0 > > > When a node is disconnected from the cluster, it often logs a stacktrace > similar to: > 2016-07-20 20:20:47,814 ERROR [Leader Election Notification Thread-1] > o.a.c.f.recipes.leader.LeaderSelector The leader threw an exception > java.lang.IllegalMonitorStateException: You do not own the lock: > /leaders/Cluster Coordinator > at > org.apache.curator.framework.recipes.locks.InterProcessMutex.release(InterProcessMutex.java:140) > ~[curator-recipes-2.10.0.jar:na] > at > org.apache.curator.framework.recipes.leader.LeaderSelector.doWork(LeaderSelector.java:425) > [curator-recipes-2.10.0.jar:na] > at > org.apache.curator.framework.recipes.leader.LeaderSelector.doWorkLoop(LeaderSelector.java:441) > [curator-recipes-2.10.0.jar:na] > at > org.apache.curator.framework.recipes.leader.LeaderSelector.access$100(LeaderSelector.java:64) > [curator-recipes-2.10.0.jar:na] > at > org.apache.curator.framework.recipes.leader.LeaderSelector$2.call(LeaderSelector.java:245) > [curator-recipes-2.10.0.jar:na] > at > org.apache.curator.framework.recipes.leader.LeaderSelector$2.call(LeaderSelector.java:239) > [curator-recipes-2.10.0.jar:na] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > [na:1.8.0_74] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > [na:1.8.0_74] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > [na:1.8.0_74] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > [na:1.8.0_74] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > [na:1.8.0_74] > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > [na:1.8.0_74] > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > [na:1.8.0_74] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [na:1.8.0_74] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [na:1.8.0_74] > at java.lang.Thread.run(Thread.java:745) [na:1.8.0_74] > This error, I believe, is harmless but is alarming and should be addressed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)