Re: the balance between read and write.

with which exception? 2017-12-02 9:56 GMT+03:00 Marco : > the question is about the scalablities and flexabilities of the framework > for > realtime data processing and reporting. I tried single node ignite 2.3, it > simply crashed when 100 concurrent quries were applied

Re: read/persist a huge cache by its affinity key

k, tks -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: the balance between read and write.

the question is about the scalablities and flexabilities of the framework for realtime data processing and reporting. I tried single node ignite 2.3, it simply crashed when 100 concurrent quries were applied throuth servicepool, the result is even worser than ignite 1.5 which at least supports

RE: Does the Ignite C# client support distributed queues?

Hi Alexey, I think I need to be logged-in to vote for it. How do I get a credential to do that? Can you speak to my second question regards the plan for functional equivalence between C# & Java clients? Thanks, Raymond. *From:* Alexey Popov [mailto:tank2.a...@gmail.com] *Sent:*

Re: SQL Count(*) returns incorrect count

Yes, that worked for me. I guess this will be fixed in version 2.4. Final version of JavaIgniteContext construction looks like: JavaIgniteContext igniteContext = new JavaIgniteContext<>(jctx, () -> { IgniteConfiguration cfg = null; try {

Re: Web Console on Kubernetes Cluster

I don't understand. What has that got to do with agents? My app pods are connecting to server ignite pod and that part is working. But now I need to connect web console. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Semaphore Stuck when no acquirers to assign permit

Hey all, We experienced an issue when trying to establish a semaphore after a single instanced client node goes down hard (kill -9). Which afterwards we cannot acquire a permit on the existing semaphore. However, if the client is redundant, the permit is transferred successfully. I created a

RE: Does the Ignite C# client support distributed queues?

Hi Raymond, You are right, distributed queues require changes at Ignite core. https://issues.apache.org/jira/browse/IGNITE-2701 It was created almost 1 year ago. Please vote for this feature. As far as I know there is no plan/schedule for it. Thank you, Alexey From: Raymond Wilson Sent:

Re: the balance between read and write.

I don't understand how it will work in your case if you will have 2 separate clusters. I think you can just add more machines to the cluster and this problem will be resolved. Evgenii 2017-12-01 18:35 GMT+03:00 Marco : > is that worthy a try that initate 2 ignite

Re: read/persist a huge cache by its affinity key

Well, then you can start other Ignite cluster with enabled persistence and move data from the first cluster to the second one. Evgenii 2017-12-01 18:31 GMT+03:00 Marco : > yes, that way works, but the question is how to output 30m out without > restart? I didn't enable

Re: the balance between read and write.

is that worthy a try that initate 2 ignite clusters, 1 for partition writting another one for isolated reading? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: read/persist a huge cache by its affinity key

yes, that way works, but the question is how to output 30m out without restart? I didn't enable persistence. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Regards the ContinuousQuery and MutableCacheEntryListenerConfiguration

Hi Aaron! You close ContinuousQuery on this line: try (QueryCursor> cur = accountCache.query(query)) { When you call *QueryCursor#close()* method this listener stops receiving updates. Just remove `*try*` and it will work as you expected. On Wed, Nov 29, 2017

Re: Java's DelayQueue as distributed data structure?

Hi Teun, Yes, you can file JIRA ticket here https://issues.apache.org/jira/projects/IGNITE And of course, feel free to contribute! :) Thanks, Slava. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

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: Two persistent data stores for a single Ignite cluster - RDBMS and Ignite native

Hi Naveen, Yes, you are right. Apache Ignite does not provide that functionality out of the box. However, it can be implemented. Please check this article: https://dzone.com/articles/syncing-a-gridgain-in-memory-computing-cluster-and Thanks! -- Sent from:

Re: Error running ignite in YARN

Hello once more! I have prepared a patch. I think it won't be hard for you to try it out since you are accustomized to building Ignite. Please try it, tell if it solves the current issue. ignite-7080.patch I was

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,

Re: Out of memory error

Hi Dmitriy, Looks like you configured memory policy and memory configuration that are not used by your caches. Also, it looks like your cache use default memory configuration, try to add to the memoryConfiguration and to the memoryPolicy configuration Evgenii 2017-12-01 16:42 GMT+03:00 Alexey

Re: Out of memory error

Hi, You identified the problem right: there is not enough memory to handle 15G of Postgres data on your server. Your idea to configure a memory policy to increase available memory is right but 16G is also not enough. Ignite data size is noticeably larger (up to 3 times, depends on many factors

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

Lucky, How much data do you retrieve in this query? There is some overhead, caused by network communication, when you are using JDBC drivers, but it's not expected to be so big. Also do you connect over JDBC to the same node, on which you test IgniteCache#query() ? Denis чт, 30 нояб. 2017 г. в

Re: How to provide a dependency to a custom CacheStoreAdapter

Hello Matt! I imagine you can have a custom CacheStore factory (implementing Factory>) that will create (or otherwise obtain) the dependency, and then supply it to every subsequent CacheStoreAdapter it creates. Then you will pass the same CacheStoreFactory in configuration of

Re: Can Ignite native persistence used with 3rd party persistence?

Hi Ray, > One more question here, how can a update or new inserts back-propagate to > Ignite when another application(not ignite) writes to persistence(hbase)? It is not supported. On Fri, Dec 1, 2017 at 12:08 PM, Ray wrote: >

RE: Rest API not working for GET

I have another case where REST APi is not working. Here is the use case. I am using 2.3, have 4 nodes running as server and one node running as client and rest api is exposed only in the client. I was trying to access the client node which is exposing the rest API Rest API does not seems to

Re: read/persist a huge cache by its affinity key

Hi Marco, Why don't you want to use an Ignite persistence: https://apacheignite.readme.io/docs/distributed-persistent-store or at least Cache Store for a 3rd party DB: https://apacheignite.readme.io/docs/3rd-party-store ? By using Ignite persistence you will get everything you want here without

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

Re: Socket Reader Timeout on ClientImpl

Hello Tolga! First of all, Ignite has two kinds of connections: Discovery connections and Communication connections. Discovery connections form a ring and make sure node requires topology updates, Communication connections established between nodes and are used to pass data. ClientImpl should

Re: Two persistent data stores for a single Ignite cluster - RDBMS and Ignite native

Hi Slava, Thanks for the reply, I have the same doubt. One more question here, how can a update or new inserts back-propagate to Ignite when another application(not ignite) writes to 3rd party persistence? For example, Ignite and 3rd party persistence both have one entry for now. When

Re: Can Ignite native persistence used with 3rd party persistence?

http://apache-ignite-users.70518.x6.nabble.com/Two-persistent-data-stores-for-a-single-Ignite-cluster-RDBMS-and-Ignite-native-td18463.html Found a similar case here, I think I'll try Slava's suggestions first. One more question here, how can a update or new inserts back-propagate to Ignite when

Re: the balance between read and write.

Hi Marco, First of all, I would suggest updating to the latest Ignite version - 2.3, it will definitely show much better performance and it's more stable. As for the question about write - yes, it's better to use Ignite data streamer if you need to write a lot of new entries in the cache.