Best practice while creating tables - specifying the length of the data type

Hi I am using 2.3 Looks like ignite does not support CLOB, can I use varchar instead of CLOB if my requirement is to store 10 characters CREATE TABLE MAP_CUST ( PARTY_ID CLOB, MAPPING_ID VARCHAR(1000) NULL, UPDATEDBY

Connection problem between client and server

Hi Ignite community, we are encountering a connection problem, in our production environment, we have 3 Ignite servers with 500G+ of data each, and about 30 Ignite clients running. then we tried to start a simple Ignite client in different environment, Citrix environment, it cannot connect to the

Evictions started (cache may have reached its capacity). You may wish to increase 'maxSize' on eviction policy being used for cache

I am using fifo eviction policy, It is showing Eviction started but still, it is showing older entries also. I am using apache ignite V 2.3. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: H2 console - GridH2QueryContext is not initialized

Hi Val, I can not share the code as it is on client machine. My application is working perfectly. I have created some cache using ignite getorcreatecache and loading data from database (using spring) . I have created pojo to keep the data in different cache. There is no issue with data loading.

How to access ignite web console in AWS Ec2

Hi, I have deployed ignite 2.3.0 in AWS Ec2 with inbound rules allowing only 8080, 80, 443 ports. Since the web console uses random port i am unable to access the web console. Please suggest. Thanks -IB -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cache.query with ScanQuery Hangs forever

I can't reproduce this behavior and actually it sounds very weird that scan query can hang with empty cache. Do you have a complete test reproducing the problem that you can share with us? -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Cache.query with ScanQuery Hangs forever

Hey all, using Ignite 2.1 we are trying to use an IgniteCache.query to retrieve records that match our query. We attempt this query on a timed basis and it gets executed when their may be no records on the cache. Example below. ScanQuery query = new ScanQuery<>(new MatchingPredicate(name)

Re: H2 console - GridH2QueryContext is not initialized

Can you please show what exactly you're doing? How do you create the table? How do you enable the console and what are your next steps? Is the issue reproduced only in H2 console (i.e. what if you execute the query in Web Console for example)? -Val -- Sent from: http://apache-ignite-users.70518

Re: Test Ignite Client

Hi Humphrey, Can you show the code? -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cluster activation thru command line

Hi Naveen! There are a few problems with your command. Try this one: *$ ./control.sh --host 10.144.96.142 --port 11211 --activate* Port should be equal to the connector port, not discovery. The same thing can be achieved, using Visor CLI, by executing *top -activate* command. Denis вт, 2 янв.

Re: Total entries on cluster using metrics()

Thank you for your prompt answer. I found that the offHeapEntriesCnt is working for me (i only use the offHeap memory strategy). -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Page eviction mode is ignored

The similar issue was created by Denis, thanks. https://issues.apache.org/jira/browse/IGNITE-7347 On Sat, Dec 23, 2017 at 12:29 AM, Denis Magda wrote: > Hi Sergey, > > > But... page eviction doesn't work for "inMemory" memory region... Why? > > If Ignite persistence is enabled, then the page-bas

Re: Re: Some question regards the DataStorageConfiguration when used in multiple data regions.

This only happen when I shut down the nodes with this persist-able cache. After bring those nodes back, either throw this exception, or the node hang up forever waiting the initial partition map. [WARN ] 2018-01-02 13:19:08.318 [main] [ig] GridCachePartitionExchangeManager - Still waiting f

Cluster activation thru command line

Hi Am using 2.3, was trying to activate the cluster with the below command [tibusr@JMNGD1BAO50D00 bin]$ ./control.sh --10.144.96.142 --port 47500 --activate Something fail during activation, exception message: Latest topology update failed. Here is the cluster config entries

Re: Ignite throwing Out Of Memory

Hi Denis, I agree that 1GB is less and that is a constraint I have and it has been running just fine with same load. Did you get a chance to look at the csv files I have uploaded after analyzing heap dump ? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite throwing Out Of Memory

Hi! Looks like 1 GB of heap is not enough for your app to work normally. Give it more memory, it's a Java application after all :) It's true, that persistence helps you forget about eviction policy and your data is safe, even when memory comes to an end. But this mechanism affects only off-heap me

Re: Ignite Cluster Error

Yes Sir, that exception is from my code that has caused ignite2 (second ignite node) to go offline :) Investigating now ... -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Cluster Error

Usman, This exception is thrown from your code, so you will have to deal with it yourself :) I would also recommend you to reset all timeouts to default values. They seem to be too high. As Ignite suggests you in log, failure detection will work faster, if you don't assign such big values to time

Re: Ignite Cluster Error

Hi Denis, I saw the following error message in the logs on one of my ignite nodes (ml-ignite1.mobilink.osa): 02/01/2018 10:39:12 WARN [tcp-disco-msg-worker-#2%jazz-prod-triggers-anum%] TcpDiscoverySpi: Local node has detected failed nodes and started cluster-wide procedure. To speed up failure d

Ignite throwing Out Of Memory

Hi All, Ignite has thrown an OutOfMemory Error, the stack of which is mentioned below 2017-12-29 10:19:11,655 ERROR [tcp-disco-sock-reader-#40%63d769bd-bea6-450e-ab8b-0697da94ef1e%] {} org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi - Runtime error caught during grid runnable execution: Socke

Re: Total entries on cluster using metrics()

Hi Alex! This is a known issue. You can track its progress here: https://issues.apache.org/jira/browse/IGNITE-6564 You can use IgniteCache#size() method as a worka

Total entries on cluster using metrics()

Hello, I try to get the number of entries on 3 nodes inside a cluster. but when i am doing : Ignition.ignite().cache(CACHE_NAME).metrics().size() I only get the size of the local cache, however i was thinking that metrics() method returned the whole cluster statistics. The ignite-config is the

Date type field in select query is returning wrong value when Time zones of Ignite Client and Server are different

Hi In my sample Demo Ignite java program, Initially a Person entry is inserted from the Ignite Client into the Ignite cache. The Person Pojo has a "dob" field which is of java.util.Date type. Now when the Person Object is obtained using _val in query, the getTime() on dob field of Person Object g

Re: SQL and backing cache question

Hi Slava Approach suggested by you still requires us to build the key and value classes right, I was under impression that we dont need to build key and value classes at all. This is the snippet I got it from the docs. Does it mean we do not need to develop these classes OR just dont need to dep

Re: Re: Some question regards the DataStorageConfiguration when used in multiple data regions.

Hi Denis, Thanks for so quick response the NPE as: Caused by: java.lang.NullPointerException at org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.metadata(CacheObjectBinaryProcessorImpl.java:538) ~[ignite-core-2.3.0.jar!/:2.3.0] at org.apache.ignite.internal.pr

Test Ignite Client

Hello, I have the following question, I want to test my IgniteClient, which has it's own @Configuration file which has an igniteBean: Now I created a separate AppConfig for the testing (which Imports the AppConfig above from the client), and I want to start first a server node so the client can

Re: Ignite Cluster Error

Hi Denis, I did not see any other errors but let me dig more and will share. Best Regards, Usman -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Cluster Error

Hi Usman! "Timeout has occurred", printed by *GridTimeoutProcessor*, is an internal debug message, which tells you, that some scheduled task is getting executed. It's not an error. And you shouldn't be worried about "connection refused" exceptions on the node startup. They are thrown for all reje

Re: H2 console - GridH2QueryContext is not initialized

Hi Slava, Yes i have set it as true and after running the application, i am querying the cache from h2 console, but getting same error while running a select query. Is there anything else i need to set for this or how i will initialize GridH2QueryContext? On Thu 28 Dec, 2017, 19:11 slava.koptili

Re: Some question regards the DataStorageConfiguration when used in multiple data regions.

Hi Aaron! Looks like warnings are printed due to a bug. I created a ticket for it: https://issues.apache.org/jira/browse/IGNITE-7347 This bug doesn't affect anything, so you can just ignore the warnings. You've cut out the most interesting part of the stack trace - place, where NPE occurred. Plea