Sorry to respond a bit late. I just found this.
I don't know pacemaker leaves log for receiving/sending, but since
heartbeat was written to ZK (unless you enable Pacemaker), you can check ZK
to not updating heartbeat. If it is, and your UI shows updated metrics,
then Pacemaker is working well. (si
Hi Jungtaek, thanks for the response.
1. My JDK version is 1.7.0_65.
2. The error went away on building with JDK 7 and using the custom jar
but
3. The error also went away when I built with JDK 8 and used the custom
jar.
I used JDK 7 in both cases for all the daemons. I am not real
Hi Abhishek,
I haven't see this behavior before.
1. What's your JDK version?
2. If you don't mind, could you confirm that your link is the cause?
- build Storm 1.0.2 source code by `mvn clean install -DskipTests` with JDK
7
- replace storm-core jar in lib directory with custom built jar
- run pa
Hello, I am using storm 1.0.2. When I start the pacemaker daemon and then
start nimbus, I see the following error in pacemaker.log repetitively and
can't submit topologies.
WARNING: An exception was thrown by a user handler while handling an
>> exception event ([id: 0xa4126833, /127.0.0.1:43693 =>