Re: Set Expiry Policies When Creating Cache Using Java Thin Client

Yes, I know I can set the template in SQL (via JDBC) or REST API. But how can I set the template on the Java thin client? Thanks! On Mon, Jul 8, 2019 at 5:55 AM Ilya Kasnacheev wrote: > Hello! > > Yes, you can declare cache configuration templates, refer to them when > creating tables from

Re: add data to table, sql add ,cache add has different result ,I use ignite 2.6

City_id is defined in the key, key never show in the value? How can I use sql insert ,insert the key like cache , and how can I use cache insert, insert the value like sql ,I want insert use cache or use sql keep the same . Can you give me a solution? > 在 2019年7月9日，上午11:46，Andrey Dolmatov

Re: INSERT and MERGE statements

Hi, I have to follow-up. MERGE INTO works fine when I define matching fields between SOURCE and DESTINATION caches. However, Merge command nullifies fields in the DESTINATION table when they are not part of the SOURCE. for Instance an object in cache DST has 3 fields : field1, field2, field3

Re: An existing connection was forcibly closed by the remote host

Hello! I think that it will make sense to have a single client per handling thread. Close only when idle. Regards. -- Ilya Kasnacheev пн, 8 июл. 2019 г. в 20:07, siva : > ok. > One more question on this, > Our dot net services(lets say micro service 15) is processing 40K to 60K > messages.

Re: An existing connection was forcibly closed by the remote host

ok. One more question on this, Our dot net services(lets say micro service 15) is processing 40K to 60K messages. In each service, I am opening and closing connection for each message processing and inserting/reading into ignite. Generally, Is it good practice to do..? -- Sent from:

Re: An existing connection was forcibly closed by the remote host

Hello! If it's thin client than you should be able to simply re-open your client when it turns bad. Then maybe it's client that closing this connection, maybe it's network stack (inactivity, etc). It is recommended to close Thin Client when not using it, rather than let it hang around.

Re: Web Agent connected to Cluster but console doesn't show

What version do you use? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: onheapCacheEnabled enormous heap consumption

Hello! Data is always written to persistence immediately (via WAL). You can control eviction of offheap with evictionThreshold and pageEvictionMode settings of DataRegionConfiguration. Regards, -- Ilya Kasnacheev пн, 8 июл. 2019 г. в 17:50, Andrey Dolmatov : > When data overfit dataRegion

Re: On ServerNode Thread TIMED_WAITING Lock

Hello! It seems that one thread is busy reading pages from disk, so other thread can't acquire write lock. May happen if you have block device with bad characteristics, such as HDD, and issue queries which overwhelm it. Regards, -- Ilya Kasnacheev чт, 4 июл. 2019 г. в 16:51, siva : >

Re: onheapCacheEnabled enormous heap consumption

When data overfit dataRegion max size, so no more available offheap space, then data goes to persistence. So, what option controls how data pages should be evicted from offheap to persistence. On Mon, Jul 8, 2019, 5:33 PM Ilya Kasnacheev wrote: > Hello! > > Data is always stored in offheap.

Re: onheapCacheEnabled enormous heap consumption

Hello! Data is always stored in offheap. Eviction strictly controls onheap cache. Once data is evicted from onheap it is available in offheap. Regards, -- Ilya Kasnacheev пн, 8 июл. 2019 г. в 17:31, Andrey Dolmatov : > We plan to use persistence in production. I didn't understand, >

Re: onheapCacheEnabled enormous heap consumption

We plan to use persistence in production. I didn't understand, CacheConfiguration.EvictionPolicy specify heap->offheap eviction, offheap->persistence eviction or both. It's not clear for me. On Mon, Jul 8, 2019, 5:19 PM Ilya Kasnacheev wrote: > Hello! > > Oops, I was wrong. This is indeed the

Re: onheapCacheEnabled enormous heap consumption

No, we didn't specify EvictionPolicy. I didn't find does CacheConfiguration have default EvictionPolicy? On Mon, Jul 8, 2019, 5:19 PM Ilya Kasnacheev wrote: > Hello! > > Oops, I was wrong. This is indeed the wrong setting. > > Have you tried specifying evictionPolicy? I think it is the one that

Re: onheapCacheEnabled enormous heap consumption

Hello! Oops, I was wrong. This is indeed the wrong setting. Have you tried specifying evictionPolicy? I think it is the one that controls eviction from onheap cache. You can put a LruEvictionPolicy of 100 000 here, for example. Regards, -- Ilya Kasnacheev пн, 8 июл. 2019 г. в 17:09, Andrey

Re: onheapCacheEnabled enormous heap consumption

No, because we didnt specify QueryEntity. Does onheapCacheEnabled uses for SQL only? What default value for sqlOnheapCacheMaxSize? пн, 8 июл. 2019 г. в 17:05, Ilya Kasnacheev : > Hello! > > Have you tried also specifying sqlOnheapCacheMaxSize? You can specify 100 > 000 if you like. > > Regards,

Re: onheapCacheEnabled enormous heap consumption

Hello! Have you tried also specifying sqlOnheapCacheMaxSize? You can specify 100 000 if you like. Regards, -- Ilya Kasnacheev пн, 8 июл. 2019 г. в 17:01, Andrey Dolmatov : > We use simple replicated KV cache. > We try to upload 32 000 000 small records to it (about 6Gb in > data region,

onheapCacheEnabled enormous heap consumption

We use simple replicated KV cache. We try to upload 32 000 000 small records to it (about 6Gb in data region, persistance disabled). We load data using DataStreamer. If we set onheapCacheEnabled=false, server node consumes heap about 500 Mb. If we set onheapCacheEnabled=true, server node

Re: Set Expiry Policies When Creating Cache Using Java Thin Client

Hello! Yes, you can declare cache configuration templates, refer to them when creating tables from thin client/JDBC, as per documentation: https://apacheignite.readme.io/docs/cache-template Regards, -- Ilya Kasnacheev пт, 5 июл. 2019 г. в 21:22, Shane Duan : > Thanks, Denis. Alternatively,

Re: An existing connection was forcibly closed by the remote host

Hello! I have seen such messages under heavy load on a large cluster. My recommendation is to increase socketWriteTimeout to 5s on TcpCommunicationSpi. The default of 2s is too small, even smaller than TCP retransmit. Regards, -- Ilya Kasnacheev пн, 8 июл. 2019 г. в 15:38, siva : >

Re: Node not joined to the cluster - joining node doesn't have encryption data

Hello! It's hard to say why node failed. Software termination? Network problems? Unhandled error? But it is likely unrelated to 'joining node doesn't have encryption data' messages. Can you provide complete logs? Regards, -- Ilya Kasnacheev пн, 8 июл. 2019 г. в 09:15, shahidv : > any idea

Re: An existing connection was forcibly closed by the remote host

Hello! Unfortunately your letter does not seem to contain any error messages. Can you paste them in as text? Regards, -- Ilya Kasnacheev пн, 8 июл. 2019 г. в 15:33, siva : > Hi, > I have .NetCore(v2.2.103) client and Server Ignite(v2.7.5) Application.And > I > am using third party thin

An existing connection was forcibly closed by the remote host

Hi, I have .NetCore(v2.2.103) client and Server Ignite(v2.7.5) Application.And I am using third party thin client making request to Server to Put And Read data to/from Server. Normal application request read and put operation is happening if no of connection is less. But onces sending

Re: IGFS block at startup

Hello! It is hard to say what is happening here without full stack trace from all threads of both nodes. Can you provide that? Regards, -- Ilya Kasnacheev пн, 8 июл. 2019 г. в 13:48, Oscar Torreno : > Hello Ilya, > > > > Please find attached the docker compose log of both nodes (shapelets-1

Re: ignite cluster lock up

Hello! When full GC is running, all threads are effectively blocked. This is why it's named 'GC pause'. Regards, -- Ilya Kasnacheev сб, 6 июл. 2019 г. в 12:33, Mahesh Renduchintala < mahesh.renduchint...@aline-consulting.com>: > We are now testing by increasing failureDetectionTimeout values

Re: Re: Distributed Cluster Deployment

Hello! I think you can use sqlline.sh directly in the shell for distributed queries either way: with Java and with XML. Regards, -- Ilya Kasnacheev пн, 8 июл. 2019 г. в 04:27, shicheng31...@gmail.com : > You mean that I need to configure Ignite with Java code (call > Ignition.start()) so

Re: TcpCommunicationSpi failed to establish connection to node, node will be dropped from cluster

Hello! Since you can use Java system properties in XMLs and you can specify those on cmdline, should be not hard to automate DevOps here. Glad that you have it working. Regards, -- Ilya Kasnacheev пн, 8 июл. 2019 г. в 10:57, wiltu : > Hello! > Yep, "172.20.0.1" is a docker network IP, like

Re: IGFS block at startup

Hello! Can you please provide complete logs and stack traces from both nodes? I guess we have a lot of tests where we start several IGFS nodes and they finish just fine. Regards, -- Ilya Kasnacheev пн, 8 июл. 2019 г. в 10:16, Oscar Torreno : > Hi, > > > > I am trying to start a fresh 2

Re: configuration of ignite client nodes

The list of machines in your IP finder list does not need to be exhaustive. As long as a node can find at least one other it should be able to join the cluster. You don’t need to configure your clients to know about the other client nodes, but, by virtue of joining the cluster, they will learn

Re: TcpCommunicationSpi failed to establish connection to node, node will be dropped from cluster

Hello! Yep, "172.20.0.1" is a docker network IP, like this : = 6: docker0: mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:56:dd:06:b5 brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 scope global docker0 valid_lft forever

IGFS block at startup

Hi, I am trying to start a fresh 2 nodes Ignite 2.7.0 cluster (using docker-compose) with 2 IGFS configured. When I start both nodes at the same time, almost always one of them starts without problems, but the second one hangs at line 120 of the IgfsMetaManager class (doing an await on a

Re: Node not joined to the cluster - joining node doesn't have encryption data

any idea ? seems to be node joined and terminated , [17:01:10,562][INFO][exchange-worker-#43][time] Started exchange init [topVer=AffinityTopologyVersion [topVer=2, minorTopVer=0], mvccCrd=MvccCoordinator [nodeId=6784e9b3-c5dc-48b2-b786-30999e3041f4, crdVer=1562239510448,