Ignite Cluster Error

Hi, We have deployed apache ignite fabric 2.3 We get the below error when trying to run on more than 1 node. GridTimeoutProcessor: Timeout has occurred: CancelableTask [id=970ee7b2061-c1565aa4-510c-4046-9ebb-46efd861b4df, endTime=1512558510454, period=5000, cancel=false,

Re: Data lose in query

Web Console currently does not allow to specify affinity keys on configuration screen, there is a ticket for this improvement: https://issues.apache.org/jira/browse/IGNITE-4709 For now the only option is to manually set the required annotations in generated classes. -Val -- Sent from:

Re: Affinity key for specific node

Mikael, You can also use a replicated cache then. This will give you both: all data available on service node as well as failover in case of failure (you will not lose any data as long as there is at least one node available). -Val On Tue, Dec 5, 2017 at 11:35 PM, Mikael

Re: Ignite Grid is in invalid state

I resolved this by Converting my client side code into a spring configuration. After that ignite resource was returned fine. It seems loading the xml directly does not work well when its a springboot project. This following project proved very useful.

Re: Index not getting created

Hi Naveen, Affinity mapping is a critical portion of Ignite data distribution and cannot be changed. For more information, please refer to this documentation: https://apacheignite.readme.io/docs/affinity-collocation D. On Wed, Dec 6, 2017 at 9:20 PM, Naveen wrote: >

Re: The client does not receive response after closure completion...

Hi Dave, Yes, TcpCommunicationSpi can establish connections both ways, so server nodes should be able to connect to client nodes. Thanks, Valentin -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: The client does not receive response after closure completion...

I got similar symptoms, but for a different root cause. I was getting the original stack trace using the "cache" command in Visor, but only when a client was connected. Using this command caused the clients to disconnect. It turned out that I had enabled inbound TCP ports to the servers, but

Re: Problem with creating table and insert data

Hi, Yes, if you need storing variable-length character data then SQL_LONGVARCHAR is a good choice. As I mentioned above, the full list of supported types is available here: https://apacheignite-sql.readme.io/docs/odbc-data-types Thanks! -- Sent from:

Re: SQL and backing cache question

This works, I could query the data. If we dont have POJOs and use binary objects to read and write, how can make rest API work. If I understand correctly, Java classes should be on classpath of the ignite node to work rest API. How can we make rest API work?? Also, instead of reading field by

Re: H2 console - GridH2QueryContext is not initialized

Hello, Please make sure that you started Ignite node and `IGNITE_H2_DEBUG_CONSOLE` system property was set to true. https://apacheignite-net.readme.io/docs/sql-queries#using-h2-debug-console Thanks! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: SQL and backing cache question

Hello Naveen, It seems, you need to use BinaryObject for that BinaryObjectBuilder builder = ignite.binary().builder("com.ril.edif.cityKey"); builder.setField("city_id", new Long(1)); BinaryObject keyValue = builder.build(); IgniteCache cache =

Re: SQL and backing cache question

Hi Ilya I was going thru an example using BinaryObject and trying to follow the same. I have created a table with the below SQL DDL CREATE TABLE city_details ( city_id LONG PRIMARY KEY, city_name VARCHAR, state_name VARCHAR ) WITH "backups=1, cache_name=city_details,