hi Sunil Muniyal,

Could you check this property in your griffin properties file?

internal.event.listeners



Thanks,

William


On Thu, Sep 3, 2020 at 11:05 PM Sunil Muniyal <[email protected]>
wrote:

> Hello,
>
> I am attempting to integrate Griffin with Cloudera Hadoop by following
> below article:
>
> https://github.com/apache/griffin/blob/master/griffin-doc/deploy/deploy-guide.md
>
>
> <https://github.com/apache/griffin/blob/master/griffin-doc/deploy/deploy-guide.md>I
> have followed everything as instructed, apart from below things:
> 1. Using Cloudera Hadoop 5.15 and relevant configurations instead of
> Apache Hadoop
> 2. Not using Elastic search as it is not applicable
> 3. Did not use Livy as it is not applicable.
>
> Maven build is successful and has got 2 jars at service/target and
> measure/target which I have uploaded to HDFS.
>
> However, *starting griffin-service.jar using nohup command* is failing
> with below error:
> *Caused by: java.lang.IllegalArgumentException: Could not resolve
> placeholder 'internal.event.listeners' in string value
> "#{'${internal.event.listeners}'.split(',')}"*
> *        at
> org.springframework.util.PropertyPlaceholderHelper.parseStringValue(PropertyPlaceholderHelper.java:174)
> ~[spring-core-4.3.6.RELEASE.jar!/:4.3.6.RELEASE]*
> *        at
> org.springframework.util.PropertyPlaceholderHelper.replacePlaceholders(PropertyPlaceholderHelper.java:126)
> ~[spring-core-4.3.6.RELEASE.jar!/:4.3.6.RELEASE]*
> *        at
> org.springframework.core.env.AbstractPropertyResolver.doResolvePlaceholders(AbstractPropertyResolver.java:236)
> ~[spring-core-4.3.6.RELEASE.jar!/:4.3.6.RELEASE]*
>
> I have tried to search a lot of articles with no luck.
>
> Would be great if someone could help me to fix this.
>
> Also, attached is the output of nohup command that was written in
> service.out.
>
> Thanks and Regards,
> Sunil Muniyal
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]

Reply via email to