Re: JVM tuning parameters

If you have all tables colocated with each other, i.e. having the same affinity function and backups count then you can try using cache groups - https://apacheignite.readme.io/docs/cache-groups --Yakov пт, 29 мар. 2019 г. в 08:49, ashfaq : > We are testing and also the production data would be

Re: Triggering Rebalancing Programmatically get error while requesting

Ilya, have you had a chance to look into threaddumps? --Yakov ср, 27 мар. 2019 г. в 06:18, luongbd.hust : > Thank you for your enthusiasm > > I attached the logs for a longer time after the error occurred. > > logs.rar > > >

Re: Local node SEGMENTED error causing node goes down for no obvious reason

It seems there were issues with network. You can see plenty of discovery warnings in logs of the kind (231.log): [2018-11-07T07:44:44,627][WARN ][grid-timeout-worker-#119][TcpDiscoverySpi] Socket write has timed out (consider increasing 'IgniteConfiguration.failureDetectionTimeout' configuration

Re: JDK 11 support

Of course jdk 8 is fine :). I meant that ignite should also be fine with jdk9 and newer. Yakov

Re: JDK 11 support

Ignite 2.7 should run on JDK 11. Vladimir, Denis, correct me if I'm wrong. Please try this link for information - https://apacheignite.readme.io/v2.7/docs/getting-started#section-running-ignite-with-java-9 --Yakov

Re: destroy cache holding residual metadata in memory (2.7)

Wayne, can you please share a reproducer for this problem that can be launched from IDE? --Yakov

Re: destroy cache holding residual metadata in memory (2.7)

Wayne, can you please share a reproducer for this problem that can be launched from IDE? --Yakov

Re: Partition eviction failed, this can cause grid hang. (Caused by: java.lang.IllegalStateException: Failed to get page IO instance (page content is corrupted))

Hi! The upcoming 2.6 should fix the problem. It is under vote now. --Yakov

Re: [TcpCommunicationSpi] Close incoming connection, unknown node

Hi! >From this log [1] I see that local node (id=06b8bcb7) reported 18 node failed events 1 for server node and 17 for clients. Communication sub-system closes incoming connections from nodes that are not in topology. We need to understand: 1. Why this node failed? Probably it started

Re: C# client too slow to connect.

Hi, slow node join is possible on windows machines which is related to tcp/ip stack differences from linux - windows implementation waits for the entire timeout which is 3000ms by defaull and linux returns immediately with "connection refuse". Just narrow the range - 10.200.20.90:47500..47509,

Re: IgniteDataStreamer.flush() returns before all futures are completed

fy the comments for flush() to make this > behavior clear. > > -DH > > On Wed, Apr 25, 2018 at 5:43 PM, Yakov Zhdanov <yzhda...@apache.org> > wrote: > >> David, can you try adding all the futures to a collection and change >> assert condition to check that

Re: IgniteDataStreamer.flush() returns before all futures are completed

David, can you try adding all the futures to a collection and change assert condition to check that for all futures in that collection fut.isDone() is true? This should be a proper assertion. Please let me know if it works. Yakov Zhdanov чт, 26 апр. 2018 г., 0:30 David Harvey <d

Re: Upgrade from 2.1.0 to 2.4.0 resulting in error within transaction block

Cross posting to dev. Vladimir Ozerov, can you please take a look at NPE from query processor (see below - GridQueryProcessor.typeByValue(GridQueryProcessor.java:1901))? --Yakov 2018-03-29 0:19 GMT+03:00 smurphy : > Code works in Ignite 2.1.0. Upgrading to 2.4.0 produces

Re: ZooKeeper Based Discovery

Dmitry, there were few threads on dev list discussing new discovery SPI implementation. You can find current code in "ignite-zk" branch. The work is still in progress, but is mostly ready and will be merged to master soon. Documentation and algorithms descriptions are still on TODO list. Stay

Re: Runtime.availableProcessors() returns hardware's CPU count which is the issue with Ignite in Kubernetes

Ilya, agree. I like IGNITE_AVAILABLE_CPU more. Yakov Zhdanov, www.gridgain.com 2017-12-26 16:36 GMT+03:00 Ilya Lantukh <ilant...@gridgain.com>: > Hi Yakov, > > I think that property IGNITE_NODES_PER_HOST, as you suggested, would be > confusing, because users might wan

Re: Prohibit "Node is out of topology"

Lukas, what about GC pauses in your cluster? What is the max? What are network specs? Also, do you use bare metal servers or virtual machines? --Yakov

Re: Ignite 2.0.0 GridUnsafe unmonitor

+1 for warning about potential deadlock and improving javadocs --Yakov

Re: Fetched result use too much time

-considerations Thanks! -- Yakov Zhdanov, Director R *GridGain Systems* www.gridgain.com 2017-09-15 4:50 GMT+03:00 Lucky <wanxing...@163.com>: > Hi > I have a table with 25,000,000 records. > The sql like this: > select fdatabasedid from databasedassign where fassing

Re: Ignite cluster with persistent store enabled did not load from wal after restarting.

Guys, it seems that we have the same issue that was described in thread - Specifying location of persistent storage location I filed a ticket some time ago - https://issues.apache.org/jira/browse/IGNITE-6285, Alex G, can you take a look if this ticket makes sense? --Yakov

Re: Cannot start/stop cache within lock or transaction

I see that you call cache.clear() after acquiring explicit lock on key "fake". This cause cache clear to hang and this in turn prevents lock.unlock() call. Explicit lock also holds the exchange process. If I comment out cache.clear() test passes without deadlock. --Yakov

Re: Cannot start/stop cache within lock or transaction

Thanks, we'll take a look! --Yakov

Re: Cannot start/stop cache within lock or transaction

Naresh, The case you described should work. Can you please create a reproducer that I can run locally? I also filed this to make best effort to avoid deadlocks - https://issues.apache.org/jira/browse/IGNITE-6380 --Yakov

Re: Task management - MapReduce & ForkJoin performance penalty

Yes, however, you can still return results from each job and use it. Please see javadoc for org.apache.ignite.compute.ComputeJobResult#getData --Yakov

Re: Ignite node not stopping after segmentation

Thanks for the report. I think we need to file a ticket and start investigation. Can anyone from community pick this up? --Yakov

Re: Thread Pool Starvation in ignite grid

The local node you see this warning on cannot reach remote node for some reason which may be: GC pause or some network connectivity problem. Can you please tell what environment you use and check heap utilization on all nodes when this happens. --Yakov

Re: Task management - MapReduce & ForkJoin performance penalty

You are welcome! What are your timings now? --Yakov 2017-09-07 15:01 GMT+03:00 ihorps : > hi @yakov > > > yakov wrote > > Try attaching @ComputeTaskNoResultCache to your task. > > Thank you for the hint. It speeds up task management processing > drastically! > > > > -- >

Re: Misconfigured Ip6 address on node causes cluster outage on node join

Hi Kristian! Can you please provide the full stack trace? It seems IP finder assumes that unresolved addresses should be filtered out somewhere else. --Yakov

Re: Task management - MapReduce & ForkJoin performance penalty

Try attaching @ComputeTaskNoResultCache to your task. Also filed a ticket - https://issues.apache.org/jira/browse/IGNITE-6284 As far as 2 - I meant empty runnables submitted to an JDK thread pool executor - submission will require to acquire a lock and notify pool thread. So overhead is very

Re: ignite.active(true) blocking forever

> OutOfMemoryError is to shutdown the node that could not be activated. > > Best regards, > Slava. > > 2017-09-06 11:26 GMT+03:00 Yakov Zhdanov <yzhda...@apache.org>: > >> Slava, this looks like the issue with start cache operation throwing >> exception on some node

Re: Task management - MapReduce & ForkJoin performance penalty

Guys, I see the following issues with the benchmark: 1. There is only one iteration. I would put it in a loop and measure at least hundred of iterations. 2. no-op jobs are not real world example at all =) job requests are processed in thread pool executor which is not very much effective for

Re: ignite.active(true) blocking forever

Slava, this looks like the issue with start cache operation throwing exception on some nodes and cache start rollback. I remember you implemented that fix. Can we apply the same machinery to rollback the activation with proper exception? --Yakov

Re: Specifying location of persistent storage location

Raymond, I think most of Ignite users run on ipv4. So, issues with v6 in this case are hardly possible =) --Yakov

Re: Specifying location of persistent storage location

+ dev Pavel Tupitsin, can you please check that org.apache.ignite.configuration.IgniteConfiguration#setConsistentId has it platform counterpart? I could not find it. Raymond, you can explicitly set a bind address for Ignite with public string Localhost { get; set; }. This will make consistent ID

Re: Testing Ignite Applications Locally

>As far as Maven archetype, Yakov, is the only purpose of it to load a project, so users can add tests to it? Yes, but not just add. We will also be providing test examples, data loading application sample, shell scripts, etc. This can be pretty handy thing to create project with all dependencies

Re: Testing Ignite Applications Locally

Sergey, can you please elaborate? --Yakov 2017-08-26 23:51 GMT+03:00 Sergey Kozlov : > The idea is great! > > Also I would suggest an ability to run new (modified) tests 100 times in > loop on the CI server to make sure that they don't cause no sporadic > failures (we can

Testing Ignite Applications Locally

Guys, I want to discuss the subject again. It is pretty vivid that having wide set of local unit and simple integration tests most likely help to avoid many failures and bugs when going to server environment. I participated in many POC and I can say for sure - if developers are not implementing

Re: Possible starvation in striped pool. message

ot;f"));}); This should work fine for both transactional and atomic caches. Thanks! -- Yakov Zhdanov, Director R *GridGain Systems* www.gridgain.com 2017-08-09 16:30 GMT+03:00 kestas <kaln...@gmail.com>: > I did some testing on #invoke vs #get performance. It works as expected o

Re: Apache Ignite Site Changed its Face

I like the new design. Looks good! --Yakov

Re: About Apache Ignite in Japanese

Wow! Very cool! Great job, Roman! --Yakov

Re: Read-through cache performance

Any reason why you left expiry policy? --Yakov

Re: Read-through cache performance

Pascal, Why do you have expiry policy in one run and do not have it in another? Please remove it and rerun your test. Also, can you please wrap your loop in another loop and take 60 measurements in a row. --Yakov

Re: Fetch column names in sql query results

Megha, this will be available in 2.1. You can see the ticket for details - https://issues.apache.org/jira/browse/IGNITE-5252 --Yakov

Re: Transaction Boundary - Data Streamer

2017-06-26 15:27 GMT+03:00 fatality : > Hi > > We have also implemented a generic receiver as > TimestampBasedUpdateStreamReceiver and also > AbstractTransactionalStreamReceiver. I send you the source code if you > want > and maybe can be added to the ignite source code.

Re: Transaction Boundary - Data Streamer

2017-06-26 13:28 GMT+03:00 Yakov Zhdanov <yzhda...@gridgain.com>: > >>If you need transactional in your operations, you can use > optimistic transactions by implementing and registering a > receiver into your datastreamer as explained here > > >> https://apachei

Re: Transaction Boundary - Data Streamer

>>If you need transactional in your operations, you can use optimistic transactions by implementing and registering a receiver into your datastreamer as explained here >> https://apacheignite.readme.io/docs/transactions#deadlock- free-transactions >> and for datastreamer here

Re: Why is custom cacheStore.write() being called in clientMode?

In Ignite terminology near node is the node that coordinates transaction or cache update. As far as store initialization you can implement org.apache.ignite.lifecycle.LifecycleAware on your store and inject Ignite instance to your store with org.apache.ignite.resources.IgniteInstanceResource

Re: Why is custom cacheStore.write() being called in clientMode?

In order to commit DB transaction consistently with in-memory one it is committed from near node (which is client node in your case). Currently we don't have an option to write-through from dht nodes, but for now you can try write behind functionality -

Re: CacheWriteSynchronizationMode

Reid, I don't think you can ensure that local node is primary for all updates. In theory you can implement affinity function having only 1 primary node for all partitions, but once you initiate replicated cache update from another node then primary node becomes remote. As far as LOCAL_SYNC - I

Re: How to return ID of Ignite task to stop this task in the future?

Couple of questions to Igniters (cross-posting to dev list). 1. Why IgniteCompute does not return ComputeTaskFuture from all methods? 2. In GridGain 6.x and earlier there was a method GridComputeImpl#cancelTask(GridUuid sesId) -

Re: 10X decrease in performance with Ignite 2.0.0

Chris, any news? --Yakov 2017-05-13 1:05 GMT+03:00 Denis Magda : > Chris, > > These are some links for reference: > > 1. BinaryObject and BinaryObjectBuilder interfaces usage: > https://apacheignite.readme.io/docs/binary-marshaller# > section-binaryobject-cache-api >

Re: 10X decrease in performance with Ignite 2.0.0

I think it will also be useful to switch to offheap tiered (cacheConfig.setMemoryMode()) in 1.9 and compare results again. --Yakov 2017-05-12 11:30 GMT+03:00 Alexey Goncharuk : > Hi Chris, > > One of the most significant changes made in 2.0 was moving to an off-heap

Re: 10X decrease in performance with Ignite 2.0.0

Absolutely agree here. I think if we can add getAll() benchmark and run it with batch sizes of 5 and 10. Thanks! -- Yakov Zhdanov, Director R *GridGain Systems* www.gridgain.com 2017-05-12 10:48 GMT+03:00 Sergi Vladykin <sergi.vlady...@gmail.com>: > According to our benchmarks I

Re: 10X decrease in performance with Ignite 2.0.0

Cross-posting to devlist. --Yakov

Re: 10X decrease in performance with Ignite 2.0.0

Yakov Zhdanov <yzhda...@apache.org>: > How many values are in your cache? > > SLB? What is it? > > >Will there be any difference between 1.9 and 2.0 if you send the same > >number of empty jobs? > >None. Exact same code > . > I want you to check if compu

Re: 10X decrease in performance with Ignite 2.0.0

How many values are in your cache? SLB? What is it? >Will there be any difference between 1.9 and 2.0 if you send the same >number of empty jobs? >None. Exact same code . I want you to check if compute engine became slower in your deployment. If you comment out all lookups inside the job and run

Re: 10X decrease in performance with Ignite 2.0.0

Chris, that's very surprising. Let's get to the bottom of it. 1. You have 10 nodes with 4 partitioned caches each configured with 2 backups. There are no updates to the caches. Correct? 2. Are caches atomic or transactional? 3. 5 nodes send compute jobs to the topology of 10 nodes. Correct? 4.

Re: Cache write behind optimization

Tolga, this looks like you do cache.get() and key resides on remote node. So, yes, local node waits for response from remote node. --Yakov 2017-02-21 10:23 GMT+03:00 Tolga Kavukcu : > Hi Val,Everyone > > I am able to overcome with write behind issue and can process

Re: Asynchronous jobs (not the scheduling)

Sergei, Vlad, I think you also might be interested in compute continuations since the result of async execution may be sufficient for the job itself. Please see ComputeFibonacciContinuationExample under ignite/examples. --Yakov

Re: Timed out waiting for message delivery receipt

Very good! Please keep us up to date. --Yakov 2017-01-24 9:30 GMT+03:00 hitendrapratap < hitendrapratapsingh.si...@target.com>: > I has been resolved when increased "ignite.failure.detection.timeout" to > 60sec from 10sec. > > > > -- > View this message in context: http://apache-ignite-users. >

Re: Locking behavior

This is the trace of the waiting thread. This means there is some thread in the cluster that holds the lock. Is it possible to determine which one and on which jvm and why this lock has not been released. > We did not use transactions because we did not want to have to handle the condition of

Re: Trigger query in ignite

You can also use jdk timers. --Yakov 2017-01-06 13:15 GMT+03:00 rishi007bansod : > Is there any way we can trigger query at some fixed time interval in > ignite(So that query is written only single time initially and it gets > called at defined time interval). Is there

Re: Efficient way to get partial data of a cache entry

I would suggest calling cache.invoke() and return needed result without altering the entry. Or compute.affinityCall() and do local get inside callable and computing and returning the result.

Re: Make changes to cache entry before data rebalanicng.

Igor, it is impossible to alter the value since it may cause data inconsistency. Imagine you have 2 nodes and cache with 1 backup. 3 node joins and you alter cache entries being sent from node 1 and 2 to 3, but those entries are currently backed up on 2 and 1 respectively. Please explain why you

Re: Not able to join cluster with Zookeeper based IP finder

Nikolay, can you please join this thread and point out how to build cluster using docker? --Yakov 2016-12-10 5:48 GMT+07:00 ghughal : > Yakov - I'll try to see if I can remove AddressResolver. The main reason > for > adding it was because we are running it inside docker

Re: AtomicSequence not performing well with 2 nodes cluster set up

GB, I am not sure if you see any difference since you will be updating the same cache entry which does not scale much. Sequence and IgniteAtomicLong work exactly in the same way. --Yakov 2016-12-08 22:15 GMT+07:00 GB : > Hi, > What if we create an ignite cache having

Re: Not able to join cluster with Zookeeper based IP finder

, then remove it, since it is misuse. Ignite automatically picks unused port and propagates this info to the rest of the cluster. Thanks! -- Yakov Zhdanov, Director R *GridGain Systems* www.gridgain.com 2016-12-08 5:03 GMT+07:00 ghughal <bakul.ghug...@gmail.com>: > Yakov, > > We

Re: Update a column of cache entities - Ignite 1.7

You can send IgniteCompute.affinityCall() to the primary node that holds the partition you are interested in. Inside the closure you can have iteration and invoke() calls that will be local to the primary copy. If you need to process the entire cache data set then send as many affinityCall's as

Re: Not able to join cluster with Zookeeper based IP finder

for some reason these two nodes register themselves with incorrect addresses or, to be more exact, incorrect ports - 47101 instead of 47500. Then they both get 2 addresses (1st is own address, 2nd is address for remote node) but cannot connect to them since port is incorrect. 2016-12-06

Re: Performance question

I think it is a bad idea to set number of threads greater than CPU count given you do not block on any IO operations However, benchmark itself seems totally incorrect to me. The most important issues are 1. total time is too low. try to put it to a loop body and measure each iterations. you can

Re: Threads got stuck

from one server and wait the > data to be replicated to others. Can that cause such a situation, too? > > On Tue, Oct 25, 2016 at 11:14 AM, Yakov Zhdanov <yzhda...@apache.org> > wrote: > >> Alper, >> >> There can be multiple reasons. >> >> C

Re: Threads got stuck

Alper, There can be multiple reasons. Can you please reproduce the issue one more time, collect and share the following with us: 1. collect all the logs from all the nodes - clients and servers 2. take threaddumps of all JVMs (from all nodes) with jstack -l --Yakov 2016-10-25 10:49 GMT+03:00

Re: Some problems in test case which comparing sql query performance between Ignite and Oracle

Bob, can you please also tell what is your benchmark scenario? Do you have enough warm-up cycles to bring your app to some steady state? --Yakov 2016-10-20 12:40 GMT+03:00 Vladislav Pyatkov : > Hi Bob, > > One way to do SQL faster this is adding indexes. > 1) I do not

Ignite service for redhat/centos

Hello Igniters! As far as I know many of Ignite deployments run under rhel & centos I think it would be very convenient to include sample service configuration and service installation instructions to our distribution. Here is the link to redhat documentation.

Re: java.util.concurrent.CompletionService implementation

Why don't use JDK provided service? ExecutorCompletionService service = new ExecutorCompletionService(dr1Hub.executorService()); --Yakov 2016-10-07 15:50 GMT+03:00 mnadeem : > Appreciate if java.util.concurrent.CompletionService implementation is > provided as in

Re: Javadoc at GridGain website is at version 1.6 instead of 1.7.1

Hi Kenan! I reached 1.7.0 API docs from ignite.apache.org site. Thanks for letting us know anyway. --Yakov 2016-09-15 19:14 GMT+03:00 Kenan Dalley : > The Javadoc link at the GridGain website hasn't been updated to the latest > release of 1.7.1 and is still referring back

Re: Ignite performance

; > > >@Override > >public void runTest() { > > this.cache.query(query).getAll(); > >} > > } > > > > Ignite configuration: > > class="org.apache.ignite.configuration.IgniteConfiguration"> > > > > > > > > > > > > c

Re: Ignite performance

Manuel, The numbers you are seeing are pretty strange to me. Is it correct that you run your query in a loop giving enough time for the whole cluster to warmup and only then take the final measurements? I also do not understand why CPU load is 400% which may be interpreted as full (correct?).

Re: Deadlock during Client Continuous Query deserialization

Ross, Deserialization may be heavy. When you deserialize object Ignite implicitly goes to some internal caches to get metadata of the type. This explains why your example works when you skip deserialization. I am not sure whether 2000 is a lot or not. For me even 1 cont query bringing all the

Re: Deadlock during Client Continuous Query deserialization

Guys, here are my comments. As far as ticket filed by Sam. If reads are paused at some point they should get unpaused when incoming message queue gets shorter. The issues's description makes me think that Ross has very heavy logic in the listener, so notification processing takes too long. Ross,

Re: How to troubleshoot a slow client node get()

I see these possible reasons of the delay 1. GC pause on client or server. Please enable GC logging and rerun test. 2. your machine runs out of resources - CPU, memory, disk IO, etc. Can you please check that there are enough resources in the system? 3. Is any energy saving stuff enabled? I also

Re: DataStreamer performance question

Case of 1 client and 1 server should be about 2 times slower than 2 servers, since in the second case 50% of keys belong to local node and there is no need to send them over network. In the first case 100% keys and values go over network. 1. I would think you are running out of memory on server

Re: How to troubleshoot a slow client node get()

Tracel, can you please also take threaddumps of both client and server JVMs when you see that get() takes too long? --Yakov 2016-07-13 12:33 GMT+03:00 tracel : > Thanks yakov, > I am using a Linux box. > The delay can also be observed after leaving client idle for

Re: How to troubleshoot a slow client node get()

What OS do do you use? Is this delay observed only initially or can also be observed after leaving client idle after doing some work? Can you please disable shared memory communication in case you use Linux or Mac - set

Re: Data Nucleus plugin extensions aren't loaded by the grid class loader

Thank you for your interest to the project! Unfortunately, I have no idea what is wrong with your case. Can you please share logs from all Ignite nodes so I can get minimal idea on what is going on? Do you see exceptions in logs? --Yakov 2016-05-13 14:12 GMT+06:00 georgeg

Re: jpoint presentation

an > > > > On Tuesday, May 10, 2016 3:56 PM, Yakov Zhdanov <yzhda...@gridgain.com> > wrote: > > > Nick, I am not sure if apache lists allow attachments. So, I will send you > personal email. > > > Thanks! > -- > Yakov Zhdanov, Director R > *GridGai

Re: jpoint presentation

Nick, I am not sure if apache lists allow attachments. So, I will send you personal email. Thanks! -- Yakov Zhdanov, Director R *GridGain Systems* www.gridgain.com 2016-05-05 13:52 GMT+06:00 Nick Pavlov <gurind...@gmail.com>: > Hi Yakov, > > Could you share your presentation from jpoint? >

Ignite Reentrant Lock

Guys, Vlad Jelisavcic has implemented Ignite reentrant lock ( https://issues.apache.org/jira/browse/IGNITE-642). I have finally reviewed and merged it today. Vlad, thank you for your efforts! I look forward to next contribution from you! I have removed origin/ignite-642 branch. Please close PR

Re: ODBC Driver?

It is possible. I think we can send 1.6 for vote as soon as odbc driver gets finished. --Yakov 2016-04-27 13:51 GMT+03:00 Tomek W : > Does it mean that in next week ODBC driver will be available ? > > 2016-04-27 5:41 GMT+02:00 arthi :

Re: Behavior of init() for clustered singleton

Please provide app logs after the issue gets reproduced. --Yakov 2016-04-08 19:20 GMT+03:00 dstieglitz : > Ok I added the debug statements: > > > https://github.com/dstieglitz/grails-ignite/blob/v0.4.x/src/java/org/grails/ignite/DistributedSchedulerServiceImpl.java

Re: Easy way to determine a node has been segmented

You can subscribe to event - org.apache.ignite.events.EventType#EVT_NODE_SEGMENTED with org.apache.ignite.IgniteEvents#localListen and take action inside listener. Please note that listener is called in sensitive internal system thread, so make sure to move all complex and blocking processing to

Re: Behavior of init() for clustered singleton

Your examples seems correct to me. 1. What does it mean by "goes null"? 2. I do not see any assignments other than instantiation in init() method. 3. You confirm that service worked OK on some node but after some time with no topology changes it starts to throw NPE, correct? Can you please share

Re: How to solve the 22 parameters' limit under scala 2.10 in the case class?

Thanks for sharing the code. Alex Goncharuk, can you please take a look? --Yakov

Re: Messaging Reliability

message, an IgniteException is > thrown? > And what happens if a new node is joining the cluster while a message is > being sent? > > If it makes sense, I could create a pull request to add this information > to the javadoc? > > Philipp > > -- >

Re: Messaging Reliability

Philipp, Messaging works on top of Ignite internal communication sub-system. Message delivery is guaranteed, unless recipient node has not left the grid. If it leaves (i.e. topology gets EVT_NODE_LEFT or EVT_NODE_FAILED), then sender clears internal queue associated with left node. When node

Re: How to solve the 22 parameters' limit under scala 2.10 in the case class?

Hi! Can you please provide the code you are trying to execute and full logs of execution. Seems that IgniteContext was not properly initialized. -- Yakov

Re: SqlQuery Error

There is an issue in your query entity configuration. After I changed it (see below) sql query and fields query started to work. fields.put("id", "java.lang.String"); fields.put("attribute1", "java.lang.String"); fields.put("attribute2", "java.lang.String"); fields.put("attribute3",

Re: SqlQuery Error

Can you please share the reproducible example or junit we can run locally to reproduce? --Yakov 2016-03-24 11:48 GMT+03:00 16616...@qq.com <16616...@qq.com>: > Thanks for your reply. But my attributer id is String. > > The code is: > > /* > * Licensed to the Apache Software Foundation (ASF)

Re: SqlQuery Error

It seems the type of your id field is integer, but parameter type is string. Can you check it? Please also see if this helps - https://groups.google.com/forum/#!topic/h2-database/fiUw3tqRb1o --Yakov 2016-03-24 11:33 GMT+03:00 16616...@qq.com <16616...@qq.com>: > hi experts, > > I can invoke

Re: Semaphore blocking on tryAcquire() while holding a cache-lock

Vlad, did you have a chance to review my latest comments? Thanks! -- Yakov Zhdanov, Director R *GridGain Systems* www.gridgain.com 2016-03-06 12:21 GMT+03:00 Yakov Zhdanov <yzhda...@apache.org>: > Vlad and all (esp Val and Anton V.), > > I reviewed the PR. My comments ar

Re: How can I achieve performance

Datastreamer does not have order guarantees, it guarantees that all data added by addData() calls is stored on closing or flushing data streamer. Can you please take a look at this - https://apacheignite.readme.io/docs/messaging#section-ordered-messages - and tell me if this works for you.

  1   2   >