The problem is I am not able to kill my ignite yarn application even though
exception has been thrown while starting the ignite and the resources of the
ignite-yarn spark job keeps piling up. Please find attached image of spark
web-ui. From my "StartStandalone" spark application I use to submit the
Hello!
I still have trouble understanding where does your problem lie, in Ignite
terms (as opposed to Yarn or ZooKeeper terms).
Why did your negative scenario fail? What is the difference in procedure
used?
Regards,
--
Ilya Kasnacheev
чт, 20 февр. 2020 г. в 08:37, ChandanS :
> Hi Ilya,
>
> Y
Hi Ilya,
Yes, I start the ignite in client mode and my other applications access this
ignite cluster. I use to start the ignite cluster with 40-executors -and
2-cores. Usually, in success scenario my starting ignite and data loading
finish within 5/6 minutes. The logs are for negative scenario, wh
Hi Ilya,
Yes, I start the ignite in client mode and my other applications access this
ignite cluster. I use to start the ignite cluster with 40-executors -and
2-cores. Usually, in success scenario my starting ignite and data loading
finish within 5/6 minutes. The logs are for negative scenario, wh
Helo!
I can see that clientMode is true, this means that it has to find some
server nodes ot join.
GridDiscoveryManager fails to start because you interrupt it. Ditto the Zk
connection that you quote next.
Regards,
--
Ilya Kasnacheev
ср, 19 февр. 2020 г. в 15:03, ChandanS :
> Hi Ilya,
>
> Wh
Hi Ilya,
When it doesn't fine existing ignite cluster, I use to create a new one. If
you see the logs, you will get
>>> Starting Ignite Client with cluster name: titan-resourceUP
You can also see ignite initial start logs as well:
>>>__
>>> / _/ ___/ |/ / _/_
Hi Ilya,
>From my spark application, I am trying to do two things:
First, start Ignite yarn cluster using ignite-yarn.jar
Second, load data to ignite cluster.
In the first step, I have my own method to submit another spark job with
YarnConfiguration to start the ignite. In second step, I use to lo
Hello!
It's hard to say what's going on. Maybe you forget to stop the node, but
retry the same computation, and you have nodes piling up?
Can you provide logs?
Regards,
--
Ilya Kasnacheev
пт, 14 февр. 2020 г. в 22:29, ChandanS :
> Hi Ilya,
>
> My submitted Ignite-yarn application works fine
Hi Ilya,
My submitted Ignite-yarn application works fine for best case scenarios. The
issue is with worst case scenarios. E.g., below is my correct ignite_path
property and my application works fine with it:
IGNITE_PATH=/project/ecpdevbermuda/ignite/apache-ignite-2.7.0-bin.zip
But, if I give the
Hi Andrei,
I am using below configurations:
IGNITE_NODE_COUNT=40
IGNITE_RUN_CPU_PER_NODE=5
IGNITE_MEMORY_PER_NODE=15000
IGNITE_PATH=/project/ecpdevbermuda/ignite/apache-ignite-2.7.0-bin.zip
IGNITE_VERSION=2.7.0
IGNITE_WORKING_DIR=/project/ecpdevbermuda/ignite/
IGNITE_XML_CONFIG=/project/ecpdevber
Hi,
Could you please provide more details:
1)Your configurations and environment variables (IGNITE_PATH?)
2)The logs of your Ignite nodes where you see the mentioned exception.
IGNITE_PATH - a path to unzipped Ignite distribution instead of the URL.
Is it possible that you didn't unzip the bin
11 matches
Mail list logo