You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "Nick Allen (JIRA)" <ji...@apache.org> on 2017/07/13 18:49:00 UTC
[jira] [Created] (METRON-1043) Profiler Should be Less Dramatic
When Missing Configuration
Nick Allen created METRON-1043:
----------------------------------
Summary: Profiler Should be Less Dramatic When Missing Configuration
Key: METRON-1043
URL: https://issues.apache.org/jira/browse/METRON-1043
Project: Metron
Issue Type: Bug
Reporter: Nick Allen
When the Profiler topology is running, but no Profiler definition is found in Zookeeper, it will log this exception to the Storm logs.
{code}
2017-07-13 18:03:12.219 o.a.m.p.b.ProfileSplitterBolt [ERROR] Unexpected failure: message='Fatal: Unable to find valid profiler definition', tuple='source: kafkaSpout:4, stream: default, id: {}, [[B@468d7611]'
java.lang.IllegalArgumentException: Fatal: Unable to find valid profiler definition
at org.apache.metron.profiler.bolt.ProfileSplitterBolt.doExecute(ProfileSplitterBolt.java:117) ~[stormjar.jar:?]
at org.apache.metron.profiler.bolt.ProfileSplitterBolt.execute(ProfileSplitterBolt.java:97) [stormjar.jar:?]
at org.apache.storm.daemon.executor$fn__6573$tuple_action_fn__6575.invoke(executor.clj:734) [storm-core-1.0.1.2.5.6.0-40.jar:1.0.1.2.5.6.0-40]
at org.apache.storm.daemon.executor$mk_task_receiver$fn__6494.invoke(executor.clj:466) [storm-core-1.0.1.2.5.6.0-40.jar:1.0.1.2.5.6.0-40]
at org.apache.storm.disruptor$clojure_handler$reify__6007.onEvent(disruptor.clj:40) [storm-core-1.0.1.2.5.6.0-40.jar:1.0.1.2.5.6.0-40]
at org.apache.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:451) [storm-core-1.0.1.2.5.6.0-40.jar:1.0.1.2.5.6.0-40]
at org.apache.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:430) [storm-core-1.0.1.2.5.6.0-40.jar:1.0.1.2.5.6.0-40]
at org.apache.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:73) [storm-core-1.0.1.2.5.6.0-40.jar:1.0.1.2.5.6.0-40]
at org.apache.storm.daemon.executor$fn__6573$fn__6586$fn__6639.invoke(executor.clj:853) [storm-core-1.0.1.2.5.6.0-40.jar:1.0.1.2.5.6.0-40]
at org.apache.storm.util$async_loop$fn__554.invoke(util.clj:484) [storm-core-1.0.1.2.5.6.0-40.jar:1.0.1.2.5.6.0-40]
at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_77]
{code}
This is a little too dramatic. This is not 'fatal' nor is it really an error. The Profiler should just log an INFO message stating that there is no configuration found and continue on with life.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)