Member since
01-04-2017
39
Posts
1
Kudos Received
0
Solutions
11-27-2017
01:24 PM
Thanks @asubramanian,
I have cleared the existing Elasticsearch indices. We have installed the Metron 0.4.1 manually in Ubuntu 14 as per the steps provided below URL,
https://community.hortonworks.com/articles/88843/manually-installing-apache-metron-on-ubuntu-1404.html
Uploaded Elasticsearch templates into ES and executed sensor-stubs. Now it is working.
... View more
11-25-2017
12:34 PM
I have installed Metron 0.4.x in Ubuntu 14. I have started REST, Metron Management and Alert UI. But Alert is always empty for any search criteria. Is there any guideline to use alert UI. Note: Data available in Elasticsearch
... View more
Labels:
03-27-2017
05:04 AM
Thanks for reply, @SBandaru We have verified the proxy setting and its looks fine as per the provided link. @Jay SenSharma We have applied ACL's as you have mentioned but issue still there. Please let us know if there any other ways to fix this issue.
... View more
03-24-2017
02:55 PM
I have executed Hive queries but Tez view says "No data available". When I click "History" links in RM it redirect to Tez view. Tez view shows the below error. Details:
{ "trace": "{\"exception\":\"NotFoundException\",\"message\":\"java.lang.Exception: Timeline entity { id: tez_application_1490359925913_0002, type: TEZ_APPLICATION } is not found\",\"javaClassName\":\"org.apache.hadoop.yarn.webapp.NotFoundException\"}", "message": "Failed to fetch results by the proxy from url: http://localhost:8188/ws/v1/timeline/TEZ_APPLICATION/tez_application_1490359925913_0002?_=1490365592944&user.name=admin", "status": 404
} Request:
{ "adapterName": "app", "url": "http://localhost:8080/api/v1/views/TEZ/versions/0.7.0.2.5.3.0-136/instances/TEZ_CLUSTER_INSTANCE/resources/atsproxy/ws/v1/timeline/TEZ_APPLICATION/tez_application_1490359925913_0002", "responseHeaders": {
"User": "admin",
"Server": "Jetty(8.1.19.v20160209)",
"X-Frame-Options": "SAMEORIGIN",
"Content-Length": "489",
"X-XSS-Protection": "1; mode=block",
"Content-Type": "application/json"
} } Stack:
Error: Adapter operation failed at ember$data$lib$adapters$errors$AdapterError.EmberError (http://localhost:8080/views/TEZ/0.7.0.2.5.3.0-136/TEZ_CLUSTER_INSTANCE/assets/vendor.js:24586:21) at ember$data$lib$adapters$errors$AdapterError (http://localhost:8080/views/TEZ/0.7.0.2.5.3.0-136/TEZ_CLUSTER_INSTANCE/assets/vendor.js:80222:50) at Class.handleResponse (http://localhost:8080/views/TEZ/0.7.0.2.5.3.0-136/TEZ_CLUSTER_INSTANCE/assets/vendor.js:81517:16) at Class.hash.error (http://localhost:8080/views/TEZ/0.7.0.2.5.3.0-136/TEZ_CLUSTER_INSTANCE/assets/vendor.js:81597:33)
at fire (http://localhost:8080/views/TEZ/0.7.0.2.5.3.0-136/TEZ_CLUSTER_INSTANCE/assets/vendor.js:3320:30) at Object.fireWith [as rejectWith] (http://localhost:8080/views/TEZ/0.7.0.2.5.3.0-136/TEZ_CLUSTER_INSTANCE/assets/vendor.js:3432:7) at done (http://localhost:8080/views/TEZ/0.7.0.2.5.3.0-136/TEZ_CLUSTER_INSTANCE/assets/vendor.js:8487:14) at XMLHttpRequest.<anonymous> (http://localhost:8080/views/TEZ/0.7.0.2.5.3.0-136/TEZ_CLUSTER_INSTANCE/assets/vendor.js:8826:9 I have checked the Application log and its seems to be fine and no error, yarn logs -applicationId application_1490359925913_0002
... View more
Labels:
01-18-2017
12:34 PM
yarn logs -applicationId <application_ID> .. Helped me to identify the issue.. It is a permission issue for the user and I have fixed it.
... View more
01-18-2017
10:35 AM
But no error message in the stderr log.. Is there any workaround to fix this issue...
... View more
01-18-2017
10:33 AM
Yes I got the below error from Oozie, 2017-01-18 09:19:56,597 WARN ShellActionExecutor:523 - SERVER[] USER[ambari-qa] GROUP[-] TOKEN[] APP[shell-wf] JOB[0000055-170117070035733-oozie-oozi-W] ACTION[0000055-170117070035733-oozie-oozi-W@shell-node] Launcher ERROR, reason: Main class [org.apache.oozie.action.hadoop.ShellMain], exit code [1]
... View more
01-18-2017
10:24 AM
I have tried the example provided in the Hortonwork tutorial, http://hortonworks.com/hadoop-tutorial/defining-processing-data-end-end-data-pipeline-apache-falcon/ I have followed the steps has provided in that tutorial but facing issue when executing "rawEmailIngestProcess", all the Jobs are KILLLED. I have followed the below links to identify root cause, Checked in Resouremanger Log. Checked in Oozie log. https://community.hortonworks.com/articles/9148/troubleshooting-an-oozie-flow.html No error message in resource manger log, Found the error in the oozie log file. Launcher ERROR, reason: Main class [org.apache.oozie.action.hadoop.ShellMain], exit code [1]
... View more
Labels:
01-17-2017
06:04 AM
I have installed Apache Atlas using Ambari and tried the Atlas + Ranger Integration using Tag. I don't understand about the Tag Attribute and its usage. I have created attribute "word" but do not know how and when it is useful. What is the purpose of tag attribute?. Can anyone provide complete example of using Tag attributes and how it will be used in Atlas?. I dont think tag attributes are useful in Ranger and it can be used only used within Atlas. Thanks, Uvaraj.S
... View more
Labels:
01-05-2017
02:06 PM
I have installed HDP 2.5 components using Ambari. All the services started and working fine without any issue except Oozie. Got the below error, ERROR XBM0A: The database directory '/data/hadoop/oozie/data/oozie-db' exists. However, it does not contain the expected 'service.properties' file. Perhaps Derby was brought down in the middle of creating this database. You may want to delete this directory and try creating the database again.
at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
at org.apache.derby.impl.services.monitor.StorageFactoryService.vetService(Unknown Source)
at org.apache.derby.impl.services.monitor.StorageFactoryService.access$900(Unknown Source)
at org.apache.derby.impl.services.monitor.StorageFactoryService$10.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.derby.impl.services.monitor.StorageFactoryService.createServiceRoot(Unknown Source)
at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(Unknown Source)
at org.apache.derby.impl.services.monitor.BaseMonitor.createPersistentService(Unknown Source)
at org.apache.derby.iapi.services.monitor.Monitor.createPersistentService(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.createDatabase(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection40.<init>(Unknown Source)
at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source)
at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
at org.apache.derby.jdbc.Driver20.connect(Unknown Source)
at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:247)
at org.apache.oozie.tools.OozieDBCLI.createConnection(OozieDBCLI.java:953)
at org.apache.oozie.tools.OozieDBCLI.validateConnection(OozieDBCLI.java:959)
at org.apache.oozie.tools.OozieDBCLI.createDB(OozieDBCLI.java:189)
at org.apache.oozie.tools.OozieDBCLI.run(OozieDBCLI.java:128)
at org.apache.oozie.tools.OozieDBCLI.main(OozieDBCLI.java:79)
... View more
Labels: