Re: Cannot start ignite nodes with shared memory - Ignite version 2.10.0

Hello. It looks like a bug. I have reported it: https://issues.apache.org/jira/browse/IGNITE-14634 Ilya пт, 16 апр. 2021 г. в 05:09, sarahsamji : > Sample > > import org.apache.ignite.Ignite; > import org.apache.ignite.Ignition; > import org.apache.ignite.configuration.*; > import

Re: Too many TCP discovery accepted incoming connections

HI Ilya, Please find attached full log file. Regards, Gangaiah server_log.zip -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: [2.9.1] Custom failure handler is not being invoked

Hello, There is no way to configure a custom failure handler for segmentation error, you can only choose from 3 available variants bounded to segmentation policy (Use IgniteConfiguration.setSegmentationPolicy to change policy) чт, 22 апр. 2021 г. в 17:10, ashishg : > Hi, > > I have set the

Re: AccessControlException

Hello! I guess this is what JVM creates for us. If you expect that Ignite would have dedicated support for security policy: it doesn't. Regards, -- Ilya Kasnacheev чт, 22 апр. 2021 г. в 16:58, Nico : > More info: it looks like the threads that are created are of type >

Re: Too many TCP discovery accepted incoming connections

Hello! I can see that a node has just joined, but I'm not sure why there are all those messages. However, the log file seems truncated. Can you provide the rest? Regards, -- Ilya Kasnacheev чт, 22 апр. 2021 г. в 16:47, Gangaiah Gundeboina : > Hi Ilya, > > There is no jvm pause, only one

Re: Too many TCP discovery accepted incoming connections

Hi Ilya, There is no jvm pause, only one entry in the server log but that too after affect. The incoming connections started at 2021-04-21T14:52:50,035 and jvm pause could see at 2021-04-21T14:54:18. I have attached logs file, could you please check. [2021-04-21T14:54:18,035][WARN

Re: AccessControlException

Hello! Obviously, you need to grant to all Ignite code permission to read any system properties. Obviously, granting all permissions didn't work in your case. I'm not sure why. Regards, -- Ilya Kasnacheev чт, 22 апр. 2021 г. в 14:33, Nico : > Hi, > > I'm using Ignite in embedded mode,

RE: [External]Re: Cluster becomes unresponsive if multiple clients join at a time

Thanks Ilya! I have observed PME related log entries in latest version as well. Does this mean these ‘some conditions’ are not met? Can you elaborate on this please ? Thanks and Regards, Kamlesh Joshi From: Ilya Kasnacheev Sent: 22 April 2021 16:24 To: user@ignite.apache.org Subject: Re:

[2.9.1] Custom failure handler is not being invoked

Hi, I have set the custom failure handler using the IgniteConfiguration: IgniteConfiguration cfg = new IgniteConfiguration(); GeDistributedCacheFailureHandler failureHandler = new GeDistributedCacheFailureHandler(); failureHandler.setIgnoredFailureTypes(Collections.EMPTY_SET);

Re: AccessControlException

More info: it looks like the threads that are created are of type InnocuousForkJoinWorkerThread, which means without permissions. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Too many TCP discovery accepted incoming connections

Hello! Can you share complete logs from that node? You can also search them for "JVM pause" messages or just for any reason why these connections were closed in the first place. Regards, -- Ilya Kasnacheev чт, 22 апр. 2021 г. в 14:39, Gangaiah Gundeboina : > Hi Igniters, > > Some times we

Too many TCP discovery accepted incoming connections

Hi Igniters, Some times we are seeing too many 'tcp discovery accepted incoming connections' from client servers in server logs. Is it due to network glitch or connectivity break between servers and clients?. This leads to system critical errors and many clients disconnected and reconnected.

AccessControlException

Hi, I'm using Ignite in embedded mode, ignite sandbox is off. I'm getting the following exception: Caused by: java.security.AccessControlException: access denied ("java.util.PropertyPermission" "IGNITE_DEFAULT_DISK_PAGE_COMPRESSION" "read") at

Re: [External]Re: Cluster becomes unresponsive if multiple clients join at a time

Hello! Yes, it should no longer be blocking assuming some conditions are met. Regards, -- Ilya Kasnacheev чт, 22 апр. 2021 г. в 08:26, Kamlesh Joshi : > Hi Ilya, > > > > Yeah even that’s what we were suspecting, PME triggering might be causing > issue. We are using 2.7.6 version. > > So you

Re: Buffer Overflow on ARM with persistency enabled

Hello! You can also configure your system to save core dumps on application crash, then you can open the core dump with debugger. Regards, -- Ilya Kasnacheev чт, 22 апр. 2021 г. в 07:07, rakshita04 : > Hi , > > We have 2 GB RAM. > we unfortunately could not attached debugger, so we don't

Re: [ANNOUNCE] Apache IGNITE python thin client (pyignite) 0.4.0 released

You might like to open a ticket on issues.apache.org. Regards, Stephen > On 22 Apr 2021, at 08:30, X Guest wrote: > > would you please release a perl thin client? thanks. > > > On Thu, Apr 22, 2021, at 3:21 PM, Ivan Daschinsky wrote: >> The Apache Ignite Community is pleased to announce the

[ANNOUNCE] Apache IGNITE python thin client (pyignite) 0.4.0 released

The Apache Ignite Community is pleased to announce the release of Apache IGNITE python thin client (pyignite) 0.4.0. This new release of python thin client contains a lot of changes. Namely: 1. Partition awareness support. 2. Asyncio support. 3. Numerous performance fixes. 4. Numerous bug fixes.