Hi,
How does the JVM error look like?
Apart from that, Andrey, Igniters, the failure handler fired off but I have
no glue from the shared logs what happened or how it is connected to the
Java heap issues. Should I expect to see anything from the logs not added
to the thread?
--
Denis Magda
On
Denis, the issue here is that we don't know for sure. We see just one
blocking issue with accessing NioAccessObject.
And there are 3 different scenario related to this issue fix:
- fixes won't help, and we should find out other options on how to create a
direct buffer from pointer - needed for dur
Hello, Ignite Community!
My name is Rafael. I want to contribute to Apache Ignite and want to start
with this issue [1].
JIRA username is rchumarin
[1] https://issues.apache.org/jira/browse/IGNITE-11120
Folks,
What are the efforts to support Java 12? Let's do 2.7.6 shortly if the
fixes are time-consuming.
-
Denis
On Fri, Mar 29, 2019 at 10:08 AM Dmitriy Pavlov wrote:
> Hi Igniters,
>
> I would like to announce code freeze for 2.7.5. Only one open ticket is
> there (reopened): https://issues
Hi Igniters,
I would like to announce code freeze for 2.7.5. Only one open ticket is
there (reopened): https://issues.apache.org/jira/browse/IGNITE-11600 (if we
can't start using Java 12 we should clearly state it in scripts/code).
We're entering to Stabilization phase for
https://cwiki.apache.o
Yes, I do it in a few days, great PR, many thanks
пт, 29 марта 2019 г., 18:49 Алексей Платонов aplaton...@gmail.com:
> Hey, Igniters!
> I prepared some PR for Serializable support in our Vectors.
> Could you review this: https://github.com/apache/ignite/pull/6378 ?
>
> чт, 28 мар. 2019 г. в 11:47
Hey, Igniters!
I prepared some PR for Serializable support in our Vectors.
Could you review this: https://github.com/apache/ignite/pull/6378 ?
чт, 28 мар. 2019 г. в 11:47, Алексей Платонов :
> Yep, I definitely agree with you.
>
> Moreover, such improvement should reduce parallel hierarchies in t
Gaurav Aggarwal created IGNITE-11657:
Summary: Stripe Threads Deadlock on Cache.putAll(Map)
Key: IGNITE-11657
URL: https://issues.apache.org/jira/browse/IGNITE-11657
Project: Ignite
Issue
Taras Ledkov created IGNITE-11656:
-
Summary: The GridCacheMapEntry#lockEntry cannot be interrupted
Key: IGNITE-11656
URL: https://issues.apache.org/jira/browse/IGNITE-11656
Project: Ignite
Is
Pavel,
I have provided MTCGA bot status in Jira issue comments. [1]
Eduard,
Yes, for current implementation it will be distributed PME if
in-memory caches configured.
1. https://issues.apache.org/jira/browse/IGNITE-9913
пт, 29 мар. 2019 г. в 14:49, Eduard Shangareev :
>
> Nikita,
>
> It sounds c
Nikita,
It sounds cool. But I didn't get about in-memory caches. The baseline is
not used for their affinity calculation.
So, this improvement would be switched off for them or completely (when
such caches are presented), wouldn't it?
On Thu, Mar 28, 2019 at 3:14 PM Pavel Kovalenko wrote:
> Hi
Hi Denis,
I'm not talking about months. In this discussion, Andrey and Ivan proposed
a couple of fixes that may help.
It will require a day or two to check if it helps. If it not helpful then
we should modify startup scripts to say clearly that Java 12 is not
supported.
Now under Java 12 Ignite
Anton Dmitriev created IGNITE-11655:
---
Summary: ML: OneHotEncoder returns more columns than expected
Key: IGNITE-11655
URL: https://issues.apache.org/jira/browse/IGNITE-11655
Project: Ignite
Anton Dmitriev created IGNITE-11654:
---
Summary: ML: Memory leak in KNNClassificationModel
Key: IGNITE-11654
URL: https://issues.apache.org/jira/browse/IGNITE-11654
Project: Ignite
Issue Type
Roman Guseinov created IGNITE-11653:
---
Summary: Remove warnings which appear during CPP compiling
Key: IGNITE-11653
URL: https://issues.apache.org/jira/browse/IGNITE-11653
Project: Ignite
Is
15 matches
Mail list logo
