Support User defined aggregate function ?

Hi Igniters, Can we support user defined aggreate function ? -- Thanks & Best Regards Tam, Nguyen Manh

Re: Support User defined aggregate function ?

Hi, Sorry for that I will move this to u...@ignite.apache.or. Thank you On Wed, Mar 20, 2019 at 8:45 PM Ilya Kasnacheev wrote: > Hello! > > As far as I know there is no such support. It is recommended to use > job/task API instead: > https://apacheignite.readme.io/docs/compute-tasks > >

Tomcat version for Web session clustering in Ignite 2.7

Hi, Can I know the tomcat version it supports for Web Session Clustering in Ignite 2.7. I see in the document it has mentioned that, it has tested in tomcat 6 and 7. Does it supports tomcat 8? [image: image.png] -- Biswajeet Rout DTIX , DELPHI O +18136176308 | M

Re: How to disable replication over multicast for development nodes?

Yes, you're right. If you wish to use specific port just add it to the value: 127.0.0.1:47500 or ports range, in case you're going to use multiple nodes in the cluster: 127.0.0.1:47500..47509 Regards, Igor -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite 2.7 Errors

Hello! We are tweaking this mechanism so maybe you will wish to reenable it in 2.8. Regards, -- Ilya Kasnacheev ср, 20 мар. 2019 г. в 18:30, Philip Wu : > Thank you, IIya! > > We ended up using > > cfg.setFailureHandler(new NoOpFailureHandler()); > > it silenced the errors and no more stack

Re: Access a cache loaded by DataStreamer with SQL

Hello! I think you need to have different types for keys too. Regards, -- Ilya Kasnacheev ср, 20 мар. 2019 г. в 21:00, Mike Needham : > I guess I am not understanding how to build this for multiple tables in a > cache that can be loaded using the datastreamer and are queryable from > DBeaver

Re: Licencing cost

Hi, Apache Ignite is always free for users without dependence on cores count or size of the cluster. Apache Ignite it is developed and supported by Apache Ignite Community, including users providing patches, enthusiasts and other individuals. Sincerely, Dmitriy Pavlov чт, 21 мар. 2019 г., 14:02

Caches have distinct sets of data nodes

Hi Igniters, Today i got this exception during testing cluster scaling. I have 2 caches X and Y in cluster, X is persistent and Y is none persistent. 1. I start 1st node A and activate cluster and populate data for X and Y 2. I start 2nd node B but not yet update topology. Few seconds later Y

Re: Blog post "Introduction to the Apache(R) Ignite™ community structure"

Sorry for the late reply. Contributors are not ranked so weight is not measured. The community always prefer to build consensus. If consensus is not reached (this happens time-to-time), then feature or change should not appear in the product. By the way, Apache PMCs may veto changes with a

Re: Tomcat version for Web session clustering in Ignite 2.7

Hello! Why don't you try, share results with us? Regards, -- Ilya Kasnacheev чт, 21 мар. 2019 г. в 13:08, Rout, Biswajeet : > Hi, > > Can I know the tomcat version it supports for Web Session Clustering in > Ignite 2.7. > I see in the document it has mentioned that, it has tested in tomcat 6

Re: Licencing cost

You should direct this question to GridGain rather than the Ignite open source community. Regards, Stephen > On 20 Mar 2019, at 16:11, austin solomon wrote: > > Hi, > > Does the gridgain licensing cost vary depending on the number of physical > cores of each node? > > Can anyone tell me. >

Re: Caches have distinct sets of data nodes

Hello! Ignite assumes that your data is affinity collocated. While rebalancing is in process, obviously this is not the case. I think you can have this problem go away by setting distributedJoins=true. Have you tried that? Note that there is a potentially large performance impact. Regards, --

Changing of eviction policies for a cache at runtime

Hi, Is it possible to change the eviction policies of a cache at runtime in Ignite? I came across wikipage : https://cwiki.apache.org/confluence/display/IGNITE/Allow+Configuration+Settings+Change+At+Runtime Is this implemented? or any plans for this? Thanks n Regards, Chalapathi.

Re: Ignite 2.7 Errors

Hello, Andrey - I see this: 2019-03-20 22:28:45,052 WARNING [FailureProcessor (tcp-disco-msg-worker-#2%XXXGrid%)] No deadlocked threads detected. is that what you mean? --- Also, prior to crash, I see this: not sure if it is related. 2019-03-20 22:28:45,029 ERROR [stderr (ActiveMQ

Re: Ignite 2.7 Errors

before that , there was: 2019-03-20 22:28:45,028 WARNING [G (tcp-disco-msg-worker-#2%XXXGrid%)] Thread [name="grid-nio-worker-tcp-comm-1-#73%XXXGrid%", id=415, state=RUNNABLE, blockCnt=0, waitCnt=0] -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite 2.7 Errors

Hello, Andrey - actually this is the sequence of events in time order: 2019-03-20 22:28:44,999 WARNING [IgniteKernal%XXXGrid (jvm-pause-detector-worker)] Possible too long JVM pause: 928937 milliseconds 2019-03-20 22:28:45,014 SEVERE [G (tcp-disco-msg-worker-#2%XXXGrid%)] Blocked system-critical

Re: Ignite 2.7 Errors

Hi, Philip! There should be a stacktrace of the blocked worker itself in the log, with warn level, before the message you cite, but after "Blocked system-critical thread has been detected." Could you please share that trace? It can help to understand failure cause. Best regards, Andrey

Re: Changing of eviction policies for a cache at runtime

Hello! Nope! Maybe in 3.0 or even later. You can't change cache at runtime, however you can do cache.withExpiryPolicy() when using that one. Regards, -- Ilya Kasnacheev чт, 21 мар. 2019 г. в 16:21, Venkata Bhagavatula : > Hi, > > Is it possible to change the eviction policies of a cache at

Re: Ignite 2.7 Errors

Hello! With NoOp handler this should be a purely cosmetic message. Regards, -- Ilya Kasnacheev чт, 21 мар. 2019 г. в 18:15, Philip Wu : > Thanks, llya! > > Actually it happened in PROD system again last night ... even with > NoOpFailureHandler. > > I am rolling back to Ignite 2.5 or 2.6 for

Re: Caches have distinct sets of data nodes

Hi, My data is affinity collocated. The issue is my 2nd node is not in a baseline yet. Persistent cache had not been re-balanced yet but non persistent cache had been done. Distributed join is not a good choice for us because of performance. I'm thinking about those solutions : 1. Don't sent

Re: Caches have distinct sets of data nodes

Hello! Please try and share with us. You can also experiment with node filters for non-persistent caches. We actually have plans to enable baseline for non-persistent caches but we're not there yet. Regards, -- Ilya Kasnacheev чт, 21 мар. 2019 г. в 19:08, Tâm Nguyễn Mạnh : > Hi, > > My data

Re: Ignite 2.7 Errors

Sorry, my mistake. I meant the last message you provided, but it doesn't contain stacktrace, only brief thread information. Anyway, 15 minutes long JVM pauses are suspicious. Do you have the same message on 2.5 or 2.6? Best regards, Andrey Kuznetsov. чт, 21 марта 2019, 19:49 Philip Wu

Re: Ignite 2.7 Errors

hello, Andrey - for your 2nd question, in Ignite 2.5, we have 15 mins + JVM paused as well, but no IgniteException, was working fine. 2019-03-15 19:08:46,088 WARNING [ (jvm-pause-detector-worker)] Possible too long JVM pause: 1001113 milliseconds. 2019-03-15 19:08:46,280 INFO

Re: Ignite 2.7 Errors

Thanks, llya! Actually it happened in PROD system again last night ... even with NoOpFailureHandler. I am rolling back to Ignite 2.5 or 2.6 for now. Thanks! 2019-03-20 22:28:45,044 SEVERE [ (tcp-disco-msg-worker-#2%XXXGrid%)] Critical system error detected. Will be handled accordingly to

Re: Can't add new key/value pair to existing cache via sql command

is there any timeline to release such limit? I have use ignite in production in my sub-system. it works so far so good, the only one exception is that every time I add new table I have to define a new cache. I think it's ok when the system is small. In fact I would like to use ignite in my another

Re: Ignite 2.7 Errors

Hello, Andrey - for your 1st question, I do have a straceTrace in other *FailureProcessor*.log Thread [name="tcp-disco-msg-worker-#2%XXXGrid%", id=445, state=RUNNABLE, blockCnt=0, waitCnt=320611] at sun.management.ThreadImpl.dumpThreads0(Native Method) at

Re: Can't add new key/value pair to existing cache via sql command

or can I log a feature ticket? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

infinite localhost to localhost connections

Hello! We have Apache ignite cluster v2.7 with Zookeeper discovery. After some time in the log on each node appeared these messages: [2019-03-21T22:48:35,536][INFO ][grid-nio-worker-tcp-comm-1-#25][TcpCommunicationSpi] Accepted incoming communication connection [locAddr=/127.0.0.1:47100,

Re: Ignite 2.7 Errors

Philip, if you can bear with so huge JVM pauses, then there is no use to investigate stacktraces anymore. Just increase systemWorkerBlockedTimeout parameter of IgniteConfiguration appropriately, as described in