Re: Query performance affected by record size?

Hi, Could you please share the queries you run against the cache? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Possible dead lock when number of jobs exceeds thread pool

Hi, That actually looks like a starvation in public pool where compute tasks are processed. Please share PerformRenderer() source. Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Possible dead lock when number of jobs exceeds thread pool

Raymond, Yes. Your understanding is correct, that should be the reason of starvation. Please take a look at custom thread pools https://apacheignite.readme.io/v2.2/docs/thread-pools#section-custom-thread-pools. Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Possible dead lock when number of jobs exceeds thread pool

Hi Raymond, You are right. As for now, C# API doesn't support WithExecutor calls. Please find a corresponding ticket for your reference https://issues.apache.org/jira/browse/IGNITE-6566 In this case. You could increase the public thread pool

Re: TcpDiscoveryS3IpFinder AmazonS3Exception: Slow Down

Hi Dave, Probably switching to VPC increased the request rate what caused the mentioned exception. Please share the corresponding Ignite logs. Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Write Behind Performance

Hi Rick, 1) As for now, there is no API for checking write-behind queue size. In any case, such method would provide only an approximate result. 2) You should carry out some testing to figure out the appropriate balance between the batch size and flush frequency that will fit your particular case.

Re: Query performance affected by record size?

Hi, Probably you have pretty much data that satisfies the condition. Try running EXPLAIN command to check the query plan. In general, it's better to move child objects into a separate cache and establish a relation via affinity

Re: Multiple Ignite Clusters using the same Zookeeper cluster

Hi, Have you tried setting different base paths for each grid via TcpDiscoveryZookeeperIpFinder#setBasePath ? Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Number of Caches

Hi, Actually, the number of caches is mostly restricted by the available memory, since every cache implies about 20M overhead. So, for 3K caches a rough estimate is 3000 * 20M = 6M ~ 59G. Please share full logs for the client node. Kind regards, Alex -- Sent from: http://apache-ignite-use

Re: Possible dead lock when number of jobs exceeds thread pool

Hi Raymond, Yes. Bringing C# client in sync with Java version is on plans. Of course, C# client will always be a bit outdated in terms of features of Java client. Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: (Cross Platform)c# wrapper for java CacheStoreAdapter for database persistence

Hi, Please take a look at the end of the following documentation section Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cache pre-loading question

Hi Franck, Yes. You would need to implement the same mapping logic in your client populating a cache via data streamer. A custom CacheStore or CacheJdbcPojoStore should be an easier approach in case of an underlying DB, especially if you need read-through/write-through semantics as well. Kind reg

Re: Cache pre-loading question

Hi, By "custom" CacheStore I meant that you could implenent a CacheStore with your custom read/write logic, but since you are using CacheJdbcPojoStore it should be OK. IgniteCache does have loadCache method. Please take a look at https://apacheignite.readme.io/docs/data-loading#section-ignitecach

Re: Lock on cache keys during node failures

Hi Naresh, In case of a node failure, all the locks acquired by that node will be released. So, if there is a node waiting on any of such keys it should eventually acquire the lock. Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: insert data took too much time

Hi, Did you have a chance to compare the results with cache.put performance? You mentioned that you set writeBehind to true, so do you have a cache store configured? What is the INSERT rate for the underlying DB in this case? Did you enable persistent store option? What is CPU and memory utiliza

Re: map types in Cassandra

Hi, It's hard to say for sure what is the problem without the logs. But obviously, it's a configuration issue. Please take a look at the corresponding documentation https://apacheignite-mix.readme.io/docs/ignite-with-apache-cassandra

Re: Ignite Transaction with Locks but not SERIALIZABLE user case.

Hello, increment/decrement is a read-modify-write operation, so to achieve the desired behavior you need to lock the key and perform the operation under that lock. So you need to use a transaction mode and isolation level that meet the requirements. For this case, you could use the approach descr

Re: No Error/Exception on Data Loss ?

Hi, If a client is up before a node leaves the cluster then it could listen to org.apache.ignite.events.EventType#EVT_NODE_LEFT and org.apache.ignite.events.EventType#EVT_NODE_FAILED events. If a client may start after a possible server node failure, then there is no solution out of the box but y

Re: QueryEntity Based Configuration

Hi, Indexes for nested collections and in particular for maps are not supported. If you need indexes for data please consider analyzing and refactoring the problem domain. You could either flatten map so that its keys become fields of the Model or move data into separate cache/caches related to

Re: QueryEntity Based Configuration

You could introduce an additional Model data cache that will store *data* for each Model as it is usually done in a regular ORM systems (http://docs.jboss.org/hibernate/orm/5.2/userguide/html_single/Hibernate_User_Guide.html#collections-map) The key for the Model data cache should include the key

Re: Adding user attribute after node has started

Hi, Node attributes can be added only before node startup. To start a cache on specific nodes you could use CacheConfiguration#setNodeFilter Ignite#compute(org.apache.ignite.cluster.ClusterGroup) accepts a cluster group which could be, for example ignite.cluster().forAttribute(...). As well, yo

Re: QueryEntity Based Configuration

Hi, Crossposting from the mail list, since looks like something is broken and some messages don't get it here. On Mon, Nov 27, 2017 at 1:48 AM, daniels wrote: Hi dear afedotov.I have a question,related to your claim "Indexes for nested collections and in particular for maps are not supported.

Re: Number of open file handles keeps on increasing on Ignite node on adding a new cache

Hi, Do you use Ignite Persistent Store? If that's the case, then for each cache partition there is a corresponding file created. Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Web Console on Kubernetes Cluster

Hi, Please take a look at this documentation section https://apacheignite.readme.io/docs/resource-injection. If you are going to inject @SpringResource you need to adopt IgniteSpringBean. Make sure that you have checked its JavaDoc before using it because some caution should be taken due to its l

Re: Ignite in docker (Native Persistence)

Hi, You need to create volumes and map them to the ${IGNITE_HOME}/work/db or any other path that you might have specified via setPersistentStorePath. These volumes should outlive the Ignite containers and thus it will be possible to reuse them on restart. It's worth trying docker-compose, docker-

Re: Can the cache key and affinity key be different

Hi, To collocate A and B with C you need to introduce custom key classes for A and B that will include @AffinityKeyMapped annotation on a C's ID field. An example of how to implement such a key could be found here https://apacheignite.readme.io/docs/affinity-collocation#section-collocate-data-with

Re: index about jdbc thin mode

Hi, Not sure, what's wrong with your code. Either IX_T_BD_StatusFid or IX_T_BD_CUSTOMER should have been taken. I removed JPA related annotations and checked your code, it gave me the following plan: [[SELECT __Z0.FID AS __C0_0, __Z0.FNUMBER AS __C0_1 FROM "customerCache".CUSTOMERIGNITEIN

Re: index about jdbc thin mode

Hi, Just to clarify, the same result I have while running using the thin JDBC driver. Class.forName("org.apache.ignite.IgniteJdbcThinDriver"); try ( Connection conn = DriverManager.getConnection("jdbc:ignite:thin://localhost:10800"); PreparedStatement pre

Re: Re:Re: index about jdbc thin mode

Hi, Actually, the same exact code I sent you works as expected on my side. Could you share a reproducer so that I can take a look at it? At least, please Ignite configuration and how you run explain query via thin JDBC driver. Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.

Re: Re:Re: Re:Re: index about jdbc thin mode

Hi, Your configuration perfectly works on my side. Make sure that you are connecting to the server node with an appropriate configuration of indexes. I'm afraid, that without a complete reproducer it's not possible to figure out the reason. Kind regards, Alex -- Sent from: http://apache-ignit

Re: javax.cache.CacheException: Failed to run map query remotely.

Hi, Please share the full log. Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cache listener for new keys

Hi, Could you please describe what are you trying to achieve with this logic? Entry related events usually send both the key and the value. You could take a look at continuous queries instead https://apacheignite.readme.io/docs/continuous-queries. As well, you could specify filters for local or r

Re: Cache listener for new keys

I mentioned continuous queries and listener filters because you probably have some logic around keys that could be handled by these means. As an option, you could utilize Ignite messaging. Of course, you could have a separate cache containing only keys that you would update. Could you describe wha

Re: javax.cache.CacheException: Failed to run map query remotely.

Hi Raj, Provided is only the top of the reason, there should be more details regarding the problem on the remote nodes. Probably query could not be parsed or something wrong with config. Could you please share Ignite config and the query you run? Kind regards, Alex -- Sent from: http://apache-

Re: why the records not zero after execute "cache -clear"

Hello, I was not able to reproduce the problem on my side. Could there be a chance that you had stopped a server node with persistence before calling cache -clear? Is the problem reproducible? How do you stop nodes? Is it kill -9 or something else? Please share Ignite configuration used for Spar

Re: Failed to instantiate Spring XML application context

Hi, Looks like you don't have required Ignite libs on your classpath. Please check your classpath for its presence. Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Count mismatch for a cache between ignitevisor & Sqlline

Hi, Could you please check, what result would produce a regular Ignite SqlFieldsQuery? Would it be the same result as for Sqlline? Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: how to set SQL timeout for the cluster?

Hi, For now, it's possible to set timeout only on the query based level, i.e. setTimeout(). You could create a utility factory method for the Query instances that would set up the required timeout and use it throughout the code. Kind regards, Alex -- Sent from: http://apache-ignite-users.7051

Re: Cache listener for new keys

Hello, OK. How do you use these registries after that? I don't think that there is a need to keep version in the key. Ignite guarantees that a cache contains the latest version at each moment. Probably the only things you need to keep in the key object are id and type. Even if you need to handle

Re: Is it possible to change notify event for continuous query

Hi, As for now, it's not possible out of the box. There is a correponding ticket for that https://issues.apache.org/jira/browse/IGNITE-425. Meanwhile, you could pass the results via an auxiliary caches and configure corresponding continuous queries for them. Kind regards, Alex -- Sent from: ht

Re: Cache listener for new keys

Hello, FYI. There is a ticket that should introduce the desired behavior. https://issues.apache.org/jira/browse/IGNITE-425 Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Trying to pass memory arguments to Ignite.sh - ./bin/ignite.sh -J -Xms2g -Xmx10g -v config/IgnitePOC-NoCacheInfo.xml

Hi, Yes, you are right. Probably -J"-Xms4g -Xmx8g" should have worked too. Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Node can not join cluster

Hi, >From logs, I can see that the node was not able to connect to the cluster due to a timeout issue. It could be caused by GC or network issue. Please check the logs of other nodes, especially of the coordinator node fcc47ef7-f080-4f88-93f5-2bc221dd1fcf. Kind regards, Alex -- Sent from: http

Re: SQL Count(*) returns incorrect count

Hi, For an example of table creation via native API please check https://apacheignite-sql.readme.io/docs/schema-and-indexes#section-overview. Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: thread number tradeoff

Hi, I think setting appropriate thread pools size to 2 should work for you. Just check which thread pools need to be adjusted depending on your use case. It's worth noting that having 8 nodes per machine you are sacrificing throughput for response time. Kind regards, Alex -- Sent from: http:/

Re: Ignite node getting stopped by itself

Hi, Could you please share full logs so that the surroundings of the problem could be checked? Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Re:Re: Node can not join cluster

As you could see in the logs [09:06:26,657][WARNING][main][TcpDiscoverySpi] Node has not been connected to topology and will repeat join process. Check remote nodes logs for possible error messages. Note that large topology may require significant time to start. Increase 'TcpDiscoverySpi.networkTi

Re: Adding custom processor in Ignite Node

Hi, 1) Why do you want to implement your own processor? 2) Have you considered using Ignite's compute grid and other features instead? If yes, what problems do you anticipate? Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Test Ignite Client

Hi Humphrey, Consider forcing server mode on the client https://apacheignite.readme.io/docs/clients-vs-servers#section-forcing-server-mode-on-client-nodes. Another option is to enforce bean definition registration order. You could explicitly order configurations so that server bean gets registere

Re: How can we create a TOPIC Config?

Hi, Did I get you correct, that you want to send an update to a topic every time the cache is updated? If that is the question then I would suggest you taking a look at the following: https://apacheignite.readme.io/docs/events https://apacheignite.readme.io/docs/messaging On Wed, Jan 18, 2017 a

Re: Abandon of the non-throwing version of C++ client API

Hi Igniters, One point we need to consider with exceptions approach is that throwing exceptions across shared library borders has many implications. For example, compiler version compatibility between libs and clients, the way libstdc++ in Linux or CRT in Windows is linked and others. But still, I

Re: SecurityContext in Ignite

Hello, As you correctly noted, security features are part of GridGain. To deal with the null SecurityContext just create a new one inside WhiteListSecurityProcessor#authorize based on the information proper for your case. On Wed, Feb 1, 2017 at 2:49 PM, rick_tem [via Apache Ignite Users] < ml-nod

Re: SecurityContext in Ignite

Rick, Just follow JavaDoc for SecurityContext and implement it in the way that will work for the node where WhiteListSecurityProcessor is called with respect to your custom logic. On Wed, Feb 1, 2017 at 7:10 PM, rick_tem [via Apache Ignite Users] < ml-node+s70518n1035...@n6.nabble.com> wrote: >

Re: Apache Ignite's full config file...

Hi Abdul, If you mean Java IgniteConfiguration then it can be configured as a regular Spring bean, so there is no such thing as a complete Spring xml config. Still, you could refer to the official documentation and take a look at examples provided with sources for additional information. Kind reg

Re: Global lock - Cache

Hi Sérgio, Currently, there is no out-of-the-box way to do such a check, but you can send a closure to the primary node for the given key and check if it's locked there. On Tue, Feb 14, 2017 at 3:15 PM, perez_25 [via Apache Ignite Users] < ml-node+s70518n10630...@n6.nabble.com> wrote: > Hi, > >

Re: failed to start Grid Manager Adapter When using PutIgniteCache process in Apache Nifi

Hi, kindly provide the error log. On Fri, Mar 3, 2017 at 6:40 AM, whateversun [via Apache Ignite Users] < ml-node+s70518n1101...@n6.nabble.com> wrote: > I was trying to store data in Ignite using the PutIgniteCache processor in > Nifi. The flowfile content is in JSON and have been evaluated usin

Re: ScanQuery and Lock

Hi, Scan query will return the current actual value, it won't wait for the lock to be released. On Tue, Mar 14, 2017 at 9:56 AM, Anil [via Apache Ignite Users] < ml-node+s70518n11159...@n6.nabble.com> wrote: > HI, > > How does scan query and lock on same entry works ? > > thread 1 -> lock on a e

Re: Configuring Ignite Services to deploy on Server nodes only

If you want to get IgniteServices for only server nodes by using XML config, then, to my knowledge, I don't think it's feasible. Why do you want to configure it via XML? On Wed, Mar 15, 2017 at 12:48 PM, GB [via Apache Ignite Users] < ml-node+s70518n11189...@n6.nabble.com> wrote: > Hi, > > Below

Re: Cache Queues and Load Balancing

HI, For examples, take a look at https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/datastructures/IgniteQueueExample.java and https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/datastructu

Re: How to start rebalancing manually from management console

Hi, As for now, there is no such functional. I've created a ticket for this https://issues.apache.org/jira/browse/IGNITE-4835 You could track it or go ahead and contribute. On Fri, Mar 17, 2017 at 11:39 AM, ght230 [via Apache Ignite Users] < ml-node+s70518n11266...@n6.nabble.com> wrote: > For so

Re: Cache consistency on node failure

Hello, A part of a partitioned cache could be lost in a case when primary and backup nodes all go down. In this case, partitions will be rebalanced to the remaining nodes and these nodes will be able to load data from cache store. Regarding the second part of the question, you could listen for mis

Re: Very slow cache query compared to H2

Hi Zaid, Also, note that only the first run takes longer than following runs since a query has to be parsed. In my environment, running the query from a client takes about 500 ms at first run and about 250 ms at following runs. >From a server, it takes 80ms and 10ms correspondingly. When running th

Re: Ability to index keys in Java Map

Sorry, I didn't quite get your question. What I was talking about is: Having such a class public class Event implements Serializable { private Long timestamp; private String name; private Map data; } and having some finite and not very large set of keys , ... for the map, you coul

Re: A question about cluster configuration (Are there any way to make client connection faster?)

Hi, Specifying a port range leads to more ports to be scanned and checked, so the delay is bigger. But the whole time highly depends on many factors: cache config, network latencies, system load on nodes etc. Kind regards, Alex 3 апр. 2017 г. 9:08 PM пользователь "vdpyatkov [via Apache Ignite Us

Re: Slow on 1st time query "SQL Join"

Hello, That is an expected behavior. On the first run a query is parsed and metadata is built for it what takes some additional time compared to the following runs. Kind regards, Alex 10 апр. 2017 г. 8:13 AM пользователь "woo charles [via Apache Ignite Users]" написал: > Hi, > > I set up 3 Ser

Re: Ignite server showing this error class org.apache.ignite.IgniteCheckedException: Failed to send message (node may have left the grid or TCP connection cannot be established due to firewall issues)

Hi, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. Also, please elaborate a bit more on your use case. Do you sto

Re: Slow on 1st time query "SQL Join"

d = s.stock_id > and q.stock_id = XXX" is perform. > > And about 13s is needed for the first sql query. > > > 2017-04-10 14:53 GMT+08:00 Sergi Vladykin <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=11870&i=0>>: > >> I think 13s is still t

Re: Slow on 1st time query "SQL Join"

est 1 ---\ >> Name = QUERY_Quote_price_large_1000_Small_950 >> ActionType = QUERY >> Object class = com.performance.test.dao.Quote >> Thread Size = 80 >> MaxTime(First Time): 30 >> Thread [QUERY_Quote_price_large_1000_Small_950] Average Time: 118.75

Re: Slow on 1st time query "SQL Join"

est regards, Charles 2017-04-13 0:48 GMT+08:00 Sergi Vladykin <[hidden email] <http:///user/SendEmail.jtp?type=node&node=11922&i=0>>: > Alex, > > Why do we have such a huge difference between client nodes and server > nodes? Looks like we should fix it if possible. Even

Re: Slow on 1st time query "SQL Join"

e will > copy the selected table to local? > > If I set false to client mode, it will become server node and > start participate in caching, compute execution, stream processing, etc., > Then it will affect the performance of my client program. How can I > prevent this? > >

Re: Slow on 1st time query "SQL Join"

e in Jira. This behavior looks > suboptimal to me. > > Sergi > > 2017-04-13 15:12 GMT+03:00 afedotov <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=11942&i=0>>: > >> Charles, >> >> In your case, you have many caches register

Re: Slow on 1st time query "SQL Join"

eate a cache in > client node. > Is this cache permanent exist in client node or will drop after sometime? > > Thanks & Best regards, > Charles > > > 2017-04-13 21:09 GMT+08:00 afedotov <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=1202

Re: How to create class affinity?

Hello, Please refer to the corresponding documentation section https://apacheignite.readme.io/docs/affinity-collocation In short, for your case, just introduce a key class for ClassC like this: public class ClassCKey { private int id; // ClassB ID which will be used for affinity. @A

Re: How to create class affinity?

Since every key in cache is unique then every entity in the same cache is unambiguously idebtified by its key. If you need to have two ebtities with key 1, for example, then just create key class for each entity, for example Cache1Key and Cache2Key each with single int ID field. Kind regards, Alex

Re: Query search performance and scalability

That should be because of the overhead of network roundtrips between the client and the servers. Are servers and client located on the same physical machine? Please provide the query and cache config. Kind regards, Alex 4 мая 2017 г. 3:36 AM пользователь "waterg [via Apache Ignite Users]" < ml+s7

Re: Query search performance and scalability

ver. > For 2 server 1 client scenario, one server and client are on one server, > the other server node is on another server. > Working on a simplified code to reproduce the problem to share with you > > Jessie > > > On Wed, May 3, 2017 at 11:14 PM, afedotov <[hidden

Re: Cache Node Concept

Hi Abhishek. It's rather an Ignite node running a cache instance and each cache instance contains its part of overall cache data. Kind regards, Alex 5 мая 2017 г. 12:47 AM пользователь "abhishek jain [via Apache Ignite Users]" написал: Hi, Can we refer a cache instance running on a Ignite se

Re: Docker cluster set up

Hi. Did I get it right that containers reside on different hosts? If it's so then containers won't see each other out of box. You probably need to start them via docker overlay network or use Swarm. Kind regards, Alex 9 мая 2017 г. 12:29 AM пользователь "waterg [via Apache Ignite Users]" < ml+s70

Re: GroupBy with index is really slow.

Hi, Which Ignite version do you use? How many Ignite nodes do you run? What is your cache configuration? As well, could you please try the following query and see the performance? SELECT DISTINCT age FROM PersonWithindex; Kind regards, Alex. On Wed, May 10, 2017 at 5:57 PM, Guillermo Ortiz [vi

Re: GroupBy with index is really slow.

outIndex"."merge_scan" */] >>> *** >>> >>> public class PersonWithIndex implements Serializable { >>> @QuerySqlField(index = true) >>> public int id; >>> @QuerySqlField(index = true, orderedGroups = >

Re: Closures stuck in 2.0 when try to add an element into the queue.

Hi, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. Kind regards, Alex. On Wed, May 10, 2017 at 2:30 PM, fatality

Re: Docker cluster set up

Also, setting --net=host when running both of containers may probably help too. Kind regards, Alex. On Wed, May 10, 2017 at 8:28 PM, waterg [via Apache Ignite Users] < ml+s70518n12605...@n6.nabble.com> wrote: > Thank you Alex! > > On Wed, May 10, 2017 at 1:54 AM, afedotov

Re: How to deploy ignite service evenly across the cluster ?

Hi Danny. At the moment, cluster singleton services are deployed on a random basis. How many Ignite nodes do you run? How did you deploy services: after all the nodes had been started or you have the services specified in configuration? Kind regards, Alex. On Sat, May 13, 2017 at 1:06 AM, dany74

Re: How to deploy ignite service evenly across the cluster ?

with the same node attribute. > > We're looking for a different solution. > Question - is it possible to have an affinity key deployment strategy, but > not having the services "rebalance" when a node leaves / joins ? > Any other solutions ? > On Mon, May 15, 2017 at 10:

Re: Is it restricted by ignite to put elements into queue in closures

Well, actually the question was answered on stackoverflow with the following: It's not allowed to invoke ignite.queue and ignite.affinity methods in EventListener, because it may lead to d

Re: Closures stuck in 2.0 when try to add an element into the queue.

Hi. The question was answered on stackoverflow . Duplicating the answer below: It's not allowed to invoke ignite.queue and ignite.affinity methods in EventListener, because it may lead to

Re: Allow ALL nodes to keep working when a new node joins the cluster

Hi Gordon. Client joining the cluster should not cause the server nodes slowdown. Did you observe such behavior? If that's the case, kindly take a thread dump for the node that is affected by slowdown. Kind regards, Alex. On Fri, May 12, 2017 at 8:36 AM, gordon.reid@ninemilefinancial [via Apache

Re: How to deploy ignite service evenly across the cluster ?

r us (So that each Scheduler node would get 900 / 20 services ~), if > possible, because when services congregate in a particular node, it gets > overloaded and crashes > - Using affinity key is problematic because the cache could rebalance and > redeploy services with no real reason > &g

Re: Port Range in JDBC Discovery

Hi. Regarding hints on the configuring isolated clusters please take a look at the following https://apacheignite.readme.io/v2.0/docs/cluster-config# section-isolated-ignite-clusters-on-same-set-of-machines TcpDiscoveryJdbcIpFinder#registerAddresses will register the specified addresses in the un

Re: Persistent data store error

Hi. Looks like you are specifying value type instead of key type into loadCache ignite.cache("EmployeeCache").loadCache(*null*, Employee.*class*.getName(), "select * from DG.Employee"); Kindly try the following: ignite.cache("EmployeeCache").loadCache(*null*, EmployeeKey.*class* .getName(), "selec

Re: Port Range in JDBC Discovery

Hi. It's not supported out of box for TcpDiscoveryJdbcIpFinder. You could extend it and implement your own method similar to TcpDiscoveryVmIpFinder#setAddresses Kind regards, Alex. On Thu, May 25, 2017 at 10:42 PM, Swetad90 [via Apache Ignite Users] < ml+s70518n13150...@n6.nabble.com> wrote: >

Re: Unable to connect and load data from Oracle, using Ignite V2.0

Hello. Make sure you have a proper jar containing the driver on the classpath. The jar probably is something like ojdbc8.jar depending on the Oracle version you are using. Kind regards, Alex 26 мая 2017 г. 5:15 PM пользователь "Pratham Joshi [via Apache Ignite Users]" написал: I am trying to

Re: Unable to connect and load data from Oracle, using Ignite V2.0

e: > Thanks for your reply @afedotov. > I already have required jdbc jar file in my project's classpath. But still > the error occurs. > > -- > If you reply to this email, your message will be added to the discussion > below: > http://apac

Re: Cache.destroy() & close() does not delete SwapFile Ignite 2.0

Hi. As for now, there is no safe way to do it via the public API. Nevertheless, these files will be cleared after the Ignite node bounce. Kind regards, Alex. On Mon, May 29, 2017 at 6:27 PM, Ramzinator [via Apache Ignite Users] < ml+s70518n13205...@n6.nabble.com> wrote: > Hi all, > > I have a

Re: Affinity Collocation and missing data

Hi. Could you please share your Ignite configuration? As well, does running the query from code via SqlFieldsQuery give you the same results? Kind regards, Alex. On Tue, Jun 6, 2017 at 4:57 PM, woo charles [via Apache Ignite Users] < ml+s70518n13417...@n6.nabble.com> wrote: > hi, > I have tried

Re: Error occurs when calling IgniteRDD.savePairs()

Hello. >From the logs, I could suggest that some nodes are leaving or joining topology while the data is being loaded. That could be due to many reasons, be it GC or connectivity issues. Please share your Ignite config. As well you could monitor the cluster for GC via Web Console or check GC metri

Re: High heap on ignite client

Hi, Anil. Could you please share your full code (class/method) you are using to read data. Kind regards, Alex 12 июня 2017 г. 4:07 PM пользователь "Anil [via Apache Ignite Users]" < ml+s70518n13626...@n6.nabble.com> написал: > Do you have any advice on implementing large records export from ign

Re: Ignite-jdbc port

Hi. Which kind of connection URL do you use: jdbc:ignite:cfg://[@]< config_url> or jdbc:ignite://:/ ? Kind regards, Alex. On Thu, Jun 15, 2017 at 11:26 AM, ishan-jain [via Apache Ignite Users] < ml+s70518n13807...@n6.nabble.com> wrote: > how can i set my jdbc discovery port value in ignite conf

Re: Understanding peerclassloading

Hi, If I get your problem right you need either enable peer class loading on both the client and the server or make sure that all required class definitions are available on the classpath of the client. https://apacheignite.readme.io/v2.0/docs/deployment-modes#section-configuration Kind regards

Re: Ignite-jdbc port

gt;> ectorConfiguration().setPort(11212); >> >> On Thu, Jun 15, 2017 at 3:39 PM, afedotov <[hidden email] >> <http:///user/SendEmail.jtp?type=node&node=13815&i=1>> wrote: >> >>> Hi. >>> >>> Which kind of connection URL do you us

  1   2   >