How to balance many service grids in the cluster?

I want to deploy 12 service grids in a cluster with 2 ignite hosts. Every service grid only running one instance. I have though that 6 service grid runnning will run on one host, and the other 6 service grids will run on the other host. But finally I found all the 12 service grids running on

Re: What is the mechanism of Ignite distributed messaging?

I understand that this mechanism is similar to Kafka. Is there alse a place to keep the messages that have been sent by the sender but have not yet been received by the listener? If so,what is the size of the place? Is it can be configured? -- View this message in context:

What is the mechanism of Ignite distributed messaging?

I have one application using Ignite distributed messaging.In this application, Ignite receive messages from outside and sendordered them by Ignite distributed messaging. On the other side, after Ignite listener receive these messages, it will process them.I have recorded the time it took from the

Re: [GridCachePartitionExchangeManager] Pending transaction deadlock detection futures

I have created a JIRA for that. https://issues.apache.org/jira/browse/IGNITE-4924. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/GridCachePartitionExchangeManager-Pending-transaction-deadlock-detection-futures-tp11362p11767.html Sent from the Apache Ignite

Re: [GridCachePartitionExchangeManager] Pending transaction deadlock detection futures

I want to know should Visor CMD be worked in client mode or daemon mode? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/GridCachePartitionExchangeManager-Pending-transaction-deadlock-detection-futures-tp11362p11638.html Sent from the Apache Ignite Users mailing

How to set the value of RebalanceThreadPoolSize?

According to the document, RebalanceThreadPoolSize is Max count of threads can be used at rebalancing.When setted to 1 will has minimal impact on the operation of the grid. But my test result is the opposite. For example, in my test, if I set RebalanceThreadPoolSize to 1,it will affect normal

Re: [GridCachePartitionExchangeManager] Pending transaction deadlock detection futures

Yes,I use custom build. Today I tried to set Ignition.setClientMode(true) for command "open" of the visorcmd. It seems the visorcmd will not stuck the whole cluster again. Is there anything wrong in "ClientMode" of the visorcmd? -- View this message in context:

Re: Can I let Ignite to do rebalance at a particular time?

Thank you for your guidance. I will try calling IgniteCache.rebalance() via compute broadcast task. But I think it is more convenient to start rebalancing manually from management console, is it right? -- View this message in context:

Re: Can I let Ignite to do rebalance at a particular time?

I have tried CacheConfiguration.setRebalanceMode(CacheRebalanceMode.NONE), and called IgniteCache.rebalance() later, but the data did not rebalance between the nodes. Is there any problem with my usage? -- View this message in context:

[GridCachePartitionExchangeManager] Pending transaction deadlock detection futures

I start 4 Ignite servers, then I start ignitevisorcmd to view the cache. But sometimes the ignitevisorcmd will stop at "Security status [authentication=off, tls/ssl=off]" and it will stuck the whole cluster. >From the log of ignitevisorcmd, we can find the following info. "[16:52:23,640][WARN

Re: Can I let Ignite to do rebalance at a particular time?

what is the difference between "CacheConfiguration.setRebalanceMode(CacheRebalanceMode.NONE)" and "CacheConfiguration.setRebalanceDelay(-1)"? I think both of them need to start rebalance manually by calling IgniteCache.rebalance(). BTW, At the particular time, Can I know whether it need to do

Can I let Ignite to do rebalance at a particular time?

When Ignite doing rebalance, sometimes it will affect other normal processing. Can I let Ignite only to do rebalance at a particular time if necessary, such as at 0:00 every day? -- View this message in context:

Re: How to start rebalancing manually from management console

No, I use VISOR MANAGEMENT CONSOLE, started by command "sh ignitevisorcmd.sh". -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-start-rebalancing-manually-from-management-console-tp11266p11300.html Sent from the Apache Ignite Users mailing list archive at

How to start rebalancing manually from management console

For some reason, I need to set "-1" to CacheConfiguration.rebalanceDelay, and I want to start rebalancing manually from management console later. Does anyone knows the corresponding command in management console? -- View this message in context:

Remote SPI with the same name is not configured

I start an Ingnite Server node first, Sometimes when I start the second Server Node, following information outputted. [09:52:21] Security status [authentication=off, tls/ssl=off] [09:52:23,921][ERROR][main][IgniteKernal] Got exception while starting (will rollback startup routine).

what is the message guaranteed level about distributed messaging

I think there are 3 message guaranteed levels. 1. one message will be received at least once. 2. one message will be received exactally once. 3. one message will be received at most once. I want to know what is the message guaranteed level about distributed messaging. -- View this message in

Ignite client doing asynchronously operation will be jammed

I start an Ignite server first, then start an Ignite client which do some asynchronously operations on cache. But only after several seconds, the operation jammed. Is there anything wrong about my code? public class ContinuousQuery { public static void main(String[] args) {

Ignite cluster unstable when doing continuous query

I found Ignite cluster unstable when doing continuous query. Following is my test code. ContinuousQuery.java public class ContinuousQuery { /** Cache name. */ private static final String CACHE_NAME_INPUTDATA = "inputdata"; private static final String CACHE_NAME_UPDATEDATA

Re: Can continuousAsyncQuery guarantee event to be processed in order?

Does what you said "notification guarantees" mean "exactly once delivery of an event"? Does it also mean "keep the order of the events"? -- View this message in context:

Re: One failing node stalling the whole cluster

I have met the same problem. It seems that IGNITE-4003 will be fixed in version 2.0. I am using version 1.6.8 now. I want to know whether the patch about IGNITE-4003 will be merged in Vesion 1.6.x? -- View this message in context:

Re: Ignite cluster will be jammed for long-running queries

I have noticed that the patch about IGNITE-4105 has been provided, I will tried it. Thank you very much! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-cluster-will-be-jammed-for-long-running-queries-tp10210p10397.html Sent from the Apache Ignite Users

Re: Ignite cluster will be jammed for long-running queries

Yes, some queries will be long running, they are unavoidable. Query slow is acceptable, but the cluster jammed is a bit of trouble. I will be grateful if IGNITE-4105 can be solved as soon as possible. -- View this message in context:

Ignite cluster will be jammed for long-running queries

My ingnite cluster will be jammed after running for server days, I found many warnning such as "Query execution is too long" from log file. I have noticed there is a jira which is similar to my problem, the link is https://issues.apache.org/jira/browse/IGNITE-4105. In this jira, the Ignite

How to remove large amount of data from cache

I want to remove the old data from cache once a day, the amout of data is abount 5 millions. My main remove processes as below: SqlFieldsQuery Sql = new SqlFieldsQuery( "select id, name from Table2 where data = "); cursor =

Re: Cluster can not let more than one client to do continuous queries

I had modified the ignite config as following, but it did not work. http://www.springframework.org/schema/beans; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=" http://www.springframework.org/schema/beans

Re: Cluster can not let more than one client to do continuous queries

I think perhaps our test produres are Inconsistent. My test produre as following: Test RemoteFilterFactory without parameter. 1. In host 192.168.137.6, run ignite.sh -i(choose the example-cache.xml) 2. In host 192.168.137.31, run jar -cp continueclient.jar

Re: Cluster can not let more than one client to do continuous queries

continueclient.jar I have disabled peer class loading. The attachment is the test project about it. CacheContinuousAsyncQueryClient11 and CacheContinuousAsyncQueryClient12 are RemoteFilterFactory with a parameter,

Re: Cluster can not let more than one client to do continuous queries

When first client start, it is OK. When one more client start, the client will pause at following place: [08:52:08] Ignite documentation: http://ignite.apache.org [08:52:08] [08:52:08] Quiet mode. [08:52:08] ^-- Logging to file '/home/ght/ignite-1.6.8/work/log/ignite-0127ad43.0.log' [08:52:08]

Cluster can not let more than one client to do continuous queries

The usual method of setting remote filter in continuous queries is just like qry.setRemoteFilterFactory(new Factory>() { @Override public CacheEntryEventFilter create() { return new

Re: How can I detect DB writing abnormal in case of write-behind?

I had tried to enable cache statistics, but it did not work. my cache configure as following:

Re: Does Ignite support SQL statement of "INSERT"?

Does Ignite SQL statement support "DELETE" operation now? If not, What is the best way when I want to remove some data from cache in the specified condition? -- View this message in context:

Re: How can I detect DB writing abnormal in case of write-behind?

I am not understand what you mean: "In this process, something wrong in the DB, then data can not be written into it." -->For one case, some field setting was wrong in DB, such as the field length of DB is less than that in the Pojo. For another case, when process write-behind, the DB down.

How can I detect DB writing abnormal in case of write-behind?

Hello: I am trying to put some data to a cache configured with write-through and write-behind. In this process, something wrong in the DB, then data can not be written into it. I want to know how can I detect the database error as soon as possible? Can I detect it by the metrics of the

Re: When writethrough processing, Persistent storage failed

In my test, I only killed MySql DB for about 10 seconds, then restore it. Then I checked Mysql DB, I found some data missed. my test code as following: for (int i = 1; i < keyCnt; i++){ orderGood2Key = new OrderGood2Key(i); orderGood2 = new

Re: When writethrough processing, Persistent storage failed

Anyone can answer this problem? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/When-writethrough-processing-Persistent-storage-failed-tp8622p8730.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: When writethrough processing, Persistent storage failed

I have another problem about this. If DB fails, after a period of time it restore. Then during the period of time from DB fail to DB restore, all the data written to the cache is not synchronous written to DB. After DB restore, will Ignite automatically write the missed data to Oracle? --

Re: When writethrough processing, Persistent storage failed

I used the one provided out of the box. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/When-writethrough-processing-Persistent-storage-failed-tp8622p8644.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

When writethrough processing, Persistent storage failed

When I was putting data into a cache(configured writethrough), the persistent storage(Oracle) failed. Then I found Ignite still continuously trying to write data to the Oracle, Until all the public thread pools are filled. When Oracle restored, Ignite still can not automatically connect to the

Re: Affinity Collocation

If Organization cache mode is Partitioned, We all know that it can save all the Person data with the same OrganizationID in the same node. For example: All Person data with OrganizationID(3) is save in Node(2). But I still want to know, can it ensure the Organization data with the same

Re: How to avoid data skew in collocate data with data

If there are too many data related to one affinity key, even more than the capacity of one node. Will Ignite automatically split that data and stored them in several nodes? -- View this message in context:

Re: How to avoid data skew in collocate data with data

I would like to pre-distribution of data according to a certain algorithm to the designated node. Is there an API can be used to put data to a specified node? -- View this message in context:

Re: How to avoid data skew in collocate data with data

For some reason, I can not choose more selective affinty key than current. If I increase number of partition, will it help me to avoid the case that keys 553, 551, 554, 550 hitting into one node? -- View this message in context:

Re: How to avoid data skew in collocate data with data

How to increase number of partitions? And if data skew happened, how can I rebalance it? Using FairAffinityFunction()? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-avoid-data-skew-in-collocate-data-with-data-tp8454p8491.html Sent from the Apache

Re: How to avoid data skew in collocate data with data

When data skew happened, what can I do to rebalance all the data to the 3 nodes. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-avoid-data-skew-in-collocate-data-with-data-tp8454p8473.html Sent from the Apache Ignite Users mailing list archive at

How to avoid data skew in collocate data with data

I had put my data into 3 nodes with collocate data with data, and found the data is not evenly distributed across the three nodes. Node A save 30 pieces of data, Node B save 30 pieces of data, and Node C saved 900 pieces of data. The example data as following: NodeAffinityKey count A

What is the purpose of command "cache stop"

I want to release the cache space by command in tool ignitevisorcmd. I tried to the command "cache stop", after I inputted the command , I could not find the cache, but the cache space seems not be released. What is the purpose of command "cache stop"? -- View this message in context:

Re: How to get the load status of the Ignite cluster

>From the work log, I can see the Metrics for local node, such as "^-- Public thread pool [active=0, idle=512, qSize=0]" I want to know which API of metrics can I use to get the value of "active", "idle" and "qsize". -- View this message in context:

How to get the load status of the Ignite cluster

I am running Ignite under below enviroment: Message Queue--->Ignite Cache--->Continuous Queries(trigger IgniteCompute). However, in some cases, the speed of message received from MQ too fast, resulting in too much burden on the computing grid, it will affect the stability of the cluster. I want

Re: How to avoid the event lost in the continuous query

I still found some events lost. The default value of expireCount is 1 in the following config. I do not know whether this value is related to this problem. Can

Re: How to avoid the event lost in the continuous query

This example combines the code for remotefilter and locallistener. Can you tell me how to run this example in detail? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-avoid-the-event-lost-in-the-continuous-query-tp7904p7985.html Sent from the Apache

Re: How to avoid the event lost in the continuous query

How to deployment ContinuousQuery? Does remoteFilter deploy on Server side and localListener deploy on Client side? Or both remoteFilter and localListener deploy on Client side? Can you show me a detailed example? -- View this message in context:

How to avoid the event lost in the continuous query

Following is my test steps about continuous query. step 1: Start an Ignite Server by command "sh ignite.sh". step 2: Start an Ignite Client, it will do continuous query for cache1. The main code is as follows Ignition.setClientMode(true); Ignite ignite = Ignition.start();

Different of publicThreadPoolSize and systemThreadPoolSize

We can configure internal thread pool and system thread pool in XML file by What is the different of their usage? I want to configure Number of threads for write-behind caching by setting "setWriteBehindFlushThreadCount(int)", and I want to know is it use

Ignitevisorcmd can not connect to the cluster

I often use ignitevisorcmd to connect the cluster in order to watch the cache, but sometimes it fails, especially just after one slow client disconnected by the cluster. below is the info about the ignitevisorcmd. [10:32:08,149][INFO][main][TcpCommunicationSpi] Successfully bound shared memory

Question about DisableExplicitGC

I have read the aticle about jvm and system tuning (https://apacheignite.readme.io/docs/jvm-and-system-tuning#section-detailed-garbage-collection-stats). Below are sets of advanced JVM configurations for applications that might generate high numbers of temporary objects hence triggering long

Slow clients can not reconnect to the cluster

I used a Ignite client to receive data from rocketMQ and put the received data to Ignite server. For some reason, the Ignite client was disconnected by the cluster(maybe as slow client), The above is normal, but after that, the ignite client can not reconnect to the cluster automatically.

Re: Does IgniteDataStreamer support traffic control

Do you mean Ignite achieve traffic control by tuning buffer size and parallel operation amount (perNodeBufferSize(), perNodeParallelOperations())? Is there any other ways to control traffic control? -- View this message in context:

Does IgniteDataStreamer support traffic control

Sometimes the requests to put the data to IgniteDataStreamer are very frequently, this will cause the Ignite cluster instability. I want to know does IgniteDataStreamer support traffic control or anything like backpress(supported by storm)? -- View this message in context:

How to stop ignite node gracefully

Usually we use command "kill" to stop an Ignite instance. But sometimes this process will take a very long time. So we try to use command "kill -9" instead. But it may make some off-heap memory not be fully released and cause system memory leaks. I want to know is it normal? And is there any

Re: Can not start another client when doing ContinuousAsyncQuery

Yes, this problem only occurs in the case of peer class loading enabled. If I disable peer class loading, it is OK. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Can-not-start-another-client-when-doing-ContinuousAsyncQuery-tp6375p6911.html Sent from the Apache

Re: Can not start another client when doing ContinuousAsyncQuery

Following is the log about assertions, Please confirm it. [10:59:33,347][SEVERE][main][IgniteKernal] Failed to start manager: GridManagerAdapter [enabled=true, name=o.a.i.i.managers.discovery.GridDiscoveryManager] class org.apache.ignite.IgniteCheckedException: Failed to start SPI:

Re: Can not start another client when doing ContinuousAsyncQuery

Yes, both client and server run with the same config(default config). -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Can-not-start-another-client-when-doing-ContinuousAsyncQuery-tp6375p6607.html Sent from the Apache Ignite Users mailing list archive at

Re: Can not start another client when doing ContinuousAsyncQuery

I almost reproduce it every time. ExampleNodeClient just start another Ignite instance by Client mode as following, it must be started before step 2 finished. public static void main(String[] args) throws IgniteException, InterruptedException { Ignition.setClientMode(true);

Re: Can not start another client when doing ContinuousAsyncQuery

ExampleNodeStartup.java CacheContinuousAsyncQueryExample.java ExampleNodeClient.java

Re: Can not start another client when doing ContinuousAsyncQuery

Anyone has ideas? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Can-not-start-another-client-when-doing-ContinuousAsyncQuery-tp6375p6530.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Can not start another client when doing ContinuousAsyncQuery

I found it is related to "peerClassLoadingEnabled". If it is setted "true", client started failed. If it is setted "false", client started OK. The test sequence is: 1. Start a Ignite Server. 2. Start a Ignite client to do ContinuousAsyncQuery. 3. Start another Ignite client before step 2 has

Can not start another client when doing ContinuousAsyncQuery

My test steps on Ignite version 1.6 are: 1. Start an Ignite with Server mode in remote side. 2. Start a ContinuousAsyncQuery with Client Mode in local side. 3. Start an Ignite with Client Mode in local side at the same time of step 2. I only use default configuration to start Ignite in all 3

Re: "ArrayIndexOutOfBoundsException" happened when doing qurey in version 1.6.0

logs.rar Please refer to the attachment. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ArrayIndexOutOfBoundsException-happened-when-doing-qurey-in-version-1-6-0-tp6245p6287.html Sent from

Re: "ArrayIndexOutOfBoundsException" happened when doing qurey in version 1.6.0

What trace do you need? The log files in work/log? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ArrayIndexOutOfBoundsException-happened-when-doing-qurey-in-version-1-6-0-tp6245p6253.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: How to set isolated Ignite Clusters by java API

After I setted "Ignition.setClientMode(false);" and setted gridname to Ignite instance, It is OK! Thanks anyway. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-set-isolated-Ignite-Clusters-by-java-API-tp6221p6247.html Sent from the Apache Ignite Users

"ArrayIndexOutOfBoundsException" happened when doing qurey in version 1.6.0

Recentely I updated Ignite version from 1.5.8 to 1.6.0 and found some queries failed with the following information. It never happened in Ignite version 1.5.8. Could anyone help me to confirm it? [14:04:45,486][SEVERE][pub-#14%null%][GridMapQueryExecutor] Failed to execute local query:

How to set isolated Ignite Clusters by java API

I followed the guide about "Isolated Ignite Clusters on the Same Set of Machines", I tried to use xml to start ignite, it is OK. but when I tried to use java api to start ignite, it failed with the following info "[09:42:47] Failed to connect to any address from IP finder (will retry to join

Re: How to set isolated Ignite Clusters

How to set isolated Ignite Clusters I tried to use java but not xml, it failed with the following info "[09:42:47] Failed to connect to any address from IP finder (will retry to join topology every 2 secs): [/127.0.0.1:48500, /127.0.0.1:48501, /127.0.0.1:48502, /127.0.0.1:48503,

Re: How to accelerate the query speed in Partitioned Mode

Thank you for your reply. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-accelerate-the-query-speed-in-Partitioned-Mode-tp5826p6159.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: How to set isolated Ignite Clusters

It works! Thank you very much. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-set-isolated-Ignite-Clusters-tp6151p6158.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

How to set isolated Ignite Clusters

I need to start two isolated Ignite clusters on the same machine. I followed the guide about "Isolated Ignite Clusters on the Same Set of Machines", but it does not work. Ignite1 and ignite2 seems not isolated, they are connected. The 1000 records are saved in both ignite1 and ignite2, but not

Re: How to accelerate the query speed in Partitioned Mode

The data to be queried is more about 700,000 records and every record includes 10 fields. When I loaded the data to only one node, query TPS is about 66,000. If I load the data to 4 nodes by Partitioned Mode, query TPS is about 40,000. The queried field is the key and has be indexed. -- View

How to accelerate the query speed in Partitioned Mode

I want to do simple SQL query such "select ... from ... where id = ?" on cache. But the amount of data to be stored in the cache is quite large, I have to save it to several nodes with Partitioned Mode. The result is: the more server nodes, the slower the query. How to accelerate the query

Re: Continuous Queries

Assuming a server node failure during processing, then what will happen? Can it guarantees exactly once process(if my process is a cumulative operation)? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Continuous-Queries-tp4440p5350.html Sent from the Apache

Re: Continuous Queries

I have tried CacheContinuousAsyncQueryExample.java in version 1.6, and found that trigger queries(the process in qry.setLocalListener()) are still executed in local client node, but not remote server nodes. Is there any problem? If I want to make the trigger queries to be executed in remote

Re: Problem about cache data size

As the document wrote "Indexes also require memory. Basic use cases will add a 30% increase", I think it means Java domain model POJOs with 1 field indexed. I want to know whether it is always 30% in the following conditions. 1. Java domain model POJOs with 2 or 3 fields indexing. 2. Java domain

Re: Can compute grid guarantee the correctness of the result

Thank you for your advise. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Can-compute-grid-guarantee-the-correctness-of-the-result-tp4992p5010.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite cache data size problem.

I want to know how to see the size of memory used, using ignitevisorcmd? for example, for the result about "Offheap, with indexes - about 400Mb offheap memory is required, or ~20Gb for all your objects." How to confirm the offheap memory is 400Mb, from "Non-heap memory initialized", "Non-heap

At-least-once-guarantee semantics for all the data streamed into Ignite

I have read from the document about that "Data streamers are built in a scalable and fault-tolerant fashion and provide at-least-once-guarantee semantics for all the data streamed into Ignite." Can anyone tell me the more detailed theory about it and in what conditions data streamers will put

Re: Continuous Queries

Do you know when version 1.6 will release? This function is important to me. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Continuous-Queries-tp4440p4651.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Continuous Queries

My case is that after listening a process of inserting a record into an ignite cache, do more than 5 SQL querys(such as seclet ... from ... where) on other ignite caches according to this event. -- View this message in context:

how to loadCache from Hbase

Is there any example about using CacheStore.loadCache() to loading data from Hbase? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/how-to-loadCache-from-Hbase-tp4528.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Continuous Queries

If the process after the event has been listened is so complicated, The burden of the node which started the query will be quite heavy. How can I do to reduce the burden of nodes If I start the same query on several nodes, can it do load balance? -- View this message in context:

Continuous Queries

Local listener is executed on local client ignite node or on the remote ignite server node? If it is executed on local client node and I start several client node, can it do loadbalance and enhance listener processing capabilities? -- View this message in context:

Re: Is JDBC driver necessary for the storage used for Read-Through and Write-Through

Thank you very much! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Is-JDBC-driver-necessary-for-the-storage-used-for-Read-Through-and-Write-Through-tp3650p3656.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Is JDBC driver necessary for the storage used for Read-Through and Write-Through

I am going to try write-through and read-through to and from an underlying persistent storage. I would like to know about it if JDBC driver is necessary for the underlying persistent storage. -- View this message in context:

Re: java.lang.IllegalStateException: Cache has been stopped

following is the detailed log, thank you for help me to check it. 2016-03-04 20:39:26 STDIO [ERROR] Mar 04, 2016 8:39:26 PM org.apache.ignite.logger.java.JavaLogger error SEVERE: Failed to send local partition map to node [node=TcpDiscoveryNode [id=6701f10e-8319-47ac-99b2-3521cfaf91ca,

Re: java.lang.IllegalStateException: Cache has been stopped

No, I only do cache.get from the same server node. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/java-lang-IllegalStateException-Cache-has-been-stopped-tp3389p3402.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

java.lang.IllegalStateException: Cache has been stopped

Hi everyone: I ran more than 30 Ignite instances in 5 physical machines and following are my cache configure: CacheCfg.setCacheMode(CacheMode.LOCAL); CacheCfg.setOffHeapMaxMemory(0); CacheCfg.setSwapEnabled(false); CacheCfg.setReadFromBackup(false); CacheCfg.setBackups(0); After I ran ignite for

Re: How to restrict the "Get" operation in local node

I got it. Thank you! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-restrict-the-Get-operation-in-local-node-tp2785p2809.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: How to restrict the "Get" operation in local node

Today I found a bug in jira https://issues.apache.org/jira/browse/IGNITE-2526, It looks very similar to my problem. What do you think? I have another question. I have tried to set "setReadFromBackup" to false, but it seems never be used in source code. -- View this message in context:

Re: How to restrict the "Get" operation in local node

when I only created one Ignite node, I found the latency of "Get" operation is about 0.01ms. But when I do "Get" operation in a Ignite cluster including 35 nodes with "replication" mode, the latency is about 2ms. I want to know whether it is normal that With the increasing of node, "Get"

Re: How to restrict the "Get" operation in local node

Thank you for your reply. BTW, do you know when version 1.5.5 will be released? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-restrict-the-Get-operation-in-local-node-tp2785p2800.html Sent from the Apache Ignite Users mailing list archive at

How to restrict the "Get" operation in local node

I have created an Ignite cluster including several nodes with "Replication" mode. I found the latency of "Get" operation is relatively slow. I suspected that this operation is not processed at the local node. I want to how to restrict the "Get" operation in local node, but not through the network

Re: Ignite performance about put/get

Thank you for your reply. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-performance-about-put-get-tp2782p2786.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

  1   2   >