Member since
08-31-2015
81
Posts
115
Kudos Received
17
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1779 | 03-22-2017 03:51 PM | |
925 | 05-04-2016 09:34 AM | |
1015 | 03-24-2016 03:07 PM | |
1094 | 03-24-2016 02:54 PM | |
1014 | 03-24-2016 02:47 PM |
03-24-2016
08:58 AM
3 Kudos
I'm following the instructions for installing Metron here: https://github.com/apache/incubator-metron/tree/master/deployment/amazon-ec2 In the ansible.log, I'm seeing the following error during the ansible [Setup] task:
2016-03-24 03:46:50,950 p=62171 u=gvetticaden | TASK [setup] *******************************************************************
2016-03-24 03:46:51,893 p=62171 u=gvetticaden | fatal: [ec2-54-191-176-45.us-west-2.compute.amazonaws.com]: UNREACHABLE! => {"changed": false, "msg": "SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
2016-03-24 03:46:51,895 p=62171 u=gvetticaden | fatal: [ec2-54-186-187-148.us-west-2.compute.amazonaws.com]: UNREACHABLE! => {"changed": false, "msg": "SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
2016-03-24 03:46:51,913 p=62171 u=gvetticaden | fatal: [ec2-54-201-6-61.us-west-2.compute.amazonaws.com]: UNREACHABLE! => {"changed": false, "msg": "SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
2016-03-24 03:46:51,915 p=62171 u=gvetticaden | fatal: [ec2-54-191-196-153.us-west-2.compute.amazonaws.com]: UNREACHABLE! => {"changed": false, "msg": "SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
2016-03-24 03:46:51,989 p=62171 u=gvetticaden | fatal: [ec2-54-201-176-11.us-west-2.compute.amazonaws.com]: UNREACHABLE! => {"changed": false, "msg": "SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
2016-03-24 03:46:52,021 p=62171 u=gvetticaden | fatal: [ec2-54-191-12-47.us-west-2.compute.amazonaws.com]: UNREACHABLE! => {"changed": false, "msg": "SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
2016-03-24 03:46:52,173 p=62171 u=gvetticaden | fatal: [ec2-54-201-9-33.us-west-2.compute.amazonaws.com]: UNREACHABLE! => {"changed": false, "msg": "SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
2016-03-24 03:46:52,175 p=62171 u=gvetticaden | fatal: [ec2-54-201-175-153.us-west-2.compute.amazonaws.com]: UNREACHABLE! => {"changed": false, "msg": "SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
2016-03-24 03:46:52,308 p=62171 u=gvetticaden | fatal: [ec2-54-201-198-3.us-west-2.compute.amazonaws.com]: UNREACHABLE! => {"changed": false, "msg": "SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
2016-03-24 03:46:52,489 p=62171 u=gvetticaden | fatal: [ec2-54-186-178-244.us-west-2.compute.amazonaws.com]: UNREACHABLE! => {"changed": false, "msg": "SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
How do I resolve this?
... View more
Labels:
- Labels:
-
Apache Metron
12-12-2015
07:48 AM
1 Kudo
very valuable content! great work.
... View more
11-18-2015
01:34 PM
4 Kudos
Repo Description The High Level Reference Architecture consists of the following: HBase - system of record for the documents/images SOLR - system of record for the the metadata and providing the indexing and searching capabilities. When a user queries for a content via metadata, we will use Solr to query the index. The solr query will return a unique hbase row key which will be used to quickly retrieve the image from Hbase. Kafka - Documents will be pushed to Kafka for Streaming, Batch and B2B integration Spring Data Solr and Spring MVC - Provides a REST interface to expose Doc and Index Services Repo Info Github Repo URL https://github.com/georgevetticaden/hdp/tree/master/reference-apps/ecm-app Github account name georgevetticaden/hdp/tree/master/reference-apps Repo name ecm-app
... View more
11-18-2015
12:27 PM
5 Kudos
Repo Description This project is meant to be a reference application/assembly for an IOT use case. The project consists of 5 projects:
trucking-data-simulator - Data simulator trucking-domain-objects - Common trucking domain objects used across projects trucking-storm-topology - Storm Topology to process trucking events in realtime trucking-env-setup - Set of scripts to setup the cluster trucking-web-portal - A web application that allows you to deploy the storm topoloyg and tap into the real-time trucking data using websockets from Active/MQ and Storm Repo Info Github Repo URL https://github.com/georgevetticaden/hdp/tree/master/reference-apps/iot-trucking-app Github account name georgevetticaden/hdp/tree/master/reference-apps Repo name iot-trucking-app
... View more
11-04-2015
08:53 PM
2 Kudos
@Jonas Straub The storm-solr codebase has SolrBoltAction that should be used if you are converting your Storm tuples to SolrInputDocument(s) and indexing them. This SolrBoltAction supports microbatching of these docs and then indexing them via the method SolrBoltAction.sendBatchToSolr. The code base also has a SolrJsonBoltAction that extends SolrBoltAction but should be used if you are indexing Json Docs. I have noticed that SolrJsonBoltAction does not support batch indexing of JSON docs via the ContentStreamUpdateRequest where as the SolrBoltAction does. We need to understand how you do batch indexing of json docs in 1 solr call. I did notice that ContentStreamUpdateRequest.addContentStream just adds content streams to a collection but when putting multiple jsondocs in that collection and then executing the request, solr only indexes 1 item in the collection.
... View more
10-30-2015
03:02 PM
Yup. got it working..my zookeeper connect string needed to have zhroot location which was solr in my case.
... View more
10-30-2015
08:17 AM
Great Tutorial/Article @Ali Bajwa. Great way to start get familiar with Nifi. On question: Did you try and get working the Nifi Twitter Template so that the PutSolrContentStream connected to Solr Cloud instance as opposed to a standard/standalone solr instance.?
... View more
10-12-2015
01:56 PM
Joe, please dont' mention customer names as we dicussed. Please reword your response to remove it.
... View more
09-28-2015
11:53 PM
Great suggestions for the guildellines. Can you add these to the Guidelines on the wiki here: Hortonworks User Forum Guidelines
... View more
09-25-2015
12:56 PM
I plan to move these this from my github to the Gallery
... View more