[jira] [Commented] (PIO-122) always get Error initializing storage client for source ELASTICSEARCH in 0.11 when pio train
[
https://issues.apache.org/jira/browse/PIO-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167425#comment-16167425
]
Donald Szeto commented on PIO-122:
--
Can you provide information on
* how you built PIO 0.11
* the template you are using
* the {{conf/pio-env.sh}} of your PIO 0.11 build
* Elasticsearch version
* detail error message in {{pio.log}} where you run {{pio train}}
?
> always get Error initializing storage client for source ELASTICSEARCH in 0.11
> when pio train
>
>
> Key: PIO-122
> URL: https://issues.apache.org/jira/browse/PIO-122
> Project: PredictionIO
> Issue Type: Bug
> Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: dongjie.shi
>
> Always get this error when I try to run PIO train to test a local PIO with
> HBase and Elasticsearch.
> [ERROR] [Storage$] Error initializing storage client for source ELASTICSEARCH
> Exception in thread "main"
> org.apache.predictionio.data.storage.StorageClientException: Data source
> ELASTICSEARCH was not properly initialized.
> at
> org.apache.predictionio.data.storage.Storage$$anonfun$10.apply(Storage.scala:285)
> at
> org.apache.predictionio.data.storage.Storage$$anonfun$10.apply(Storage.scala:285)
> at scala.Option.getOrElse(Option.scala:120)
> at
> org.apache.predictionio.data.storage.Storage$.getDataObject(Storage.scala:284)
> at
> org.apache.predictionio.data.storage.Storage$.getDataObjectFromRepo(Storage.scala:269)
> at
> org.apache.predictionio.data.storage.Storage$.getMetaDataEngineInstances(Storage.scala:371)
> at
> org.apache.predictionio.workflow.CreateWorkflow$.main(CreateWorkflow.scala:247)
> at
> org.apache.predictionio.workflow.CreateWorkflow.main(CreateWorkflow.scala)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.apache.spark.deploy.SparkSubmit$.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:731)
> at org.apache.spark.deploy.SparkSubmit$.doRunMain$1(SparkSubmit.scala:181)
> at org.apache.spark.deploy.SparkSubmit$.submit(SparkSubmit.scala:206)
> at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:121)
> at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)
> It seems that every component is ok in pio staus:
> [INFO] [Management$] Your system is all ready to go.
> And about the configurations in pio-env.conf, I have checked them for many
> times.
> PIO_FS_BASEDIR=${HOME}/.pio_store
> PIO_FS_ENGINESDIR=${PIO_FS_BASEDIR}/engines
> PIO_FS_TMPDIR=${PIO_FS_BASEDIR}/tmp
> SPARK_HOME=${SPARK_HOME}
> HBASE_CONF_DIR=${HBASE_HOME}/conf
> PIO_STORAGE_REPOSITORIES_METADATA_NAME=pio_meta
> PIO_STORAGE_REPOSITORIES_METADATA_SOURCE=ELASTICSEARCH
> PIO_STORAGE_REPOSITORIES_EVENTDATA_NAME=pio_event
> PIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE=HBASE
> PIO_STORAGE_REPOSITORIES_MODELDATA_NAME=pio_model
> PIO_STORAGE_REPOSITORIES_MODELDATA_SOURCE=LOCALFS
> PIO_STORAGE_SOURCES_ELASTICSEARCH_TYPE=elasticsearch
> PIO_STORAGE_SOURCES_ELASTICSEARCH_CLUSTERNAME=predictionio
> PIO_STORAGE_SOURCES_ELASTICSEARCH_HOSTS=localhost
> PIO_STORAGE_SOURCES_ELASTICSEARCH_PORTS=9300
> PIO_STORAGE_SOURCES_ELASTICSEARCH_HOME=${ELASTICSEARCH_HOME}
> PIO_STORAGE_SOURCES_LOCALFS_TYPE=localfs
> PIO_STORAGE_SOURCES_LOCALFS_PATH=${PIO_FS_BASEDIR}/models
> PIO_STORAGE_SOURCES_HBASE_TYPE=hbase
> PIO_STORAGE_SOURCES_HBASE_HOME=${HBASE_HOME}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
Re: [VOTE] Apache PredictionIO (incubating) 0.12.0 Release (RC2)
I believe those are fixed by PIO-60, PIO-62 and PIO-63 in the release notes. +1 binding from me On Thu, Sep 14, 2017 at 2:13 PM Pat Ferrel wrote: > The last release was hung up by the IPMC regarding content licensing > issues and libraries used by the doc site, which we promised to address in > this release. Have these been resolved, don’t recall the specifics? It > would be great to fly through the IPMC vote without issue. > > > On Sep 14, 2017, at 2:06 PM, Chan Lee wrote: > > This is the vote for 0.12.0 of Apache PredictionIO (incubating). > > The vote will run for at least 72 hours and will close on Sep 17th, 2017. > > The release candidate artifacts can be downloaded here: > https://dist.apache.org/repos/dist/dev/incubator/predi > ctionio/0.12.0-incubating-rc2 > > Test results of RC1 can be found here: https://travis-ci.org/ap > ache/incubator-predictionio/builds/275634960 > > Maven artifacts are built from the release candidate artifacts above, and > are provided as convenience for testing with engine templates. The Maven > artifacts are provided at the Maven staging repo here: > > https://repository.apache.org/content/repositories/orgapachepredictionio-1020 > > All JIRAs completed for this release are tagged with 'FixVersion = > 0.12.0-incubating'. You can view them here: https://issues.apache.or > g/jira/secure/ReleaseNote.jspa?version=12340591&projectId=12320420 > > The artifacts have been signed with Key: ytX8GpWv > > Please vote accordingly: > > [ ] +1, accept RC as the official 0.12.0 release > [ ] -1, do not accept RC as the official 0.12.0 release because... > >
[jira] [Comment Edited] (PIO-122) always get Error initializing storage client for source ELASTICSEARCH in 0.11 when pio train
[
https://issues.apache.org/jira/browse/PIO-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167406#comment-16167406
]
dongjie.shi edited comment on PIO-122 at 9/15/17 6:35 AM:
--
It works correctly when I change PIO to version 0.10.0.
But for PIO 0.11.0, it always fail.
was (Author: glorysdj):
it is ok when i change pio to version 0.10.0
> always get Error initializing storage client for source ELASTICSEARCH in 0.11
> when pio train
>
>
> Key: PIO-122
> URL: https://issues.apache.org/jira/browse/PIO-122
> Project: PredictionIO
> Issue Type: Bug
> Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: dongjie.shi
>
> Always get this error when I try to run PIO train to test a local PIO with
> HBase and Elasticsearch.
> [ERROR] [Storage$] Error initializing storage client for source ELASTICSEARCH
> Exception in thread "main"
> org.apache.predictionio.data.storage.StorageClientException: Data source
> ELASTICSEARCH was not properly initialized.
> at
> org.apache.predictionio.data.storage.Storage$$anonfun$10.apply(Storage.scala:285)
> at
> org.apache.predictionio.data.storage.Storage$$anonfun$10.apply(Storage.scala:285)
> at scala.Option.getOrElse(Option.scala:120)
> at
> org.apache.predictionio.data.storage.Storage$.getDataObject(Storage.scala:284)
> at
> org.apache.predictionio.data.storage.Storage$.getDataObjectFromRepo(Storage.scala:269)
> at
> org.apache.predictionio.data.storage.Storage$.getMetaDataEngineInstances(Storage.scala:371)
> at
> org.apache.predictionio.workflow.CreateWorkflow$.main(CreateWorkflow.scala:247)
> at
> org.apache.predictionio.workflow.CreateWorkflow.main(CreateWorkflow.scala)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.apache.spark.deploy.SparkSubmit$.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:731)
> at org.apache.spark.deploy.SparkSubmit$.doRunMain$1(SparkSubmit.scala:181)
> at org.apache.spark.deploy.SparkSubmit$.submit(SparkSubmit.scala:206)
> at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:121)
> at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)
> It seems that every component is ok in pio staus:
> [INFO] [Management$] Your system is all ready to go.
> And about the configurations in pio-env.conf, I have checked them for many
> times.
> PIO_FS_BASEDIR=${HOME}/.pio_store
> PIO_FS_ENGINESDIR=${PIO_FS_BASEDIR}/engines
> PIO_FS_TMPDIR=${PIO_FS_BASEDIR}/tmp
> SPARK_HOME=${SPARK_HOME}
> HBASE_CONF_DIR=${HBASE_HOME}/conf
> PIO_STORAGE_REPOSITORIES_METADATA_NAME=pio_meta
> PIO_STORAGE_REPOSITORIES_METADATA_SOURCE=ELASTICSEARCH
> PIO_STORAGE_REPOSITORIES_EVENTDATA_NAME=pio_event
> PIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE=HBASE
> PIO_STORAGE_REPOSITORIES_MODELDATA_NAME=pio_model
> PIO_STORAGE_REPOSITORIES_MODELDATA_SOURCE=LOCALFS
> PIO_STORAGE_SOURCES_ELASTICSEARCH_TYPE=elasticsearch
> PIO_STORAGE_SOURCES_ELASTICSEARCH_CLUSTERNAME=predictionio
> PIO_STORAGE_SOURCES_ELASTICSEARCH_HOSTS=localhost
> PIO_STORAGE_SOURCES_ELASTICSEARCH_PORTS=9300
> PIO_STORAGE_SOURCES_ELASTICSEARCH_HOME=${ELASTICSEARCH_HOME}
> PIO_STORAGE_SOURCES_LOCALFS_TYPE=localfs
> PIO_STORAGE_SOURCES_LOCALFS_PATH=${PIO_FS_BASEDIR}/models
> PIO_STORAGE_SOURCES_HBASE_TYPE=hbase
> PIO_STORAGE_SOURCES_HBASE_HOME=${HBASE_HOME}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (PIO-122) always get Error initializing storage client for source ELASTICSEARCH in 0.11 when pio train
[
https://issues.apache.org/jira/browse/PIO-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167406#comment-16167406
]
dongjie.shi commented on PIO-122:
-
it is ok when i change pio to version 0.10.0
> always get Error initializing storage client for source ELASTICSEARCH in 0.11
> when pio train
>
>
> Key: PIO-122
> URL: https://issues.apache.org/jira/browse/PIO-122
> Project: PredictionIO
> Issue Type: Bug
> Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: dongjie.shi
>
> Always get this error when I try to run PIO train to test a local PIO with
> HBase and Elasticsearch.
> [ERROR] [Storage$] Error initializing storage client for source ELASTICSEARCH
> Exception in thread "main"
> org.apache.predictionio.data.storage.StorageClientException: Data source
> ELASTICSEARCH was not properly initialized.
> at
> org.apache.predictionio.data.storage.Storage$$anonfun$10.apply(Storage.scala:285)
> at
> org.apache.predictionio.data.storage.Storage$$anonfun$10.apply(Storage.scala:285)
> at scala.Option.getOrElse(Option.scala:120)
> at
> org.apache.predictionio.data.storage.Storage$.getDataObject(Storage.scala:284)
> at
> org.apache.predictionio.data.storage.Storage$.getDataObjectFromRepo(Storage.scala:269)
> at
> org.apache.predictionio.data.storage.Storage$.getMetaDataEngineInstances(Storage.scala:371)
> at
> org.apache.predictionio.workflow.CreateWorkflow$.main(CreateWorkflow.scala:247)
> at
> org.apache.predictionio.workflow.CreateWorkflow.main(CreateWorkflow.scala)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.apache.spark.deploy.SparkSubmit$.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:731)
> at org.apache.spark.deploy.SparkSubmit$.doRunMain$1(SparkSubmit.scala:181)
> at org.apache.spark.deploy.SparkSubmit$.submit(SparkSubmit.scala:206)
> at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:121)
> at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)
> It seems that every component is ok in pio staus:
> [INFO] [Management$] Your system is all ready to go.
> And about the configurations in pio-env.conf, I have checked them for many
> times.
> PIO_FS_BASEDIR=${HOME}/.pio_store
> PIO_FS_ENGINESDIR=${PIO_FS_BASEDIR}/engines
> PIO_FS_TMPDIR=${PIO_FS_BASEDIR}/tmp
> SPARK_HOME=${SPARK_HOME}
> HBASE_CONF_DIR=${HBASE_HOME}/conf
> PIO_STORAGE_REPOSITORIES_METADATA_NAME=pio_meta
> PIO_STORAGE_REPOSITORIES_METADATA_SOURCE=ELASTICSEARCH
> PIO_STORAGE_REPOSITORIES_EVENTDATA_NAME=pio_event
> PIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE=HBASE
> PIO_STORAGE_REPOSITORIES_MODELDATA_NAME=pio_model
> PIO_STORAGE_REPOSITORIES_MODELDATA_SOURCE=LOCALFS
> PIO_STORAGE_SOURCES_ELASTICSEARCH_TYPE=elasticsearch
> PIO_STORAGE_SOURCES_ELASTICSEARCH_CLUSTERNAME=predictionio
> PIO_STORAGE_SOURCES_ELASTICSEARCH_HOSTS=localhost
> PIO_STORAGE_SOURCES_ELASTICSEARCH_PORTS=9300
> PIO_STORAGE_SOURCES_ELASTICSEARCH_HOME=${ELASTICSEARCH_HOME}
> PIO_STORAGE_SOURCES_LOCALFS_TYPE=localfs
> PIO_STORAGE_SOURCES_LOCALFS_PATH=${PIO_FS_BASEDIR}/models
> PIO_STORAGE_SOURCES_HBASE_TYPE=hbase
> PIO_STORAGE_SOURCES_HBASE_HOME=${HBASE_HOME}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (PIO-122) always get Error initializing storage client for source ELASTICSEARCH in 0.11 when pio train
dongjie.shi created PIO-122:
---
Summary: always get Error initializing storage client for source
ELASTICSEARCH in 0.11 when pio train
Key: PIO-122
URL: https://issues.apache.org/jira/browse/PIO-122
Project: PredictionIO
Issue Type: Bug
Components: Core
Affects Versions: 0.11.0-incubating
Reporter: dongjie.shi
Always get this error when I try to run PIO train to test a local PIO with
HBase and Elasticsearch.
[ERROR] [Storage$] Error initializing storage client for source ELASTICSEARCH
Exception in thread "main"
org.apache.predictionio.data.storage.StorageClientException: Data source
ELASTICSEARCH was not properly initialized.
at
org.apache.predictionio.data.storage.Storage$$anonfun$10.apply(Storage.scala:285)
at
org.apache.predictionio.data.storage.Storage$$anonfun$10.apply(Storage.scala:285)
at scala.Option.getOrElse(Option.scala:120)
at
org.apache.predictionio.data.storage.Storage$.getDataObject(Storage.scala:284)
at
org.apache.predictionio.data.storage.Storage$.getDataObjectFromRepo(Storage.scala:269)
at
org.apache.predictionio.data.storage.Storage$.getMetaDataEngineInstances(Storage.scala:371)
at
org.apache.predictionio.workflow.CreateWorkflow$.main(CreateWorkflow.scala:247)
at
org.apache.predictionio.workflow.CreateWorkflow.main(CreateWorkflow.scala)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.apache.spark.deploy.SparkSubmit$.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:731)
at org.apache.spark.deploy.SparkSubmit$.doRunMain$1(SparkSubmit.scala:181)
at org.apache.spark.deploy.SparkSubmit$.submit(SparkSubmit.scala:206)
at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:121)
at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)
It seems that every component is ok in pio staus:
[INFO] [Management$] Your system is all ready to go.
And about the configurations in pio-env.conf, I have checked them for many
times.
PIO_FS_BASEDIR=${HOME}/.pio_store
PIO_FS_ENGINESDIR=${PIO_FS_BASEDIR}/engines
PIO_FS_TMPDIR=${PIO_FS_BASEDIR}/tmp
SPARK_HOME=${SPARK_HOME}
HBASE_CONF_DIR=${HBASE_HOME}/conf
PIO_STORAGE_REPOSITORIES_METADATA_NAME=pio_meta
PIO_STORAGE_REPOSITORIES_METADATA_SOURCE=ELASTICSEARCH
PIO_STORAGE_REPOSITORIES_EVENTDATA_NAME=pio_event
PIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE=HBASE
PIO_STORAGE_REPOSITORIES_MODELDATA_NAME=pio_model
PIO_STORAGE_REPOSITORIES_MODELDATA_SOURCE=LOCALFS
PIO_STORAGE_SOURCES_ELASTICSEARCH_TYPE=elasticsearch
PIO_STORAGE_SOURCES_ELASTICSEARCH_CLUSTERNAME=predictionio
PIO_STORAGE_SOURCES_ELASTICSEARCH_HOSTS=localhost
PIO_STORAGE_SOURCES_ELASTICSEARCH_PORTS=9300
PIO_STORAGE_SOURCES_ELASTICSEARCH_HOME=${ELASTICSEARCH_HOME}
PIO_STORAGE_SOURCES_LOCALFS_TYPE=localfs
PIO_STORAGE_SOURCES_LOCALFS_PATH=${PIO_FS_BASEDIR}/models
PIO_STORAGE_SOURCES_HBASE_TYPE=hbase
PIO_STORAGE_SOURCES_HBASE_HOME=${HBASE_HOME}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
Re: [VOTE] Apache PredictionIO (incubating) 0.12.0 Release (RC2)
The last release was hung up by the IPMC regarding content licensing issues and libraries used by the doc site, which we promised to address in this release. Have these been resolved, don’t recall the specifics? It would be great to fly through the IPMC vote without issue. On Sep 14, 2017, at 2:06 PM, Chan Lee wrote: This is the vote for 0.12.0 of Apache PredictionIO (incubating). The vote will run for at least 72 hours and will close on Sep 17th, 2017. The release candidate artifacts can be downloaded here: https://dist.apache.org/repos/dist/dev/incubator/predi ctionio/0.12.0-incubating-rc2 Test results of RC1 can be found here: https://travis-ci.org/ap ache/incubator-predictionio/builds/275634960 Maven artifacts are built from the release candidate artifacts above, and are provided as convenience for testing with engine templates. The Maven artifacts are provided at the Maven staging repo here: https://repository.apache.org/content/repositories/orgapachepredictionio-1020 All JIRAs completed for this release are tagged with 'FixVersion = 0.12.0-incubating'. You can view them here: https://issues.apache.or g/jira/secure/ReleaseNote.jspa?version=12340591&projectId=12320420 The artifacts have been signed with Key: ytX8GpWv Please vote accordingly: [ ] +1, accept RC as the official 0.12.0 release [ ] -1, do not accept RC as the official 0.12.0 release because...
[VOTE] Apache PredictionIO (incubating) 0.12.0 Release (RC2)
This is the vote for 0.12.0 of Apache PredictionIO (incubating). The vote will run for at least 72 hours and will close on Sep 17th, 2017. The release candidate artifacts can be downloaded here: https://dist.apache.org/repos/dist/dev/incubator/predi ctionio/0.12.0-incubating-rc2 Test results of RC1 can be found here: https://travis-ci.org/ap ache/incubator-predictionio/builds/275634960 Maven artifacts are built from the release candidate artifacts above, and are provided as convenience for testing with engine templates. The Maven artifacts are provided at the Maven staging repo here: https://repository.apache.org/content/repositories/orgapachepredictionio-1020 All JIRAs completed for this release are tagged with 'FixVersion = 0.12.0-incubating'. You can view them here: https://issues.apache.or g/jira/secure/ReleaseNote.jspa?version=12340591&projectId=12320420 The artifacts have been signed with Key: ytX8GpWv Please vote accordingly: [ ] +1, accept RC as the official 0.12.0 release [ ] -1, do not accept RC as the official 0.12.0 release because...
