Ignite Cluster Error

[Usman Waheed]

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,
task=org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager$BackupCleaner@2c898c3e
]



Code is running fine on one node when ever new node joins it is gives above
error. We are using the below properties for making the cluster. Any
pointers or help will be much appreciated.























   



localIP:47500..47509



remoteIP:47500..47509

Re: Data lose in query

[vkulichenko]

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: http://apache-ignite-users.70518.x6.nabble.com/

Re: Affinity key for specific node

[Valentin Kulichenko]

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  wrote:

> Well, I would like to use a partitioned cache so that the data in the
> cache stays intact if that node goes down for a while, but if more nodes go
> down it might be lost anyway so maybe I need to use a local cache and
> persist it instead, was trying to avoid that.
>
>
>
> Den 2017-12-06 kl. 00:00, skrev vkulichenko:
>
>> If it's a single node, I would just create a special local cache for these
>> entries and deploy it on that node. Will this work?
>>
>> -Val
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>>
>

Re: Ignite Grid is in invalid state

[soodrah]

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.
https://mromeh.com/2017/11/17/spring-boot-with-apache-ignite-persistent-durable-memory-storage-plus-sql-queries-over-ignite-cache/
We can close this.



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

Re: Index not getting created

[Dmitriy Setrakyan]

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:

> This issue got fixed after clean restart of the cluster and creating the
> caches again.
> I could create the index.
> Do we have any option to set the affinity mapping for the cache which is
> already created and holding data.
>
> Thanks
> Naveen
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

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

[vkulichenko]

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...

[Dave Harvey]

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 this command requires an inbound connection into the clients,
and the TCP ports were blocked for the client.



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

Re: Problem with creating table and insert data

[slava.koptilin]

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: http://apache-ignite-users.70518.x6.nabble.com/

Re: SQL and backing cache question

[Naveen Kumar]

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 field from the binary object, can we get
the whole object

Which one works better,

Having POJOs for each table or with binary object to store and write from
the performance point of you.

Thanks
Naveen

On 28-Dec-2017 6:45 PM, "slava.koptilin"  wrote:

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 =
ignite.cache("city_details").withKeepBinary();
BinaryObject po = cache.get(builder.build());

Thanks!





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

Re: H2 console - GridH2QueryContext is not initialized

[slava.koptilin]

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

[slava.koptilin]

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 =
ignite.cache("city_details").withKeepBinary();
BinaryObject po = cache.get(builder.build());

Thanks!





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

Re: SQL and backing cache question

[Naveen]

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, key_type=com.ril.edif.cityKey,
value_type=com.ril.edif.city" ;

Inserted 2 records thru SQL line and was trying query data thru Java API,
here is the code

++++
|CITY_ID |   CITY_NAME|  
STATE_NAME   |
++++
| 1  | Mumbai | MH  
  
|
| 2  | Hyd| TS  
  
|
++++


IgniteCache binaryCache =
ignite.cache("city_details").withKeepBinary();
BinaryObject po = binaryCache.get(new Long(1));
String name = po.field("city_name");

Does not seems to be working, getting java.lang.NullPointerException at
String name = po.field("city_name")

what is wrong with this code.

As the doc mentioned the reason I am going for binary object is to not to
maintain or write POJOs for all the objects and maintain it under classpath. 

Does the rest API work for GET if we dont keep classes under classpath

Thanks
Naveen



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