Re: Ignite loadCache performance issue

Hasan, Unfortunately, there is no way to disable off-heap memory. Since Ignite 2.0 Ignite operates over memory pages, that are allocated in off-heap memory, and accessed over Java Unsafe. You can configure eviction policy in terms of occupied memory though. You can say, that when there is a

Re: 3rd Party Persistence and two phase commit

, ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > Denis, no, its valid case. > > you can set certain StoreFactory in cache configuration so that it create > *different* instances of database(local) on different nodes. Then, my case > will be applied. > > > > ср, 17 янв.

Re: Ignite loadCache performance issue

Hi Hasan! Try disabling *onheapCacheEnabled* and *evictionPolicy *properties from configuration. I think, it may have some performance impact. Also make sure, that your database is connected to Ignite nodes via high-throughput network, and is available from every data node. > Database has 3.2

Re: 3rd Party Persistence and two phase commit

Aleksey, You described an invalid case. Cache stores on all nodes for a single cache should point to the same database. Otherwise data won't be the same in different databases. Different nodes are not supposed to have personal local DBs. If you want nodes to store data on disk in distributed

Re: Connection problem between client and server

array. It will make Ignite filter out all environment variables. It should improve node connection time in your case. Add the following lines to IgniteConfiguration in your XML: Denis ср, 10 янв. 2018 г. в 11:37, Denis Mekhanikov <dmekhani...@gmail.com>: > Hi Jeff. > > Looks like my

Re: 3rd Party Persistence and two phase commit

Hi Andrey! Actually, commit to the 3rd party database will be performed from the node, that initiated the transaction. So, there will be only one transaction on the backing database. Otherwise it is impossible to guarantee data consistency, as you noticed. Denis ср, 10 янв. 2018 г. в 18:58,

Re: How possible we can get the reason why the ignite shut down itself?

Hi Aaron! Does the whole node stop, or only a single cache? Make sure, that you don't call *Ignite.close()* or *IgniteCache.close()* anywhere or use it as a resource in a try-with-resources block. Logs may contain useful information about the node failure. Try analysing it or attach it to the

Re: Are services serialized ?

Hi Mikael! Services along with *ServiceConfiguration* are put into a replicated system cache, so they are serialized at the moment of deployment and sent to all nodes in the cluster. When service is deployed, it is deserialized. So, if you have a field, that stores a socket instance, it's better

Re: Connection problem between client and server

Hi Jeff. Looks like my letter wasn't noticed by the developer community. I sent a message to the dev list one more time: http://apache-ignite-developers.2346864.n4.nabble.com/Irrelevant-data-in-discovery-messages-td25927.html In the meanwhile make sure, that this is really the cause of the

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

-1.4.195.jar!/:?] > > at org.h2.command.dml.Select.queryWithoutCache(Select.java:625) > ~[h2-1.4.195.jar!/:?] > > at org.h2.command.dml.Query.queryWithoutCacheLazyCheck(Query.java:114) > ~[h2-1.4.195.jar!/:?] > > at org.h2.command.dml.Query.query(Query.java:352) ~[h2-1.4.195.

Re: insert into ignite cache from Netezza database using talend

Hi Kavin! Inserts are supported, but transactions are not yet (but they are expected to be this year). Make sure, that explicit transactions are not started by Talend. Denis пт, 5 янв. 2018 г. в 7:27, Kavin : > Hi, > > I am using talend to insert data from netezza

Re: off heap memory usage

Collin, To be able to see data region metrics, you should enable them either in configuration, or via MXBean. You can find a note about it here: https://apacheignite.readme.io/v2.3/docs/memory-metrics Note, that memory metrics collection should be enabled per data region. Denis пт, 5 янв. 2018

Re: Connection problem between client and server

Jeff, All node attributes, including environment variables and classpath are transmitted in discovery messages. So try to create an environment, where your app won't have this irrelevant information. To check, what is included into the node attributes, you can use the following code: ClusterNode

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

Hi Rajarshi! Well, it must be, that you are actually closing the cache. Check, that you didn't put cache creation into a try-with-resources. When *IgniteCache.close()* is called, then cache is destroyed. Denis чт, 4 янв. 2018 г. в 18:17, Rajarshi Pain : > Hi, > > I am

Re: off heap memory usage

Hi! Looks like this metric shows only non-heap memory, consumed by JVM itself. Looks like a bug. If you want to get a picture of how much memory Ignite pages consumed, you can get *DataRegionMetrics#PhysicalMemoryPages* and multiply it by a size of a data page. To do this you should enable memory

Re: Connection problem between client and server

Jeff, Your have indeed a lot of data sent over discovery. Almost all of it is taken by node attributes. Try reducing Java classpath and PATH environment variable. Also increasing of TCP window could help, because now a lot of small messages are sent instead of a few big ones. Cross-sending it to

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

Hi Naveen! CLOB is not supported in Ignite as an SQL-specific type. You can use VARCHAR for character data or BINARY for binary data. VARCHAR corresponds to java.lang.String type, and BINARY - to byte[]. There is no need to specify length for VARCHARs, it has no effect. VARCHARs always can have

Re: Connection problem between client and server

Hi Jeff! 1 MB sound like a lot of data. Especially for discovery protocol. I didn't check, what is the volume of discovery data normally, but I think, it shouldn't be measured in megabytes. If you don't create thousands of caches, of cause. What work load do you perform on your cluster? How many

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

Hitesh, Problem, that you described looks similar to the one described in the following ticket: https://issues.apache.org/jira/browse/IGNITE-1535 Please consider submiting a patch, if this functionality is critical for you. Denis ср, 3 янв. 2018 г. в 13:51, Hitesh :

Re: Cache persistence question

ey are > written to storage. > > Den 2018-01-03 kl. 12:55, skrev Denis Mekhanikov: > > Hi Mikael! > > Yes, this is fine. Expiration policy is intended to remove those entries > from memory, that are saved to the persistent data storage. > So, if you query expired data one mo

Re: Cache persistence question

, Denis Mekhanikov <dmekhani...@gmail.com>: > Hi Mikael! > > Yes, this is fine. Expiration policy is intended to remove those entries > from memory, that are saved to the persistent data storage. > So, if you query expired data one more, it will be loaded from persistence.

Re: Cache persistence question

Hi Mikael! Yes, this is fine. Expiration policy is intended to remove those entries from memory, that are saved to the persistent data storage. So, if you query expired data one more, it will be loaded from persistence. > will any items in the cache that expire and have been modified be saved

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

. 2018 г. в 13:22, Hitesh <hiteshnandwan...@gmail.com>: > hey @Denis Mekhanikov I am asking that I am getting older entries also > which > should be removed from cache > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >

Re: Ignite throwing Out Of Memory

Hi! I see in the CSV, that you provided, that there are a lot of BinaryObjects on heap. Looks like you are streaming data, using DataStremer, and batches of it are stored on heap. I don't see the reason of your confusion. The app consumed more memory, than during last 6 months, so it failed with

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

Hi Hitesh! What do you mean by older versions? FIFO eviction policy can limit size of a cache, and it specifies the order, in which values will be evicted. Does it work in some other way? Denis ср, 3 янв. 2018 г. в 8:05, Hitesh : > I am using fifo eviction policy,

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

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

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

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

Re: Upgrade from 2.2.0 to 2.3.0 problem with BinaryObjectException

Oh, looks like this problem is already fixed: https://issues.apache.org/jira/browse/IGNITE-6944 I checked, your project works, when Ignite from current master is used. So, you can just wiat for the next release and switch to it. Denis ср, 20 дек. 2017 г. в 13:10, Denis Mekhanikov <dmekh

Re: Upgrade from 2.2.0 to 2.3.0 problem with BinaryObjectException

Hi Łukasz! This problem is caused by *@Cacheable* annotation on *SampleRepo#getSampleEntity() *method. When you invoke it for the first time, its result is put into an Ignite cache. And for the second time the result is just taken from the cache, you probably know that. The problem is that

Re: Re: Re: Re: Re: Re: Re: Re: Re:Poor performance select query with jdbc thin mode

Lucky, If you want to run queries with *JOIN*s, you should make sure, that entries are collocated. It means, that all data for a* JOIN* should be available on a single node. You may have many nodes, but each row of the result should be composed of the data, that is stored within a single data

Re: Re: Re: Re: Re: Re: Re: Re: Re:Poor performance select query with jdbc thin mode

Lucky, Please provide explain and timing for the same query, executed on a single node. Denis ср, 6 дек. 2017 г. в 16:27, Lucky : > well,3 node took about double time of single node. >

Re: Re: Re: Re: Re: Re: Re: Re:Poor performance select query with jdbc thin mode

Lucky, You can find information about distributed joins tuning here: https://apacheignite-sql.readme.io/docs/distributed-joins It contains explanation of how distributed joins work, and why it's important to keep data collocated. Denis ср, 6 дек. 2017 г. в 13:06, Denis Mekhanikov <dmekh

Re: Re: Re: Re: Re: Re: Re: Re:Poor performance select query with jdbc thin mode

Looks like you ran this query on a cluster with more than one node, so you get performance drop because of distributed joins. Let's tune performance on a single node first. You can expect queries with joins to operate fast only if data is collocated. Otherwise latency will suffer from network

Re: Re: Re: Re: Re: Re: Re:Poor performance select query with jdbc thin mode

Lucky, Well, at least we figured out, that JDBC drivers and IgniteCache#query don't have that huge difference, that you told us about :) Could you show result of *EXPLAIN *for this query? Did you configure any indexes? Denis ср, 6 дек. 2017 г. в 4:05, Lucky : > No, the

Re: ignite.compute(ClusterGroup) is broken??

Chris, That's right. You get nodes from affinity function, that doesn't know anything about a cluster group. And you ignore *subgrid *parameter, that is collected with regard to the ClusterGroup. Denis вт, 5 дек. 2017 г. в 18:08, Chris Berry : > Denis, > > My current

Re: ignite.compute(ClusterGroup) is broken??

Chris, Tasks are sent to all nodes, that return from map() method, regardless of the provided ClusterGroup. ClusterGroup only affects a list of nodes, that are specified in *subgrid* parameter. So, it's your responsibility to assign tasks to nodes, that match your needs. If you want to send them

Re: Re: Re: Re: Re: Re:Poor performance select query with jdbc thin mode

So, the problem was in measurement, right? Denis вт, 5 дек. 2017 г. в 12:39, Lucky <wanxing...@163.com>: > > now it is about the same as JDBC thin mode. > > > > > > At 2017-12-05 16:52:48, "Denis Mekhanikov" <dmekhani...@gmail.com> wrote:

Re: Register Contentious query quit slow

Jin, > Fact is after I commented out IQ, RF and keep local listeners exists, no more meta data update happened and the program still work. I already explained you in the previous letter, where this metadata update comes from. It's because you transfer IQ and RF over network. On the other hand,

Re: Re: Re: Re:Poor performance select query with jdbc thin mode

gt; > Thanks. > > > > > > 在 2017-12-01 23:52:48，"Denis Mekhanikov" <dmekhani...@gmail.com> 写道： > > Lucky, > > If you enable *enforceJoinOrder* option, then join operations will be > performed in the exact order, in which they appear in the quer

Re: ignite.compute(ClusterGroup) is broken??

Chris, I lost track of our discussion, because this part of your system seems to be too overarchitectured. Can you provide a short summary of what you are trying to achieve? The main thing that I don't understand is why you need a *map* method? This method is supposed to be used as a part of a

Re: Deploy Cluster Singleton blocks and never returns

Hi Jean! What is your service configuration? Maybe you specified some node filter, that doesn't accept any nodes? There is also a known issue with services with injected Spring resources: https://issues.apache.org/jira/browse/IGNITE-6555 Do you have something like that in your service

Re: Re: Re:Poor performance select query with jdbc thin mode

11:30, Lucky <wanxing...@163.com>: > Denis, > It's worse! > There just have several sql can be faster, the other took more time. > Thanks. > > > > > > 在 2017-11-29 21:31:05，"Denis Mekhanikov" <dmekhani...@gmail.com> 写道： > > Lu

Re: Re: Re: Re: Re: JdbcQueryExecuteResult cast error

> add additional synchronization? > But how? You should make sure, that one JDBC connections is not used from multiple threads simultaneously. You can, for example, acquire some lock before using it. > Another thing, the JDBC connection can be closed automatically? Do you mean closing by

Re: Re: Re: Re: JdbcQueryExecuteResult cast error

Also I have say before, that If I exit the system,And relogin again, > it is normal. > > Thank you very much. > > > > At 2017-11-29 18:37:33, "Denis Mekhanikov" <dmekhani...@gmail.com> wrote: > > Lucky, > > What tool are you using to access Ignite over JDBC? Does this problem > reproduce, if you use DBeaver, for example? > As Taras said, looks like the same JDBC connection is used concurrently. > > Denis > >> >>>

Re: Register Contentious query quit slow

pys? as you can see, my > initial query and remotefilter just do a string compare and dont need any > extra class help, all my logic is in local listener which just runs > locally. > i dont see necessary for that exchange in this case. is that a bug? > br, > jin > ---Orig

Re: Re:Poor performance select query with jdbc thin mode

and took 5 seconds in > cluster(3 ignite nodes). > > JDBC Client driver is worse than JDBC thin driver. it took about more > 1 seconds. > > Did there any other suggestiones? > Thanks. > > > 2017-11-24 20:25,Denis Mekhanikov<dmekhani...@gmail.com> >

Re: Re: Re: JdbcQueryExecuteResult cast error

rnal.jdbc.thin.JdbcThinTcpIo.send(JdbcThinTcpIo.java:376) > at > org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.sendRequest(JdbcThinTcpIo.java:325) > at > org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:668) > > Since then, n

Re: Re: JdbcQueryExecuteResult cast error

How many thread do you use for update & select? In case your application > is multi-threaded be sure that separate JDBC Connection is used for each > thread. Ignite JDBC API is not thread safe. > > Otherwise, please share the smallest reproducer / steps to reproduce. > >

Re: Cache size changes unexpectedly

tTime/getAveragePutTime? Do they provide average get time for > entire cluster or just local node? > > > > -Biren > > > > *From: *Denis Mekhanikov <dmekhani...@gmail.com> > *Reply-To: *"user@ignite.apache.org" <user@ignite.apache.org> > *Date:

Re: Register Contentious query quit slow

Jin, Regarding the problem with initial query: it's not binary metadata update, what causes the slow-down, but processing the data. Binary metadata update is done by just sending a few messages across the ring, it's not a big deal, you shouldn't care too much about it. You just have a lot of

Re: Node unable to join cluster

eout=1] > > 2017-11-27 10:35:55 [grid-nio-worker-tcp-comm-0-#17%nvIDNGB1%] INFO > TcpCommunicationSpi:463 - Established outgoing communication connection > [locAddr=/10.105.244.16:47214, rmtAddr=/205.139.17.146:1511] > > > > Thanks. > > > > *From:* Denis

Re: Register Contentious query quit slow

And are you sure, that it's not initial query causing continuous query to register slowly? Maybe class loading has nothing to do with it? Denis пн, 27 нояб. 2017 г. в 19:26, Denis Mekhanikov <dmekhani...@gmail.com>: > You wrote in your previous letters, that startup takes much time. &g

Re: Register Contentious query quit slow

You wrote in your previous letters, that startup takes much time. Could you clarify, whether node connection to a cluster takes much time, or query execution? Because I'm a bit confused. The messages, that you see is not a class deserialization, it's binary metadata update messages. They appear

Re: Unable to start Hadoop Accelerator with Persistence

I don't see much sense in using both HDFS and Ignite native persistence, since HDFS stores data on disk on its own. Could you describe your use-case? Maybe, there is a point to allow it, if there is a valid usage scenario. Denis сб, 25 нояб. 2017 г. в 6:31, Amol : >

Re: JdbcQueryExecuteResult cast error

Could you attach queries, that you are trying to execute and full error message? Also make sure, that JDBC driver version is also 2.3 Denis сб, 25 нояб. 2017 г. в 12:39, Lucky : > Hi > The ignite version is 2.3 > When I update something by cache.query(new

Re: IgniteInterruptedException: Node is stopping

Hi Hyma! Looks like you encountered a classic deadlock. It happens because you put values into cache in arbitrary order. This line causes this problem: *companyDao.nameCache.putAll(kvs)* So, when multiple threads try to acquire the same locks in different order, then these operations will be

Re: Service deployment

Hi Mikael! You don't need to check whether a service is already deployed. Ignite will handle such collisions, but only if you don't try to deploy the same service multiple times with different configurations. Otherwise you will get an exception. If configurations match, then consecutive

Re: Public thread pool idle number is always 0 ?

Hi! You shouldn't set thread pool size to such high values. It's recommended to leave it default (number of available cores), or 2 x number of cores. > I found Public thread pool idle numbers on every node is always 0 What do you mean by that? How did you check it? CPU load may be low, if

Re: AffinityKey question

Mikael, If you choose to use *AffinityKey* to wrap your keys, then you should use it everywhere. Because basically it's just a tuple of a key and affinity key, so this pair is used as a composite key. You can also annotate some field of you key class with *@AffinityKeyMapped*, instead of using

Re: Poor performance select query with jdbc thin mode

Hi! Please try running the same test on Ignite 2.3 Also try changing to JDBC client driver and let us know the results. Denis пт, 24 нояб. 2017 г. в 12:25, Lucky : > Hi: >I need to return a ResultSet, So I had

Re: ComputeTask is including Nodes for ComputeJobs prematurely

> Affinity is not affected by IgniteCompute. My mistake. > I get a hold of an IgniteCompute _before_ the Affinity is applied I'm not sure, what you are trying to say. Correct me, if I'm wrong, but you are trying to choose a node to run a compute task on, depending on where a needed key is stored

Re: JDBC ResultSet get columns with table alias

Hi! Column access by name is supported by Ignite. Can you provide more details about your issue? Project with reproducer would be great. At least let us know, what version of Ignite and JDBC driver (thin or client

Re: Node unable to join cluster

scovery SPI > > TcpDiscoverySpi discoverySpi = *new* TcpDiscoverySpi(); > > discoverySpi.setLocalPort(1510); > > discoverySpi.setLocalPortRange(1); > > discoverySpi.setIpFinder(ipFinder); > > discoverySpi.setNetworkTimeout(2); > >

Re: Cache size changes unexpectedly

local to the node? > > > > -Biren > > > > *From: *Denis Mekhanikov <dmekhani...@gmail.com> > *Reply-To: *"user@ignite.apache.org" <user@ignite.apache.org> > *Date: *Wednesday, November 22, 2017 at 8:13 AM > *To: *"user@ignite.apache.org" <user@

Re: Register Contentious query quit slow

lowed. > what kind of port is ignite actually used? I thought just 47500 47100 > 10800 and some others but not random,right? > > ---Original--- > *From:* "Denis Mekhanikov"<dmekhani...@gmail.com> > *Date:* 2017/11/22 23:04:21 > *To:* "user"<user@

Re: Cache size changes unexpectedly

Hi Brien! I tried to run a cluster with a cache configured like you described, but everything works fine. Could you provide more information about this issue? A project with a reproducer will be ideal. Are you sure that you measure size correctly? Denis ср, 22 нояб. 2017 г. в 1:28, Biren Shah

Re: Unable to query system cache through Visor console

Hi Krzysztof! It's even problematic to get an instance of system cache over Java API, not even from Visor CLI. Internal system information is stored there, so it's hidden from users. And Visor cannot access it as well, because it uses public API. Why would you want to do something like that?

Re: Register Contentious query quit slow

> I wondered why connecting so many port, as my configuration is like You see remote ports, that are opened on remote nodes to establish a client connection. They are chosen by the OS arbitrary and may differ from the ones you specified in config. > Does the "Class locally deployed" means load

Re: WAL size control

Hi David! WAL is a ring buffer on the filesystem. Each file in it is called a "segment". By default each segment occupies 64 MB on disk (*walSegmentSize* property), and there are 10 such files in the buffer (*walSegments* property). So, WAL

Re: Unable to read all the entries in present single cache using Streamer

As Alexey said, DataStreamer is for loading data *to* Ignite. So, If you want to get data *from *Ignite, you may choose to use IgniteCache#iterator() method. But note, that this method is not transactional,

Re: Register Contentious query quit slow

etwork is not good. > Is that matters? should i just specfiy the port exactly? > > ---Original--- > *From:* "Denis Mekhanikov"<dmekhani...@gmail.com> > *Date:* 2017/11/21 20:27:43 > *To:* "user"<user@ignite.apache.org>; > *Subject:* Re: Register

Re: Node unable to join cluster

Hi Josephine! Make sure, that TcpDiscoveryVmIpFinder has address of the local node on the list. Otherwise the first node won't be able to start, because discovery SPI won't find any nodes. Also note, that TcpDiscoverySpi has localAddress and localPort properties. Try setting them according to

Re: Register Contentious query quit slow

Hi! It's hard to tell, what causes such long startup time. What do logs say? Try enabling debug log and watching, what nodes are doing all that time. Please let me know if you find something. I don't think, that peer class loading causes it, because it only works for compute jobs and a few more

Re: ComputeTask is including Nodes for ComputeJobs prematurely

Chris, If it's exactly the thing that you want to achieve, you can start Ignite twice. First time - to get contents of the "admin cache", and second time, after all initialization is finished - to accept compute jobs. To avoid compute jobs from being executed by the first node, you can run them

Re: ComputeTask is including Nodes for ComputeJobs prematurely

Hi Chris! Can you just start Ignite after you finished all initialization that is needed by compute jobs? Denis чт, 16 нояб. 2017 г. в 21:25, Chris Berry : > No. There are things in the general application that are not yet > initialized. > It is essentially a

Re: Custom Expiry Policies ?

Sorry, I provided the same link twice. This is a link to ExpiryPolicy interface JavaDoc: https://static.javadoc.io/javax.cache/cache-api/1.0.0/javax/cache/expiry/ExpiryPolicy.html Denis пн, 20 нояб. 2017 г. в 13:08, Denis Mekhanikov <dmekhani...@gmail.com>: > Hi! > > Here

Re: Custom Expiry Policies ?

Hi! Here is description of expiry policies, that are implemented in Ignite: https://apacheignite.readme.io/docs/expiry-policies. In most cases it will be enough just to choose one of them and configure it properly. But you can also implement it yourself and provide it to cache configuration. Here

Re: Using two ignite contexts with spark streaming

Hi! I don't really see what you are trying to achieve. In the example, that you provided, the second IgniteContext, called ignitec2, is not used. Do you mean that when you start the second IgniteContext, then both of them stop working? When ignitec.fromCache("Data2") is executed, then cache is

Re: Race in Service Grid deployment?

Hi Artem! This is a known issue. I created a JIRA ticket for it: https://issues.apache.org/jira/browse/IGNITE-6571 The exception that you see in log doesn't mean anything bad, it just means that you are trying to call a method of a service that is already deployed, but haven't initialized yet.

Re: An issue of Ignite In-Menory Sql Grid since version 2.0.0

advise discontinuing the SQL for the use case. > > > Alex P., Vladimir, > > What’s the main reason of WITH RECURSIVE removal? Why it worked before and > broken now? > https://issues.apache.org/jira/browse/IGNITE-5289 > > — > Denis > > On Sep 25, 2017, at 12:31 AM

Re: Cassandra Persistence problem

Hi! Try commenting out this line: configuration.setWriteBehindEnabled(true); Write behind mode makes a cache wait for a moment, when there is enough updates to write them in a batch. Disabling this mode should help. Denis вт, 26 сент. 2017 г. в 16:09, elopez779 : >

Re: POJO field having wrapper type, mapped to cassandra table are getting initialized to respective default value of primitive type instead of null if column value is null.

There is a page in confluence with description of the process: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute To get permission to assign tickets to yourself you should write a letter to dev list and ask for it by telling your JIRA username. While waiting for JIRA

Re: Re: What's the best practice to init the cache when in cluster env?

egated run locally on each nodes, we do not want > this will be too heavy on the first node. > > > Regards > Aaron > ------ > aa...@tophold.com > > > *From:* Denis Mekhanikov <dmekhani...@gmail.com> > *Date:* 2017-09-25 19:46 > *To:*

Re: ClusterTopologyCheckedException: Failed to wait for request completion (node has left) while loading data into using savePairs method of Ignite Red

Hi! This exception is usually thrown when topology changes during execution of some operation. Did you see messages in logs that this node with id from the exception failed or left? Denis вт, 26 сент. 2017 г. в 3:48, pradeepchanumolu : > I am using savePairs method of

Re: POJO field having wrapper type, mapped to cassandra table are getting initialized to respective default value of primitive type instead of null if column value is null.

If somebody fixes this issue, then the fix will be included in 2.4 release. If you want to know for sure, the best chance for you is to fix it yourself, so feel free to contribute. Code freeze for 2.3 is planned for the end of this week, so you have chances to make it in 2.3 Denis вт, 26 сент.

Re: POJO field having wrapper type, mapped to cassandra table are getting initialized to respective default value of primitive type instead of null if column value is null.

I guess, you are right. It's worth checking if the column value is null for wrapper types in that method. Please file a ticket to JIRA: https://issues.apache.org/jira/secure/Dashboard.jspa Also consider contributing this patch to Ignite. Denis пн, 25 сент. 2017 г. в 17:13, kotamrajuyashasvi

Re: What's the best practice to init the cache when in cluster env?

Hi Aaron! There are two good options for data loading: using DataStreamer or IgniteCache.loadCache(...) . The second option is good when initial data is stored in some database. If you worry about overhead on data

Re: Ignite Context : java.lang.NoSuchMethodError: org.apache.curator.framework.api.CreateBuilder.creatingParentContainersIfNeeded

Make sure that all dependencies are present in classpath during execution. In your case you need curator-framework:2.9.1 library. You should either add jars of these libraries to --jars option of spark-submit command, add needed dependencies to Spark configuration, or build an uber-jar that will

Re: Re: An issue of Ignite In-Menory Sql Grid since version 2.0.0

. 2017 г. в 4:11, 贺波 <hebo...@163.com>: > Hi! > I have executed the recursive sql statement on H2 database,it > executes correctly.But it executes error since version 2.0.0.So I think > it's a bug of Ingite,not H2.My test demo is in the attachment. > > > > > &

Re: Ignite Server start failing with the exception with Ignite 2.1.0

Hi! Could you describe your scenario in more detail? What configuration do your nodes have and in what order do you start them? Do some nodes go down during the deployment? What environment do you have? Situation that you described sounds too simple to cause any problems. Denis чт, 21 сент.

Re: An issue of Ignite In-Menory Sql Grid since version 2.0.0

Hi! Internally Ignite uses H2 to process SQL queries. Recursive queries is an experimental feature of H2, so I wouldn't recommend you to use it in production for now. Ignite 2.0 and 2.1 don't seem to support this kind of queries, so the best option for you is to modify your query if possible to

Re: Ignite Context : java.lang.NoSuchMethodError: org.apache.curator.framework.api.CreateBuilder.creatingParentContainersIfNeeded

Hi! Apparently you have some problem with classpath. Looks like version of Apache Curator used in runtime differs from the one used during compilation. It will be easier to say what is wrong if you provide your pom.xml Denis чт, 21 сент. 2017 г. в 8:57, pradeepchanumolu :

Re: Compute Grid Request Tracing

Hi Chris! Take a look at the documentation of LoggerResource annotation: https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/resources/LoggerResource.html You can annotate a field of ComputeTask, ComputeJob or some other classes and use the injected logger during execution. Does

Re: Ignite/yardstick benchmarking from within Docker Image

You can change a docker entry point, so Ignite instance won't start by default. You can do something like this: *docker run --entrypoint=/bin/bash -it apacheignite/ignite* Denis -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Unsubscribe

Hi Jessie. Sorry to see you go. To unsubscribe from the user mailing list send a letter to user-unsubscr...@ignite.apache.org with a word "Unsubscribe" without quotes as a topic. If you have a mailing client, follow an unsubscribe link here:

Re: Problem with transactions in Apache Ignite!

with ongoing transactions. So aparently it is not a bug. Denis ср, 20 сент. 2017 г. в 17:37, Denis Mekhanikov <dmekhani...@gmail.com>: > Sergey! > > After offline discussion I managed to reproduce your problem. > It seems that IgniteCache.size(...) doesn't take into account changes mad

Re: Problem with transactions in Apache Ignite!

:23, Denis Mekhanikov <dmekhani...@gmail.com>: > Hi! > > Could you please provide a pure Ignite reproducer that won't involve > Hibernate OGM? > Right now it's hard to tell whether the problem is in Ignite or in > Hibernate. > > Thanks! > Denis > > с

<    1   2   3   4   >