You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Dave Harvey <dh...@jobcase.com> on 2017/09/05 21:16:50 UTC
Re: Issue with starting Ignite node on AWS
I'm also a newbie, but I'm running 2.1.0 and I seem to be hitting the same
problem, which sounds like it was fixed a long time ago. Is there
something else going on?
I've uploaded the 2 lines I pass when creating the EC2 instance from the AMI
as well as the config file I'm using, as well as the full output from docker
logs. errs.log
<http://apache-ignite-users.70518.x6.nabble.com/file/t1332/errs.log>
xxx.txt <http://apache-ignite-users.70518.x6.nabble.com/file/t1332/xxx.txt>
config.xml
<http://apache-ignite-users.70518.x6.nabble.com/file/t1332/config.xml>
Caused by: org.springframework.beans.factory.CannotLoadBeanClassException:
Cannot find class
[org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder] for
bean with name
'org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder#71623278'
defined in URL [https://s3.amazonaws.com/jc-ignite-trial/example-cache.xml];
nested exception is java.lang.ClassNotFoundException:
org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder
at
org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1385)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:299)
... 28 more
Caused by: java.lang.ClassNotFoundException:
org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Issue with starting Ignite node on AWS
Posted by vkulichenko <va...@gmail.com>.
Most likely ignite-aws module is not enabled. For standalone node started
using ignite.sh, move 'ignite-aws' folder from 'libs/optional' to 'libs'
prior to node start. For embedded, add 'ignite-aws' Maven dependency along
with 'ignite-core', 'ignite-spring' and any other that you might use.
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Issue with starting Ignite node on AWS
Posted by Dave Harvey <dh...@jobcase.com>.
Thanks.
In the AWS AMI deployment, under "Advanced Details". I hadn't set anything
under OPTION_LIBS. The following has gotten me much further.
CONFIG_URI=https://s3.amazonaws.com/jc-ignite-trial/example-cache.xml
OPTION_LIBS=ignite-aws,ignite-aop,ignite-indexingignite-log4j,ignite-spring
IGNITE_VERSION=2.1.0
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Issue with starting Ignite node on AWS
Posted by vkulichenko <va...@gmail.com>.
Most likely ignite-aws module is not enabled. For standalone node started
using ignite.sh, move 'ignite-aws' folder from 'libs/optional' to 'libs'
prior to node start. For embedded, add 'ignite-aws' Maven dependency along
with 'ignite-core', 'ignite-spring' and any other that you might use.
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/