Re: Values lost when cache is in partitioned mode in cluster

Hi, An update : when I set writeSynchronizationMode as FULL_SYNC, this is working now. [Seems like a work around, hoping to get a correct solution] Earlier cache store was getting executed even though I had never invoked its load method explicitly. Also one time, I got this message in the log:

Failed to fetch SQL query result

Hello. I did a scan query on a table which has 8w records and tried to go through all records in the result set but got following exception: [13:53:31,523][SEVERE][client-connector-#77][JdbcRequestHandler] Failed to fetch SQL query result [reqId=0, req=JdbcQueryFetchRequest [queryId=38106237,

Can we have different Segmentation Policy in same cluster grid?

Hi, Can we have different Segmentation Policy in same cluster grid? () Let 's say I have grid with 3 node server cluster. Can I configure segmentationPolicy value to 'STOP' in one server, 'RESTART_JVM' on another server and 'NOOP' on the other sever? What is is behavior if it is allowed and what

Re: Values lost when cache is in partitioned mode in cluster

I do flush the data in the streamer. Reproducer attached along. reproducer.zip -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite startu is very slow

Hi, I have deActivated the cluster and closed, but still same issue persists. Thanks & Regards, Venkat -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: (IF NOT EXISTS) in CREATE TABLE statement does not work

The problem has been re-described under another topic: some cases (IF NOT EXISTS) in the CREATE TABLE statement does not work -- Sent from:

some cases (IF NOT EXISTS) in the CREATE TABLE statement does not work

Question=== When testing Ignite 2.6.0 (2018-07-16), it was found that in some cases (IF NOT EXISTS) in the CREATE TABLE statement does not work. [Wrong case] After the first run is successful, the code will prompt "Table already exists: CITY" in the next iteration:

Re: Optimum storage startegy (Advice?)

Hi, You mentioned that all fields are indexed, does this mean that you have only single-field indexes? Do you consider creating group indexes for your queries? Can you share query plans with us? If you will have proper group indexes for all queries, maybe it worth to try to avoid joins at all

Re: (IF NOT EXISTS) in CREATE TABLE statement does not work

Start a single instance Ignite server node locally, then connect this Ignite cluster and run the previous test code, run successfully; then connect the original distributed three-node Ignite cluster again, the test code also runs successfully, what is the reason? Will the Ignite client buffer some

Re: (IF NOT EXISTS) in CREATE TABLE statement does not work

Start a single instance Ignite server node locally, then connect this Ignite cluster and run the previous test code, run successfully; then connect the original distributed three-node Ignite cluster again, the test code also runs successfully, what is the reason? Will the Ignite client buffer some

Re: Values lost when cache is in partitioned mode in cluster

Hi, Do you flush data in data streamer? Can you share a simple reproducer? Best Regards, Evgenii пн, 26 нояб. 2018 г. в 11:18, the_palakkaran : > Hi, > > I have two nodes. A cache which has an Object as Key and a list of Objects > as values is configured in partitioned mode. On a single node

Re: Ignite Query Slow

Can you attach it instead of just posting to the message? пн, 26 нояб. 2018 г. в 10:12, Skollur : > Also attached GC-> > > 2018-11-26T13:35:23.058-0500: 1172.703: [GC pause (G1 Evacuation Pause) > (young), 0.0070730 secs] >[Parallel Time: 6.3 ms, GC Workers: 2] > [GC Worker Start (ms):

Support for SELECT ... INTO ?

When will Ignite support this? Will this be included in 2.7? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Values lost when cache is in partitioned mode in cluster

Hi, I have two nodes. A cache which has an Object as Key and a list of Objects as values is configured in partitioned mode. On a single node every value in the list is loaded correctly. While started in a cluster of two nodes, even though the data is queried and put into the cache correctly,

Re: When will Apache Ignite support Java 11?

Hello, The current plan is that Oracle will stop updates for Java 8 commercial users after January 2019, and Java 11 is the next LTS release, so is there a plan to have Ignite working with Java 11 by then? Thank you. On Thu, Nov 22, 2018 at 10:49 PM Petr Ivanov wrote: > Hi! > > > Full Java 9+

Re: Ignite Query Slow

Also attached GC-> 2018-11-26T13:35:23.058-0500: 1172.703: [GC pause (G1 Evacuation Pause) (young), 0.0070730 secs] [Parallel Time: 6.3 ms, GC Workers: 2] [GC Worker Start (ms): Min: 1172702.9, Avg: 1172703.3, Max: 1172703.7, Diff: 0.8] [Ext Root Scanning (ms): Min: 1.1, Avg: 1.4,

Re: Ignite Query Slow

Hello Are u suggesting to have more nodes with REPLICATE OR PARTITIONED settings? Thanks -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Suppressing reflective serialisation in Ignite

P.S. I realize that this is a major limitation.Ticket filed: https://issues.apache.org/jira/browse/IGNITE-10411 On Mon, Nov 26, 2018 at 7:54 PM Pavel Tupitsyn wrote: > Yes, there is a mismatch there, Ignite passes uninitialized object to the > serializer in order to handle reference loops. > >

Re: Suppressing reflective serialisation in Ignite

Yes, there is a mismatch there, Ignite passes uninitialized object to the serializer in order to handle reference loops. I think the easiest workaround is to use some library like DeepClone [1]: public void ReadBinary(object obj, IBinaryReader reader) { if (obj is IBinarizable bin) {

Re: How to get the column names(or fieldsNames) of existing ignite sql table

1. Check out this thread to get a list of fields: http://apache-ignite-users.70518.x6.nabble.com/Get-Field-Names-In-Select-Query-td25258.html 2. "Create table..." command creates a cache under the hood. https://apacheignite-sql.readme.io/docs/create-table -- Sent from:

Speed Expectations for Ignite Queue

Hello, I'm currently trying Apache Ignite and love the concept. I have created a simple example of what I'm trying to achieve (producer): https://github.com/karussell/igniteexample/blob/master/src/main/java/test/MyIgnite.java My assumption is that the default settings are tuned to get a setup

Re: NearCache entries on heap ?

Near cache is always on-heap. Its not an independent cache, its just a local copy of a cache stored on another node. In some cases it improves performance. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Does it affect the put, get, query operation when add or remove a node?

There is no simple answer to this question. It depends on configuration of your cluster and load profile. Cluster won't stop in any case, because it is designed to support scaling, but the performance could be affected. If you use partitioned caches (default cache configuration) then adding or

Re: Ignite cluster going down frequently

Hello! Maybe you have some data in your caches which causes runaway heap usage in your own code. Previously you did not have such data or code which would react in such fashion. It's hard to say, can you provide more logs from the node before it segments? Regards, -- Ilya Kasnacheev пн, 26

Re: Why GridDiscoveryManager onSegmentation use StopNodeFailureHandler?

Hello! Node is stopped because server node will not be able to rejoin a cluster once segmented. JVM is not terminated by default since Ignite may be not the only thing running in same JVM and you don't want to kill someone else's code. Regards, -- Ilya Kasnacheev пн, 26 нояб. 2018 г. в

Re: Ignite cluster going down frequently

Thank you very much Ilya Kasnacheev for your response. We are loading data initially, after that only small delta change will be updated. Grid down issue is happening after it is running successfully 2 to 3 days. Once the issue started, it is repeating frequently and not getting any clue. Thanks

Why GridDiscoveryManager onSegmentation use StopNodeFailureHandler?

Why GridDiscoveryManager onSegmentation use StopNodeFailureHandler? But not the StopNodeOrHaltFailureHandler ! In my case,when net problem happen, I wan't the jvm close? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Ignite 2.7

Thanks Andrey. От: Maxim.Pudov Отправлено: 26 ноября 2018 г. в 12:56 Кому: user@ignite.apache.org Тема: Re: Ignite 2.7 It is up to community to decide. You can track the progress here: http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-Last-Mile-td36359i40.html I think it

Re: Is near cache persistent ?

Near cache is a local cache for faster access to data on client nodes. Client node is a node, which connects to a cluster, does some work and could be disconnected after that, it doesn't store data permanently, that's server node's responsibility. -- Sent from:

Re: JDBC Streaming

The streaming examples should work fine for you. “Grid caches” and “SQL tables” are not two, different things. They are just two ways of accessing the same underlying structures. You can happily insert data using a Data Streamer and access it later using SQL. Regards, Stephen > On 26 Nov

Re: Ignite Query Slow

Hello, It is hard to tell what is the bottleneck in your case, could be anything. I suggest tracking CPU and memory usage, enable GC logs. Adding more nodes will definitely help in this case. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite 2.7

It is up to community to decide. You can track the progress here: http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-Last-Mile-td36359i40.html I think it will happen in a matter of weeks. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Continuous queries and duplicates

Thanks. This is a little disappointing. ScanQuery would probably work, but it’s not as efficient (can’t use indexes etc.). Are there any plans to enable isolation on SqlQuery? -KS From: Ilya Kasnacheev [mailto:ilya.kasnach...@gmail.com] Sent: 26 listopada 2018 08:01 To: user@ignite.apache.org

Re: JDBC Streaming

Hi Ilya, I realize that Streaming is not supported via the JDBC Client node interface (*thanks for that info). But is it possible to stream-import data via (code) SQL directly and load it into persistent SQL table? (The Ignite code examples for Streaming only show loading data into grid

Re: Question about add new nodes to ignite cluster.

I understand, thank you very much. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Question about add new nodes to ignite cluster.

Hi! You have it at the first paragraph in the documentation "If Ignite persistence is enabled, Ignite enforces the /baseline topology/ concept which represents a set of server nodes in the cluster that will persist data on disk." The baseline topology is needed for persistence, if your

Question about add new nodes to ignite cluster.

I added 3 nodes to existing cluster, but not add them to topology, like below: Cluster state: active Current topology version: 93 Baseline nodes: ConsistentID=0ded99c1-b19c-4ced-ba3a-06abe233c6c8, STATE=ONLINE ConsistentID=2c252722-a3c4-4f55-8d26-d216329fddbb, STATE=ONLINE

Question about add new nodes to ignite cluster.

I added 3 nodes to existing cluster, but not add them to topology, like below: Cluster state: active Current topology version: 93 Baseline nodes: ConsistentID=0ded99c1-b19c-4ced-ba3a-06abe233c6c8, STATE=ONLINE ConsistentID=2c252722-a3c4-4f55-8d26-d216329fddbb, STATE=ONLINE

Question about add new nodes to ignite cluster.

I added 3 nodes to existing cluster, but not add them to topology, like below: Cluster state: active Current topology version: 93 Baseline nodes: ConsistentID=0ded99c1-b19c-4ced-ba3a-06abe233c6c8, STATE=ONLINE ConsistentID=2c252722-a3c4-4f55-8d26-d216329fddbb, STATE=ONLINE

Re: (IF NOT EXISTS) in CREATE TABLE statement does not work

After many tests, I found that if I first set up an Ignite client node and then use ("jdbc:ignite:thin://127.0.0.1/") as the JDBC connection URL, various problems will occur, but if similar ( "jdbc:ignite:thin://192.168.0.138/") The pure JDBC method that connects directly to the target Ignite

Re: Ignite cluster going down frequently

Hello! Node will get segmented if other nodes fail to wait for Discovery response from that node. This usually means either network problems or long GC pauses causes by insufficient heap on one of nodes. Make sure your data load process does not cause heap usage spikes. Regards. -- Ilya