[GitHub] metron issue #943: METRON-1462: Separate ES and Kibana from Metron Mpack

[mmiklavc]

Github user mmiklavc commented on the issue:

https://github.com/apache/metron/pull/943
  
Awesome, thanks @anandsubbu and @nickwallen!


---

[GitHub] metron issue #943: METRON-1462: Separate ES and Kibana from Metron Mpack

[nickwallen]

Github user nickwallen commented on the issue:

https://github.com/apache/metron/pull/943
  
I was able to replicate this same problem in master running on the ubuntu14 
dev environment.  This does not seem to be a problem caused by your PR.  I will 
open a separate defect for this.

+1 That being said, nice work!  


---

[GitHub] metron issue #943: METRON-1462: Separate ES and Kibana from Metron Mpack

[nickwallen]

Github user nickwallen commented on the issue:

https://github.com/apache/metron/pull/943
  
When I spin this up in Ubuntu, the Indexing topology is unable to write to 
Elasticsearch.  This may very well be a resource constraint issues in my 
environment, but I thought I'd mention it before I spend too much more time 
digging into this.
```
2018-04-04 15:51:05.707 o.a.s.d.executor Thread-6-indexingBolt-executor[3 
3] [ERROR] 
org.elasticsearch.client.transport.NoNodeAvailableException: None of the 
configured nodes are available: 
[{#transport#-1}{rZcTXccfSPq4fH4IRLQ0zg}{node1}{127.0.1.1:9300}]
at 
org.elasticsearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:347)
 ~[stormjar.jar:?]
at 
org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:245)
 ~[stormjar.jar:?]
at 
org.elasticsearch.client.transport.TransportProxyClient.execute(TransportProxyClient.java:59)
 ~[stormjar.jar:?]
at 
org.elasticsearch.client.transport.TransportClient.doExecute(TransportClient.java:363)
 ~[stormjar.jar:?]
at 
org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:408)
 ~[stormjar.jar:?]
at 
org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:80)
 ~[stormjar.jar:?]
at 
org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:54)
 ~[stormjar.jar:?]
at 
org.apache.metron.elasticsearch.writer.ElasticsearchWriter.write(ElasticsearchWriter.java:92)
 ~[stormjar.jar:?]
at 
org.apache.metron.writer.BulkWriterComponent.flush(BulkWriterComponent.java:239)
 [stormjar.jar:?]
at 
org.apache.metron.writer.BulkWriterComponent.write(BulkWriterComponent.java:217)
 [stormjar.jar:?]
at 
org.apache.metron.writer.bolt.BulkMessageWriterBolt.execute(BulkMessageWriterBolt.java:236)
 [stormjar.jar:?]
at 
org.apache.storm.daemon.executor$fn__7590$tuple_action_fn__7592.invoke(executor.clj:730)
 [storm-core-1.1.0.2.6.4.0-91.jar:1.1.0.2.6.4.0-91]
at 
org.apache.storm.daemon.executor$mk_task_receiver$fn__7511.invoke(executor.clj:462)
 [storm-core-1.1.0.2.6.4.0-91.jar:1.1.0.2.6.4.0-91]
at 
org.apache.storm.disruptor$clojure_handler$reify__7166.onEvent(disruptor.clj:40)
 [storm-core-1.1.0.2.6.4.0-91.jar:1.1.0.2.6.4.0-91]
at 
org.apache.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:472)
 [storm-core-1.1.0.2.6.4.0-91.jar:1.1.0.2.6.4.0-91]
at 
org.apache.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:451)
 [storm-core-1.1.0.2.6.4.0-91.jar:1.1.0.2.6.4.0-91]
at 
org.apache.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:73)
 [storm-core-1.1.0.2.6.4.0-91.jar:1.1.0.2.6.4.0-91]
at 
org.apache.storm.daemon.executor$fn__7590$fn__7603$fn__7656.invoke(executor.clj:849)
 [storm-core-1.1.0.2.6.4.0-91.jar:1.1.0.2.6.4.0-91]
at org.apache.storm.util$async_loop$fn__553.invoke(util.clj:484) 
[storm-core-1.1.0.2.6.4.0-91.jar:1.1.0.2.6.4.0-91]
at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_112]
```


---

[GitHub] metron issue #943: METRON-1462: Separate ES and Kibana from Metron Mpack

[anandsubbu]

Github user anandsubbu commented on the issue:

https://github.com/apache/metron/pull/943
  
My +1 still holds. Installed both mpacks on a 12-node cluster and was able 
to get bro indices to work successfully. Thanks @mmiklavc !


---

[GitHub] metron issue #943: METRON-1462: Separate ES and Kibana from Metron Mpack

[mmiklavc]

Github user mmiklavc commented on the issue:

https://github.com/apache/metron/pull/943
  
I re-tested this via full dev spin-up from scratch. The dashboard comes up 
as expected.


---

[GitHub] metron issue #943: METRON-1462: Separate ES and Kibana from Metron Mpack

[mmiklavc]

Github user mmiklavc commented on the issue:

https://github.com/apache/metron/pull/943
  
Kick Travis re: profiler test failure


---

[GitHub] metron issue #943: METRON-1462: Separate ES and Kibana from Metron Mpack

[mmiklavc]

Github user mmiklavc commented on the issue:

https://github.com/apache/metron/pull/943
  
@ottobackwards @merrimanr @anandsubbu - I've moved the Kibana dashboard 
from the Elasticsearch MPack to the Metron one. Can you reaffirm your +1's or 
let me know if there's anything more I need to address?


---