Re: Yarn deployment for static TcpDiscoverySpi issues:Urgent In Production

2016-08-24 Thread percent620
I have already fixed my issues, and add classpth://srping-bean.jar to load native jar NOT internet. Thanks -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Yarn-deployment-for-static-TcpDiscoverySpi-issues-Urgent-In-Production-tp7205p7289.html Sent from t

Re: Yarn deployment for static TcpDiscoverySpi issues:Urgent In Production

2016-08-24 Thread vkulichenko
No, this exception means that Spring can't parse your configuration file. If you're using the exact same file, most likely it's a classpath issue caused by the absence of spring-beans.jar dependency. Please check your project structure. -Val -- View this message in context: http://apache-ignit

Re: Yarn deployment for static TcpDiscoverySpi issues:Urgent In Production

2016-08-24 Thread percent620
Thanks Val, I have run successfully this with yarn on my local env. but when i run this on production env, I always get spring beans error message http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation=" htt

Re: Yarn deployment for static TcpDiscoverySpi issues:Urgent In Production

2016-08-23 Thread percent620
Thanks Val, I have fixed my issues for above, thanks for your great help on this issue. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Yarn-deployment-for-static-TcpDiscoverySpi-issues-Urgent-In-Production-tp7205p7253.html Sent from the Apache Ignite Users ma

Re: Yarn deployment for static TcpDiscoverySpi issues:Urgent In Production

2016-08-23 Thread vkulichenko
Configuration file is required on all nodes where Ignite will start. On executors the same path that you provide will be used. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Yarn-deployment-for-static-TcpDiscoverySpi-issues-Urgent-In-Production-tp7205p7249

Re: Yarn deployment for static TcpDiscoverySpi issues:Urgent In Production

2016-08-23 Thread percent620
This is my java code as below 1) val igniteContext = new IgniteContext[Integer, Integer](sc, "/u01//apache-ignite-fabric-1.6.0-bin/config/default-config.xml") println("define igniteContext end===") val sharedRDD = igniteContext.fromCache("sharedBaselineCacheRDD") //val sharedRDD = i

Re: Yarn deployment for static TcpDiscoverySpi issues:Urgent In Production

2016-08-23 Thread percent620
I have fixed the file issues "file:/usr/apache-ignite-fabric-1.6.0-bin/config/default-config.xml" on today. I verified again on our production env and found another issues as below 1) I have set IGNTE_HOME on spark driver machine and start to submit this jar to yarn cluster export IGNITE_HOME=/u0

Re: Yarn deployment for static TcpDiscoverySpi issues:Urgent In Production

2016-08-22 Thread vkulichenko
Hi, Can you please attach the configuration file instead of copy-pasting pieces of it? percent620 wrote* > the sparks-run will be running successfully, but the programs always > running NOT STOP, and didn't print message numbers * Can you please clarify what you meant by this? Is there still an

Re: Yarn deployment for static TcpDiscoverySpi issues:Urgent In Production

2016-08-22 Thread Nikolai Tikhonov
Hi, How I see in your logs that your "file:/usr/apache-ignite- fabric-1.6.0-bin/config/default-config.xml" is incorrect. invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 6; columnNumber: 71; cvc-elt.1: Cannot find the declaration of element 'beans'. at org.springfra

Yarn deployment for static TcpDiscoverySpi issues:Urgent In Production

2016-08-22 Thread percent620
Hello, Everything is okay for me to integrate ignite with yarn on *Multicast Based Discovery* in my local spark and yarn cluster , but in our production env, some of ports could't be opened .So, I need to specify a static ip address to discovery each other. but when running my configuration and