[
https://issues.apache.org/jira/browse/GRIFFIN-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606483#comment-16606483
]
Michael Kisly commented on GRIFFIN-190:
---------------------------------------
Hi Lionel,
The job appears to be failing somewhere between the interaction with livy/spark
and hdfs. When we run a postman request to livy 8998 and use something like
the following "file": "hdfs://localhost:9000/example/" it seems to resolve the
path fine. When running the griffin job livy reports in an error in its logs of
the following: ERROR SparkProcApp: spark-submit exited with code 1 . I've
found some different behavior when editing the path to the jar files in the
sparkJob.Properties but am unsure of how the address should be specified. When
using something sparkJob.file=hdfs://localhost:9000/griffin/griffin-measure.jar
we get an error wrong fs expected file:/// so we then changed the path of the
jars to hdfs:///griffin/ and hdfs:///livy/ however now we just get that 1 error
code. Also in the application.Properties we have the following specified
fs.defaultFS = hdfs://localhost:9000 . No applications appear to get created
in yarn
Thanks,
Mike
> Blank Health and DQ Metrics Screen
> ----------------------------------
>
> Key: GRIFFIN-190
> URL: https://issues.apache.org/jira/browse/GRIFFIN-190
> Project: Griffin (Incubating)
> Issue Type: Bug
> Affects Versions: 0.2.0-incubating
> Reporter: Cory Woytasik
> Priority: Major
>
> Griffin is up and running. We have both an accuracy measure and a profiling
> measure that is set to run every minute via jobs. When we click the chart
> icon next to the job we receive a "no content" message. When we click on the
> Health link or DQ Metrics link they think for a second and then display a
> blank screen. We are thinking this might be ES related, but aren't
> completely sure. Need some help. We assume it's a path or property setup
> issue. Here are the versions we are running:
> Hive - 3.1.0
> Elasticsearch - 5.3.1
> griffin - 0.2.0
> hadoop - 3.1.1
> livy - 0.3.0
> spark - 2.3.1
> Using postgres too
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
