Re: ignite stops expiring caches after a period of time

I forgot to mention this is on Ignite 2.6.0 and i'm running with a 3 node cluster. I've been experimenting some more and I'm finding that using PARTITIONED caches works fine, but replicated caches stop expiring usually within 10 minutes. The behavior is very consistent. I plan on trying this

Re: Do we require to set MaxDirectMemorySize JVM parameter?

In the above example, is setting " " in xml config file same as adding a jvmoption "-XX:MaxDirectMemorySize=8g" ? or its different? Can somone please clarify? Thanks ...summa -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite .NET in docker (linux)?

Here is a gist to run Ignite.NET in Docker on Linux & .NET Core: https://gist.github.com/ptupitsyn/1cbbdaef1fef7cc4be22addda19cade4 Confirmed to work with Ignite.NET Client on Windows. Let me know if you need more info. Looks like you use some event API with remote filters, make sure that remote

Re: Avoiding Docker Bridge network when using S3 discovery

Created https://jira.apache.org/jira/browse/IGNITE-10791 for this -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite .NET in docker (linux)?

Thanks for your support, but I need more informations. Let me try to give you more details: I've launched a ignite node on docker with this command: docker run -it --rm --name ignite --net=host apacheignite/ignite Then I try to connect to my dotnet client with this configuration: Snippet Ignite

RE: First write to new cache on new cluster.

Hi, Are you sure it is only the first write? I’m not aware of any lazy initialization there, so I wouldn’t expect the first write to be slow. Which version do you use? And what is the performance difference of the first transaction compared to the second? I have two ideas why it may work

Re: how credentials can be provided in client side when ignite authentication is enabled

Hello! As far as my understanding goes, Apache Ignite authentication only affects thin clients (such as JDBC or native Python/PHP/C# client). You can add authorization include client node join checks, but that will require custom plugin implementation. See

Re: Re: Partition-exchanger blocked after upgrade to 2.7

Hello! There is a ticket to make those messages more clear: https://issues.apache.org/jira/browse/IGNITE-10760 Regards, -- Ilya Kasnacheev пт, 21 дек. 2018 г. в 11:31, aa...@tophold.com : > Thanks for clarify! > > Regards > Aaron > > > *From:* Loredana Radulescu Ivanoff > *Date:* 2018-12-21

Re: Re: Partition-exchanger blocked after upgrade to 2.7

Thanks for clarify! Regards Aaron From: Loredana Radulescu Ivanoff Date: 2018-12-21 02:40 To: user Subject: Re: Re: Partition-exchanger blocked after upgrade to 2.7 Hello, We've been witnessing a similar set of logs from Apache Ignite after upgrading to 2.7 (from 2.6) in a couple of