[
https://issues.apache.org/jira/browse/PIO-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
WangShiXin updated PIO-201:
---------------------------
Priority: Minor (was: Major)
> Train Deploy seperately cause Error: No valid engine instance found for engine
> ------------------------------------------------------------------------------
>
> Key: PIO-201
> URL: https://issues.apache.org/jira/browse/PIO-201
> Project: PredictionIO
> Issue Type: Bug
> Affects Versions: 0.13.0
> Environment: spark ubuntu
> Reporter: WangShiXin
> Priority: Minor
> Labels: newbie
>
> After i trained on cluster A got log like：
> {quote}[INFO] [Engine$] EngineWorkflow.train completed
> [INFO] [Engine] engineInstanceId=8e334d55-1482-4d79-9b55-e02b91aa0caa
> [INFO] [CoreWorkflow$] Inserting persistent model
> [INFO] [CoreWorkflow$] Updating engine instance
> [INFO] [CoreWorkflow$] Training completed successfully.
> [INFO] [AbstractConnector] Stopped
> Spark@6ec63f8\{HTTP/1.1,[http/1.1]}{0.0.0.0:4041}
> {quote}
>
> then, when deploy on server B use pio deploy,failed:
> {quote}[WARN] [Template$] /home/dev/tmp/deploy/template.json does not exist.
> Template metadata will not be available. (This is safe to ignore if you are
> not working on a template.)
> Sat Jan 05 15:21:17 CST 2019 WARN: Establishing SSL connection without
> server's identity verification is not recommended. According to MySQL
> 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established
> by default if explicit option isn't set. For compliance with existing
> applications not using SSL the verifyServerCertificate property is set to
> 'false'. You need either to explicitly disable SSL by setting useSSL=false,
> or set useSSL=true and provide truststore for server certificate verification.
> [ERROR] [Engine$] No valid engine instance found for engine
> com.example.iti.SimilarRankEngine 099400e4829c88639502c061b9d62ba37405be03.
> Try running 'train' before 'deploy'. Aborting.
> {quote}
>
> When I specify --engine-instance-id with the engineInstanceId got from tail
> of the train log, it work well.
> Now I have to manually copy engineInstanceId from cluster A's log and
> redeploy with engineInstanceId I got when update model.
> This issue did'n appear when train/deploy both run in same server.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
