AFAIK, the Heroku support is fairly new so not surprising that a multiple engine template has trouble. Multiple Algorithms in a Template are fairly rare. I’d ask Heroku what is going on.
BTW what are you using this for? There are other ways to get similar products—some of which may work better. For instance is there a reason for multiple algorithms? On Jan 9, 2017, at 10:45 AM, Daniel O' Shaughnessy <[email protected]> wrote: Hi, I'm attempting to add a like/dislike event to the ecom recommender ( as per http://predictionio.incubator.apache.org/templates/similarproduct/multi-events-multi-algos/ <http://predictionio.incubator.apache.org/templates/similarproduct/multi-events-multi-algos/> ). This method combines the results of 2 separate algorithms in the Serving class. When I deploy this using the predictionIO Heroku buildpack it seems to deploy and run the release command OK but when I check the Heroku logs it fails here: 2017-01-09T15:32:44.905195+00:00 app[web.1]: [INFO] [Engine] Using persisted model 2017-01-09T15:32:44.912783+00:00 app[web.1]: [INFO] [Engine] Loaded model com.dos.sfdc.ECommModel for algorithm com.dos.sfdc.ECommAlgorithm 2017-01-09T15:32:45.307111+00:00 app[web.1]: [INFO] [Engine] Custom-persisted model detected for algorithm com.dos.sfdc.LikeAlgorithm 2017-01-09T15:32:45.668678+00:00 app[web.1]: [ERROR] [OneForOneStrategy] Cannot call methods on a stopped SparkContext. 2017-01-09T15:32:45.668690+00:00 app[web.1]: This stopped SparkContext was created at: 2017-01-09T15:32:45.668691+00:00 app[web.1]: 2017-01-09T15:32:45.668692+00:00 app[web.1]: org.apache.spark.SparkContext.<init>(SparkContext.scala:82) 2017-01-09T15:32:45.668693+00:00 app[web.1]: org.apache.predictionio.workflow.WorkflowContext$.apply(WorkflowContext.scala:45) 2017-01-09T15:32:45.668694+00:00 app[web.1]: org.apache.predictionio.workflow.CreateServer$.createServerActorWithEngine(CreateServer.scala:228) Anyone come across this before? Thanks, Daniel.
