Hi Semyon,
I have tracked the issue down in our code base and in the end it wasn't
Ignite's fault.
Sorry for the false alarm.
Kamil
On 5/19/21 9:43 AM, Kamil Misuth wrote:
Hi,
yes. I am preparing a reproducer but this is happening in a production
grade app deployed in our testing
such optimizations but I don't see them enabled in your
configuration so perhaps it's a bug.
I still have trouble reproducing your issue, so could you please send a minimal
reproducer?
Kind regards, Semyon.
19.05.2021, 06:12, "Kamil Misuth" :
Hi Semyon,
we are using Ignite 2.8.1. That being said, co
Hi Semyon,
we are using Ignite 2.8.1. That being said, could Ignite really be using
some behind the scenes optimization which allows for a value instance to
be re-used between multiple EntryProcessor runs?
Kamil
On 5/17/21 11:45 AM, Данилов Семён wrote:
I tried reproducing your issue but
Hi, since Java 11 is not only about new features but also about new
licensing terms and new release schedule, I would like to ask about the
long term goals of the Apache Ignite project.
Question 1:
With the new Java release model, it seems Oracle will provide security
fixes and backports to
Hi,
there were multiple issues, one of them being shared and overloaded
disks on a hypervisor. That being said, I am not sure if the problem
disappeared completely. The node was up since then. The dataset is some
40 GB "bootstrapped" from Kafka. I would need to play with it more, but
don't
after 2.0 release. You can track the
progress here:
https://issues.apache.org/jira/browse/IGNITE-4961
—
Denis
On Apr 18, 2017, at 3:47 PM, Kamil Misuth <ki...@ethome.sk> wrote:
Replying, to my own question.
Indeed, it seems to be the case that for Ignite 2.0, everything will
be off heap.
:).
Kamil
On 2017-04-19 00:43, Kamil Misuth wrote:
Sure, Andrey.
In mean time, a fact-checking question:
I haven't really gone through the new memory policy functionality in
depth, but it does seem that for Ignite 2.0 your aim is to move data
off heap implicitly for all caches (and possibly backup
you again!
On Wed, Apr 12, 2017 at 11:56 PM, Kamil Misuth <ki...@ethome.sk> wrote:
Hi Andrey,
I've built ignite-3477-master (commit hash 5839f481b7) today.
Apart from the fact that some other Configuration APIs changed,
CacheMemoryMode disapeared. I guess this is related to
http://apache-i
Are you getting "GC Overhead limit exceeded" OOME?
I think you could always move IGFS data block cache off heap if it is
not the case already.
I am wondering why you've set block size to 4 GB for Ignite when HDFS
stock configured block size is either 64 MB or 128 MB. Have you tried to
set
.
Attaching crash logs from both nodes (running on the same machine
FreeBSD 11) to this e-mail.
Kamil
On 2017-04-12 00:49, Kamil Misuth wrote:
Sure thing.
I will check out ignite-3477-master as soon as I have some time
tomorrow.
Kamil
On 04/11/2017 05:48 PM, Andrey Gura wrote:
Thanks
Apr 10, 2017 at 2:53 AM, Kamil Misuth <ki...@ethome.sk> wrote:
Greetings,
OpenJDK (7 and 8) HotSpot JVM SIGSEGVs on FreeBSD 11 as soon as node
joins a
topology and starts to communicate via DirectNioClientWorker.
The root cause is DirectByteBufferStreamImpl (both versions) which uses
GridU
Greetings,
OpenJDK (7 and 8) HotSpot JVM SIGSEGVs on FreeBSD 11 as soon as node
joins a topology and starts to communicate via DirectNioClientWorker.
The root cause is DirectByteBufferStreamImpl (both versions) which uses
GridUnsafe.getXXX/putXXX(Object object, offset, value) methods to
12 matches
Mail list logo
