HI   

这个拓扑 没有获取到topic, 这个是如何配置的 ? 

ALERT_UNIT_TOPOLOGY_APP_SANDBOX 
<http://10.63.64.23:8080/topology.html?id=ALERT_UNIT_TOPOLOGY_APP_SANDBOX-23-1494900983>

2017-05-16 10:57:30.849 o.a.e.a.e.c.i.ZKMetadataChangeNotifyService [INFO] 
Metadata changed isValueVersionId: true, value: spec_version_1494903450729
2017-05-16 10:57:30.850 o.a.e.a.s.MetadataServiceClientImpl [INFO] Requesting 
http://10.63.64.23:9090/rest/metadata/schedulestates/spec_version_1494903450729
2017-05-16 10:57:30.852 o.a.e.a.e.c.i.ZKMetadataChangeNotifyService [INFO] 
Metadata changed isValueVersionId: true, value: spec_version_1494903450729
2017-05-16 10:57:30.853 o.a.e.a.s.MetadataServiceClientImpl [INFO] Requesting 
http://10.63.64.23:9090/rest/metadata/schedulestates/spec_version_1494903450729
2017-05-16 10:57:30.869 o.a.e.a.e.c.i.ZKMetadataChangeNotifyService [INFO] 
Metadata changed isValueVersionId: true, value: spec_version_1494903450729
2017-05-16 10:57:30.869 o.a.e.a.s.MetadataServiceClientImpl [INFO] Requesting 
http://10.63.64.23:9090/rest/metadata/schedulestates/spec_version_1494903450729
2017-05-16 10:57:30.894 o.a.e.a.e.c.i.ZKMetadataChangeNotifyService [INFO] 
Metadata changed isValueVersionId: true, value: spec_version_1494903450729
2017-05-16 10:57:30.894 o.a.e.a.s.MetadataServiceClientImpl [INFO] Requesting 
http://10.63.64.23:9090/rest/metadata/schedulestates/spec_version_1494903450729
2017-05-16 10:57:30.917 o.a.e.a.e.r.AlertBolt [INFO] no new policy with 
AlertBoltSpec 
version:spec_version_1494903450729-topo:ALERT_UNIT_TOPOLOGY_APP_SANDBOX, 
boltPolicyIdsMap {},
 publishPartitions  for this bolt alertBolt0
2017-05-16 10:57:30.918 o.a.e.a.e.s.CorrelationSpout [INFO] new metadata is 
updated version:spec_version_1494903450729-topo:ALERT_UNIT_TOPOLOGY_APP_SANDBOX
2017-05-16 10:57:30.919 o.a.e.a.e.s.CorrelationSpout [INFO] Topics were 
added=[], removed=[], modified=[]   为什么这里是空的  
2017-05-16 10:57:30.919 o.a.e.a.e.s.CorrelationSpout [INFO] after 
CorrelationSpout reloads, 0 kafkaSpouts are generated for 0 topics



HDFS_AUDIT_LOG_MONITOR_APP_SANDBOX 
<http://10.63.64.23:8080/topology.html?id=HDFS_AUDIT_LOG_MONITOR_APP_SANDBOX-22-1494900978>

而这个拓扑是正常在执行 ; 
 
SA|李平|lpn1509
在线游戏事业部-技术部-网管组
phone: 18819381175
email:[email protected]




> 在 2017年5月15日,11:11,lpn1509 <[email protected]> 写道:
> 
> 
> HI 
>  
> it is for what ? 下面这个用来干嘛的? 怎么用? document has nothing about it  ~~~  
> 
>  <PastedGraphic-1.tiff>SA|李平|lpn1509
> 在线游戏事业部-技术部-网管组
> phone: 18819381175
> email:[email protected] <http://corp.netease.com/>
> 
> 
> 
> 
>> 在 2017年5月15日,10:14,lpn1509 <[email protected] 
>> <mailto:[email protected]>> 写道:
>> 
>> alter  spout 拿不到数据 ~  怎么处理? 
>> 
>> 2017-05-15 09:37:51.870 o.a.e.a.e.c.i.ZKMetadataChangeNotifyService [INFO] 
>> Metadata changed isValueVersionId: true, value: spec_version_1494559752711
>> 2017-05-15 09:37:51.871 o.a.e.a.s.MetadataServiceClientImpl [INFO] 
>> Requesting 
>> http://10.63.64.23:9090/rest/metadata/schedulestates/spec_version_1494559752711
>>  
>> <http://10.63.64.23:9090/rest/metadata/schedulestates/spec_version_1494559752711>
>> 2017-05-15 09:37:52.004 o.a.e.a.s.MetadataServiceClientImpl [WARN] List one 
>> entity failed, ignored and continue, 
>> path:/metadata/schedulestates/spec_version_1494559752711
>> com.sun.jersey.api.client.UniformInterfaceException: GET 
>> http://10.63.64.23:9090/rest/metadata/schedulestates/spec_version_1494559752711
>>  
>> <http://10.63.64.23:9090/rest/metadata/schedulestates/spec_version_1494559752711>
>>  returned a response status of 204 No Content
>>         at 
>> com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:609) 
>> ~[stormjar.jar:?]
>>         at 
>> com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:586) 
>> ~[stormjar.jar:?]
>>         at 
>> org.apache.eagle.alert.service.MetadataServiceClientImpl.listOne(MetadataServiceClientImpl.java:182)
>>  [stormjar.jar:?]
>>         at 
>> org.apache.eagle.alert.service.MetadataServiceClientImpl.getVersionedSpec(MetadataServiceClientImpl.java:166)
>>  [stormjar.jar:?]
>>         at 
>> org.apache.eagle.alert.engine.coordinator.impl.ZKMetadataChangeNotifyService.onNewConfig(ZKMetadataChangeNotifyService.java:115)
>>  [stormjar.jar:?]
>>         at 
>> org.apache.eagle.alert.engine.coordinator.impl.ZKMetadataChangeNotifyService.activateFetchMetaData(ZKMetadataChangeNotifyService.java:77)
>>  [stormjar.jar:?]
>>         at 
>> org.apache.eagle.alert.engine.runner.AbstractStreamBolt.prepare(AbstractStreamBolt.java:86)
>>  [stormjar.jar:?]
>>         at 
>> backtype.storm.daemon.executor$fn__5694$fn__5707.invoke(executor.clj:757) 
>> [storm-core-0.10.0.jar:0.10.0]
>>         at backtype.storm.util$async_loop$fn__545.invoke(util.clj:477) 
>> [storm-core-0.10.0.jar:0.10.0]
>>         at clojure.lang.AFn.run(AFn.java:22) [clojure-1.6.0.jar:?]
>>         at java.lang.Thread.run(Thread.java:745) [?:1.8.0_102]
>> 
>>  
>> SA|李平|lpn1509
>> 在线游戏事业部-技术部-网管组
>> phone: 18819381175
>> email:[email protected] <http://corp.netease.com/>
>> 
>> 
>> 
>> 
>>> 在 2017年5月15日,09:51,lpn1509 <[email protected] 
>>> <mailto:[email protected]>> 写道:
>>> 
>>> HI  , 关于 0.5.0 版本的eagle , 其中的alter的模块如何指定读取哪一个TOPIC呢?   
>>> 
>>> 
>>>  
>>> SA|李平|lpn1509
>>> 在线游戏事业部-技术部-网管组
>>> phone: 18819381175
>>> email:[email protected] <http://corp.netease.com/>
>>> 
>>> 
>>> 
>>> 
>>>> 在 2017年5月12日,15:13,lpn1509 <[email protected] 
>>>> <mailto:[email protected]>> 写道:
>>>> 
>>>> HI  
>>>> 
>>>>     麻烦指导一下, 关于 0.5.0 版本的eagle.conf
>>>> 
>>>> 关于一下这部分, 我不想用hbase , 而是选择jdbc方式,选择这种方式, 该如何配置呢?  
>>>> 
>>>> 
>>>> storage {
>>>>   # storage type: ["hbase","jdbc"]
>>>>   # default is "hbase"
>>>>   type = "jdbc"
>>>>   jdbc {
>>>>     username = "eagle"
>>>>     password = "eagle"
>>>>     driverClassName = com.mysql.jdbc.Driver
>>>>     database = "eagle"
>>>>     connection = "jdbc:mysql://10.120.165.104:3306/eagle"
>>>>     }
>>>>  
>>>> SA|李平|lpn1509
>>>> 在线游戏事业部-技术部-网管组
>>>> phone: 18819381175
>>>> email:[email protected] <http://corp.netease.com/>
>>>> 
>>>> 
>>>> 
>>>> 
>>>>> 在 2017年5月8日,16:13,lpn1509 <[email protected] 
>>>>> <mailto:[email protected]>> 写道:
>>>>> 
>>>>> 
>>>>> HI  ,    
>>>>> 
>>>>> For the job analysis, can I use 0.4.0 to do it ? 
>>>>> 
>>>>> or
>>>>> 
>>>>> can i use 0.5.0 for hadoop which is based on java 1.7 
>>>>> 
>>>>> 
>>>>> eagle的0.5.0版本, 我是否可以用来监控 基于java 1.7 的hadoop集群呢? 目前我们的hadoop集群都是基于1.7 
>>>>> 的java的
>>>>>  
>>>>>  SA|李平|lpn1509
>>>>> 在线游戏事业部-技术部-网管组
>>>>> phone: 18819381175
>>>>> email:[email protected] <http://corp.netease.com/>
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>> 在 2017年5月6日,00:30,Edward Zhang <[email protected] 
>>>>>> <mailto:[email protected]>> 写道:
>>>>>> 
>>>>>> Hi LPN,
>>>>>> 
>>>>>> Please kindly subscribe to eagle dev mail list, so you can receive 
>>>>>> message from eagle community.
>>>>>> 
>>>>>> Thanks
>>>>>> Edward
>>>>>> 
>>>>>> 
>>>>>> ---------- Forwarded message ----------
>>>>>> From: Liangfei Su <[email protected] <mailto:[email protected]>>
>>>>>> Date: 2017-05-04 23:22 GMT-07:00
>>>>>> Subject: Re: eage问题咨询
>>>>>> To: [email protected] <mailto:[email protected]>
>>>>>> 
>>>>>> 
>>>>>> Thanks for the interest.
>>>>>> 
>>>>>> For the job analysis, you might follow the instruction by Jijun for eagle
>>>>>> 0.5.0 snapshot.
>>>>>> 
>>>>>> Thanks
>>>>>> Ralph
>>>>>> 
>>>>>> 
>>>>>> 2017-05-05 10:55 GMT+08:00 lpn1509 <[email protected] 
>>>>>> <mailto:[email protected]>>:
>>>>>> 
>>>>>> >
>>>>>> > HI , 试用了eagle 0.4.0版本
>>>>>> >
>>>>>> > 实现了namenode的审计日志的检测功能,
>>>>>> >
>>>>>> > 但是我比较关心的是eagle在集群任务分析、负载分析上的实现, 官网没有这方便的具体的指引, 另外官网的指引与0.4.0版本不太一样
>>>>>> >
>>>>>> > https://cwiki.apache.org/confluence/display/EAG/Hadoop+JMX+Monitoring 
>>>>>> > <https://cwiki.apache.org/confluence/display/EAG/Hadoop+JMX+Monitoring>
>>>>>> >  <
>>>>>> > https://cwiki.apache.org/confluence/display/EAG/Hadoop+JMX+Monitoring 
>>>>>> > <https://cwiki.apache.org/confluence/display/EAG/Hadoop+JMX+Monitoring>>
>>>>>> >
>>>>>> >
>>>>>> > 是否可以给我一些指引资料呢?
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> > SA|李平|lpn1509
>>>>>> > 在线游戏事业部-技术部-网管组
>>>>>> > phone: 18819381175
>>>>>> > email:[email protected] <mailto:[email protected]>
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> 
>>>>> 
>>>> 
>>> 
>> 
> 

Reply via email to