[ERROR] [OneForOneStrategy] Wrong FS: file:/home/aml/ur/engine.json, expected: hdfs://localhost:9000

88 views
Skip to first unread message

Michael Zhou

unread,
Mar 20, 2019, 9:48:21 AM3/20/19
to actionml-user
Got this error when running the universal recommender integration test. Any idea what this is?

Pat Ferrel

unread,
Mar 20, 2019, 2:59:45 PM3/20/19
to Michael Zhou, actionml-user
What are you trying to do when you get this?
--
You received this message because you are subscribed to the Google Groups "actionml-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to actionml-use...@googlegroups.com.
To post to this group, send email to action...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/actionml-user/3f18a233-9c65-48f0-9495-9591932dd7a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Michael Zhou

unread,
Mar 20, 2019, 3:03:25 PM3/20/19
to Pat Ferrel, actionml-user
It came from "pio deploy". See https://lists.apache.org/thread.html/a0d0b8241f4c24dbb75bdb7b1621c625710cab04f0a9b89c37842eed@<user.predictionio.apache.org> for more details.
Update: Seems like a regression introduced by pio 0.14.0. It works after I downgraded to pio 0.13.0.
In particular, I suspect this diff https://github.com/apache/predictionio/pull/494/files#diff-167f4e9c1445b1f87aad1dead8da208c to have caused the issue.

Pat Ferrel

unread,
Mar 20, 2019, 3:44:06 PM3/20/19
to Michael Zhou, actionml-user, us...@predictionio.apache.org
What line in that PR? It is rather large.

The URI is not correct. To use HDFS and a local filesystem you would use file:///home/aml/ur/engine.json

I’m not sure where this URI is being generated but it is being generated incorrectly. You should be able to pass in the full URI explicitly to use either hdfs or file in `pio train` and/or `pio deploy`. The default in 0.13.0 was to look in the directory you are cded into and read engine.json so this may be a broken assumption in 0.14.0. Passing an explicit location may solve this.

BTW if the assumption is causing a bad URI to be generated, it is a bug and should be filed.

Anyone else know a better answer?

Michael Zhou

unread,
Mar 20, 2019, 3:46:50 PM3/20/19
to Pat Ferrel, actionml-user, us...@predictionio.apache.org
Line 84 in EngineServerPluginContext.scala seems to change how the URI gets generated: https://github.com/apache/predictionio/pull/494/files#diff-167f4e9c1445b1f87aad1dead8da208cR84

Pat Ferrel

unread,
Mar 23, 2019, 5:28:54 PM3/23/19
to Michael Zhou, us...@predictionio.apache.org, actionml-user
The UR for PredictionIO was last tested on PIO 0.12.1. We have moved it to our next-gen ML Server called Harness.

If you want to use it with PIO 0.14.0 you should make sure the build.sbt of the UR has the same deps as the build.sbt for PIO. In otehr words make sure the version numbers match. The UR in any flavor requires Elasticsearch 5.x, ES 6.x will not work.

In due time we’ll go back and get it upgraded for PIO 0.14.0. If you are in a hurry, you can try upgrading yourself or use PIO 0.12.1.

Not sure this is the root of your problem but will need to be addressed in any case.
Reply all
Reply to author
Forward
0 new messages