Re: Using Java executor service inside Ignite transaction

Hi, My business case: A user can add multiple IPs to subscription to scan the assets. So the subscription can have N number of IPs. User can add IPs in following format: 10.10.10.10, 10.10.10.12-10.10.10.100, 10.10.10.102, 10.10.10.105-10.10.11.255 So the Subscription is top level entity. Then t

Re: Ignite clustering doubts

The documentation does explain it pretty well: https://apacheignite.readme.io/docs/affinity-collocation Den 2018-06-08 kl. 07:41, skrev the_palakkaran: Why do I want to map keys to partition ids? Can you tell me more, please? By keys, it means the keys used for the cache right? If so, particu

Re: Ignite Backup doubts

Hi, 1. By default get() will read backups if node, on which it's invoked is affinity node. In other words, if current node has backups, Ignite prefer to read local data from backup rather requesting primary node over network. This can be changed by setting CacheConfiguration.setReadFromBackup(fals

Re: Ignite benchmarking on K8s cluster

Hi, What's actually wrong with yardstick benchmarks? On Thu, May 24, 2018 at 10:34 AM, vbm wrote: > Hi, > > We are trying to use yardstick benchmark from gridgain > (https://www.gridgain.com/resources/benchmarks/running-gridgain-benchmarks > ). > These tests are mainly for a non K8s cluster. (

Node pause for no obvious reason

I setup a six node Ignite cluster to test the performance and stability. Here's my setup.

Failsafe re-entrant locks still held after a node exits.

Hi. I have been observing a problem on 2.5.0 where a node shuts down but locks held by it appear to still be held. Hopefully the attached demo code illustrates the issues (there is a detailed description in the files header comment). I have searched the archives and find similar bug reported bu

Re: Failsafe re-entrant locks still held after a node exits.

Hi, I've run your code several times and see no errors. On Fri, Jun 8, 2018 at 12:59 PM, Jon Tricker wrote: > Hi. I have been observing a problem on 2.5.0 where a node shuts down but > locks held by it appear to still be held. > > > > Hopefully the attached demo code illustrates the issues (the

Re: Ignite C# Geometry

Hi, Here is an example hot to create binary object [1]. I'm not sure it will work, but you can try to pass full class name as BinaroObject type. Smth like that: IBinaryObjectBuilder builder = ignite.GetBinary().GetBuilder("com.vividsolutions..."); [1] https://apacheignite-net.readme.io/docs/bi

Error while Starting Grid: javax.management.InstanceAlreadyExistsException: (LruEvictionPolicy)

Hi everyone, As a quick note on what we do here, we listen to NODE_FAILED, and NODE_SEGMENTED events and upon such events, we use Ignition.stopAll(true) and Ignition.start() to restart the Ignite grid in a given JVM. Here Ignite does not starts as a standalone process by itself, but bootstrap

Re: Node pause for no obvious reason

Hi, Looks like node was segmented due to long JVM pause. There are 2 "long JVM pause" messages in long an suspicious long checkpoint: Checkpoint finished [cpId=77cf2fa2-2a9f-48ea-bdeb-dda81b15dac1, pages=2050858, markPos=FileWALPointer [idx=2051, fileOff=38583904, len=15981], walSegmentsCleared=0

Re: Error while Starting Grid: javax.management.InstanceAlreadyExistsException: (LruEvictionPolicy)

Hi, Looks like a bug. Can you share grid configuration? Do you have more than one node in same JVM? Do you have configure cache groups manually? On Fri, Jun 8, 2018 at 4:48 PM, HEWA WIDANA GAMAGE, SUBASH < subash.hewawidanagam...@fmr.com> wrote: > Hi everyone, > > > > As a quick note on what we

Re: Node pause for no obvious reason

Possibly there is a race. I've created a ticket for this [1] [1] https://issues.apache.org/jira/browse/IGNITE-8751 On Fri, Jun 8, 2018 at 4:56 PM, Andrey Mashenkov wrote: > Hi, > > Looks like node was segmented due to long JVM pause. > There are 2 "long JVM pause" messages in long an suspiciou

RE: Error while Starting Grid: javax.management.InstanceAlreadyExistsException: (LruEvictionPolicy)

Hi Andrey, Thank you very much for the prompt response. We have only one node in a JVM. This is my grid config. We use 1.9.0 Ignite. IgniteConfiguration cfg = new IgniteConfiguration(); cfg.setPeerClassLoadingEnabled(false); cfg.setLifecycleBeans(new LogLifecycleBean()); TcpDiscoverySpi disc

Re: Ignite 2.5 | Can't restore memory - critical part of WAL archive is missing with walMode=NONE

Hi Emmanuel, Sorry for late answer. I've found I check your test against master branch and test passes, but it fails on 2.5 branch. It looks like already fixed. On Wed, Jun 6, 2018 at 3:47 PM, Emmanuel Marchand < emmanuel.march...@exensa.com> wrote: > I was wrong on the introduction of the excep

Re: How are SQL Queries executed on Ignite Cluster

1. It is not supported for now, but we plan do fix it [1] 2. Not yet. We split index different way. Every tree can manage certain partition numbers. Feel the difference. Mapping "partition -> tree segment" is static and we use as reminder of the division, like partition_id%N. Query works same way

RE: ClassCastException When Using CacheEntryProcessor in StreamVisitor

Static classes do not work either. Has anyone used CacheEntryProcessor in StreamVisitor? Does Ignite allow that? My requirement is to update certain fields of the Value in cache based on a data stream. I want to update only several fields in a large object. Do I have to get the whole Value obje

Re: Node pause for no obvious reason

Hi, Please see the GC log and the picture I attached. Looks like the GC is not taking a very long time. Yes, the checkpoint is taking a long time to finish. Could it be the checkpoint thread has something to do with the node crash? In my understanding, the checkpoint will not block other threads

Re: Failsafe re-entrant locks still held after a node exits.

Do you see the message "ERROR ; Lock is not released on exit" printed by the code? I believe if things are working correctly it should not be. From: Andrey Mashenkov Sent: 08 June 2018 14:40:19 To: user@ignite.apache.org Subject: Re: Failsafe re-entrant locks

Re: Ignite user create/modify trouble

Hi, Documentation should be updated as for me to describe how it designed in SQL. I will file the issue. When you use SQL and require to create the user like TesT then just use quotes. Without quotes, you will create TEST. In case if you are going to change the password for TesT user via SQL the

Re: Ignite user create/modify trouble

https://issues.apache.org/jira/browse/IGNITE-8756 -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Node pause for no obvious reason

Checkpoint can block other threads only if there another checkpoint should be started. But seems checkpoint is not the cause. It is hard to tell what was going on server. May be you have any dstat logs? How many nodes to you start per machine? Do you use docker or any VM? We have bad experience

Re: Failsafe re-entrant locks still held after a node exits.

No. I see no message. On Fri, Jun 8, 2018 at 7:27 PM, Jon Tricker wrote: > Do you see the message "ERROR ; Lock is not released on exit" printed by > the code? > > > I believe if things are working correctly it should not be. > > > -- > *From:* Andrey Mashenkov > *Se

Re: Failsafe re-entrant locks still held after a node exits.

OK. That's odd. I consistently get that message. Maybe differences in Java shutdown handling. Can you let me know which JDK and OS you are using. Thanks. From: Andrey Mashenkov Sent: 08 June 2018 17:53:24 To: user@ignite.apache.org Subject: Re: Failsafe re-entr

Re: Node pause for no obvious reason

I didn't have the dstat logs. But I think these charts is the same as dstats logs. CPU usage CPU.png Memory usage Memory.png Swap swap.png

Re: Ignite 2.5 nodes do not rejoin the cluster after restart (works on 2.4)

Hi, szj. Could it be that you run 2 different version of Ignite? You have mentioned that you used 2.4. Ignite nodes should be the same version. On Thu, Jun 7, 2018 at 8:36 PM, szj wrote: > Hi > > I'm afraid I wiped Ignite off my servers already as this behaviour was a > blocker to me. I only

Re: NPE from the native persistence enable node

Thank you Ilya, it worked! Em segunda-feira, 4 de junho de 2018 15:44:35 GMT-3, ilya.kasnacheev escreveu: Hello! Yes, you should be able to do that by specifying WITH "VALUE_TYPE=..." Look it up on readme.io: https://apacheignite-sql.readme.io/docs/create-table Regards, -- Sent f

DotNet version issue Invalid flag value: 0

Hello, I'm trying to run a sample with Apache Ignite 2.5. I'm using Visual Studio 2017, and NuGet to add ignite to my console project. I unchecked the "Prefer 32-bit" in the project properties. When running the project, I get the following error: An unhandled exception of type 'Apache.Ignite.Core

Re: Ignite 2.5 nodes do not rejoin the cluster after restart (works on 2.4)

No, I definitely started with 2.5. I only took the trouble to try it later with 2.4 to see that this problem did not exist there. 2.4 works fine in the very same scenario. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite user create/modify trouble

Vladimir, Taras, Please help to understand how to improve existing docs. Do you have any plans on addressing the documented and discussed limitations in regards the case sensitivity? -- Denis On Fri, Jun 8, 2018 at 9:48 AM, aealexsandrov wrote: > https://issues.apache.org/jira/browse/IGNITE-87