Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

Which issue? As I said, embedded mode was deprecated a long time ago, as this docs says: https://apacheignite-fs.readme.io/docs/ignitecontext-igniterdd#section-ignitecontext and looks like it was discontinued. Consider starting a separate Ignite cluster and using standalone mode to avoid data

Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

I think we are deviating from the point. The core issue still remains. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Call to deployClusterSingleton blocked.

Most likely it’s either https://issues.apache.org/jira/browse/IGNITE-8023 or https://issues.apache.org/jira/browse/IGNITE-7753 Until these issues are fixed, avoid starting/restarting nodes while cluster activation is in progress. Thanks, Stan From: Calvin KL Wong, CLSA Sent: 19 июля 2018 г.

Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

I am now explicitly setting the clientmode as False in the java code. "You can use ExampleNodeStartup to start Ignite node from idea." --- this defeats the purpose of executing spark code across Ignite nodes. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

how? You will start a client node, connect to your cluster and will interact with it via this client. 2018-07-19 13:08 GMT+03:00 chetanj : > I am now explicitly setting the clientmode as False in the java code. > > "You can use ExampleNodeStartup to start Ignite node from idea." > > --- this

spark - Failed to process custom exchange task

*Everything was working fine this morning then i had to reboot to install an update on other software. Starting it all up again the ignite server starts, cache is loaded and can be queried from DBBeaver. When i access from spark however it all falls apart. * *import

Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

As you using integration with spark, it enables clientMode flag internally - it doesn't make any sense to create new server each time for integrating with spark - you should have already started server nodes. You can use ExampleNodeStartup to start Ignite node from idea. 2018-07-19 12:34

RE: Insert Query in Gridgrain WebConsole

If you’re using GridGain, it would be better to contact their customer support. Also, check out this docs page about queries in WebConsole: https://apacheignite-tools.readme.io/docs/queries-execution Stan From: UmeshPandey Sent: 19 июля 2018 г. 12:54 To: user@ignite.apache.org Subject: Insert

RE: How to increase memory of Gridgrain database.

If you’re using GridGain, it would be better to contact their customer support. Stan From: UmeshPandey Sent: 19 июля 2018 г. 12:59 To: user@ignite.apache.org Subject: How to increase memory of Gridgrain database. Can anyone tells, how to increase a memory of Gridgrain database? I tried below

Re: Thin client doesn't support Expiry Policies.

I have not found any tickets for this feature, so there must be no current plans to implement it from any community member. However, I've created a ticket for this feature [1] so anyone may pick it up now. Also, you can easily track this ticket now. [1] -

RE: Insert Query in Gridgrain WebConsole

In this blog insert query is not there and I am looking for insert in Ignite Web Console. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Task not serializable: java.io.NotSerializableException: org.apache.ignite.configuration.IgniteConfiguration

brilliant thanks it is working here is the code for anyone else that will find this useful. val igniteContext = new IgniteContext(sc, () =>{ val tcpDiscoverySpi: TcpDiscoverySpi = new TcpDiscoverySpi val ipFinder: TcpDiscoveryVmIpFinder = new

Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

If you're facing the same error, most possible that other node(most possible client) already was started on the port 47500. At the same time, you server node starts on the next port(47501 for example). But your configuration contains only one address in ipFinder - 47500. You need to make sure that

Re: LRU policy, on heap - off heap size ?

Hello, Yep, it is expected behavior. You are using on-heap eviction policy and so, this policy removes the cache entries from Java heap only. The entries stored in the off-heap region of the memory are not affected. You can find a comprehensive description here:

Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

Yes i have recompiled, get the same error still. as told earlier i have removed the explicit declaration for setclientmode. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Insert Query in Gridgrain WebConsole

You can write INSERT the same way as you write SELECT. Syntax for INSERT is described here: https://apacheignite-sql.readme.io/docs/insert Thanks, Stan From: UmeshPandey Sent: 19 июля 2018 г. 13:43 To: user@ignite.apache.org Subject: RE: Insert Query in Gridgrain WebConsole In this blog insert

Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

ignite.bat starts server node. As you see in your java code which you starts from idea:IgniteConfiguration().setClientMode(true). Client mode will be started only after it will be connected to server node. Evgenii 2018-07-19 11:35 GMT+03:00 chetanj : > @ezhuravlev > > I am not starting the

Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

log.txt -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

Interesting.. I am not getting any logs in the Work directory. for the server node. Intellij code is the only piece is run, so not sure why its starting the client. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

LRU policy, on heap - off heap size ?

Here is the my lru configuration ... ccfg.setOnheapCacheEnabled(true); ccfg.setEvictionPolicyFactory(new LruEvictionPolicyFactory(2)); ... When I want to load 3 datas to cache, ignite console shows me 2 on heap and

Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

I am not using both Code and Config.xml at the same time. I just shared to demonstrate that either of the approaches do not work. Step1 : First i try with the xml config. it didnt work Step2 : then i tried via the code, it didnt work. currently both my server and client nodes are not running.

Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

Well, then you can try to recompile it or rerun Idea. I see that clientMode was explicitly set in IgniteConfiguration. 2018-07-19 12:21 GMT+03:00 chetanj : > > Interesting.. I am not getting any logs in the Work directory. for the > server node. > Intellij code is the only piece is run, so not

[TcpDiscoverySpi] Failed to connect to any address from IP finder

Hello, I am aware that this issue has been discussed in this forum in past. But none of the resolution steps given helped resolve this. I am facing the below issues ; 1. Apache Ignite version 2.6.0, [ issue occurs in versions 2.5.0, 2.4.0 ] IntelliJ Spark-scala Machine :

Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

Hi, >From the part of the log you've provided, I see that you starting client node - it needs server nodes to connect to. At the same time, ignite.bat script starts server node. Regards, Evgenii 2018-07-19 10:04 GMT+03:00 Chetan Jayaram : > Hello, > > > > I am aware that this issue has been

Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

@ezhuravlev I am not starting the server node via ignite.bat. The main issue i am facing is executing the Ignite in Intellij. 1. Do i have to start the server node separately [ignite.bat] . I am currently executing Ignite from Intellij - Run Edit configuration with VM parameters ->

Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

I don't understand which configuration you use - you sharing both java code and xml config, which configures the same thing. Which configuration you use? 2018-07-19 11:58 GMT+03:00 chetanj : > there are no other clients running, not even the server node. I have > specified the range in the

Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

You still starting a client node. Do you have logs for server node? 2018-07-19 12:11 GMT+03:00 chetanj : > log.txt > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >

How to increase memory of Gridgrain database.

Can anyone tells, how to increase a memory of Gridgrain database? I tried below snippet in MSSQLCluster-server.xml, but it is not working. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

Yes, mistake at my end. i made it to "False" but it still gives me the same error. On Thu, Jul 19, 2018 at 4:41 PM, Evgenii Zhuravlev wrote: > ignite.bat starts server node. As you see in your java code which you > starts from idea:IgniteConfiguration().setClientMode(true). Client mode > will

Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

changing it to "false" setClientMode(false) , still gives the same IP_FINDER error -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

then can you share the full reproducer? 2018-07-19 11:44 GMT+03:00 chetanj : > changing it to "false" setClientMode(false) , still gives the same > IP_FINDER > error > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >

Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

interesting.. I am not getting any logs in the Work directory. and this is the only code which i execute, so not sure why its starting the client. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

there are no other clients running, not even the server node. I have specified the range in the default-config.xml 127.0.0.1:47500..47509 Btw, thanks for the speedy response

Re: [TcpDiscoverySpi] Failed to connect to any address from IP finder

well, then please share the full log from the node. 2018-07-19 12:05 GMT+03:00 chetanj : > I am not using both Code and Config.xml at the same time. I just shared to > demonstrate that either of the approaches do not work. > > Step1 : First i try with the xml config. it didnt work > Step2 : then

Insert Query in Gridgrain WebConsole

how to write an insert query in Gridgrain WebConsole. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Call to deployClusterSingleton blocked.

Hi, Is this issue reproducible? Can you share logs from all nodes and code of the service? Evgenii -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

[CVE-2018-1273] Apache Ignite impacted by security vulnerability in Spring Data Commons

Severity: Important Vendor: The Apache Software Foundation Versions Affected: * Apache Ignite 1.0.0-RC3 to 2.5 Impact: An unauthenticated remote malicious user (or attacker) can issue requests against Spring Data REST or Spring Data Description: Apache Ignite utilizes Spring Data Common

Re: spark - Failed to process custom exchange task

is this bug still active (generated from web console) https://issues.apache.org/jira/browse/IGNITE-4829 Spring context is not injected into POJO store when JDBC driver is utilized -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

How to do partial update from multiple client

Hi we have questions about partial column updates from different clients. 1) We have a c++ client updates some meta-data columns, it uses SqlFieldsQuery to do partial update. The update is not frequently. it happens in several hours. 2) We have a java client that frequently updates market data

Re: LRU policy, on heap - off heap size ?

thanks slava.koptilin wrote > Hello, > > Yep, it is expected behavior. You are using on-heap eviction policy and > so, > this policy removes the cache entries from Java heap only. The entries > stored in the off-heap region of the memory are not affected. > You can find a comprehensive

Re: Thin client doesn't support Expiry Policies.

Thanks for opening the ticket. Edison -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

[CVE-2018-8018] Possible Execution of Arbitrary Code via Apache Ignite GridClientJdkMarshaller

Severity: Important Vendor: The Apache Software Foundation Versions Affected: Apache Ignite 2.5 and earlier Impact: An attacker can execute arbitrary code on Ignite nodes via GridClientJdkMarshaller deserialization endpoint in the case when Ignite classpath contains arbitrary vulnerable

latency for replication

Hi, How can I measure the latency for updates to be replicated from the primary node to a backup node? I use the PRIMARY_SYNC mode. I want to know the time for a backup node to catch up. Is there any API for the latency measurement? Do you have any suggestion? Thanks, Cong