[ 
https://issues.apache.org/jira/browse/GRIFFIN-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605153#comment-16605153
 ] 

Lionel Liu commented on GRIFFIN-190:
------------------------------------

Hi [~cwoytasik], you might need to check for some information.

1. Assume you're using the default env.json, there should be result persisted 
in hdfs if the measure job succeed, you can find the results in the path: 
hdfs:///griffin/persist/<job_name>/, there will be several directories named as 
the timestamp of job triggered, inside there lists the metrics.
 * If the "_METRICS" file seems good, it means that the job succeed in spark.
 * If the "_METRICS" doesn't exist, we have to find the yarn log of the spark 
application for the job. In that way, we need to find the application id in 
livy log or griffin service log, then fetch yarn log by this: 
yarn logs -applicationId <application id> > app.log
To export the application log into app.log, then you can find the ERROR msg in 
that log.

2. If the results exist in hdfs, we can try to query them from ES like this: 

curl -XGET 
'<ES_IP>:9200/griffin/accuracy/_search?pretty&filter_path=hits.hits._source' -d 
'\{"query":{"match_all":{}},  "sort": [\{"tmst": {"order": "asc"}}]}'

If it doesn't exist, there might be something wrong when spark application 
submit metrics to ES.

> 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)

Reply via email to